Public Artifact Index¶
This page is the stable opening-order registry for the public proof surfaces the repository expects outsiders to inspect.
These artifacts are not decorative links. They exist because the repository now has enough benchmark, runtime, grounding, recommendation, and consequence surfaces that readers need a clear starting order instead of reverse engineering intent from the tree.
How To Use This Index¶
- start with repository-wide artifacts when the question is whether any wider public sentence is earned at all
- move to workflow-family artifacts only after the repository boundary is clear
- treat every coexistence rationale as a removal pressure: if two artifacts no longer serve distinct review roles, one of them should disappear
Repository-Wide Artifacts¶
| artifact | reader question | why it exists |
|---|---|---|
| Flagship Release Candidate | what is the strongest release sentence today | names the current bounded family bundle |
| Current Capability Limits | where must the language still stop | acts as the honesty boundary for all stronger prose |
| Hostile Review Kit | what is the shortest whole-repository challenge route | gives the harder outsider-facing opening order |
| What Would Make This Repository Ready | what concrete evidence would widen the boundary | converts blocker categories into closing conditions |
Workflow-Family Artifact Pattern¶
Each public flagship family should now be readable through three different artifact roles:
| role | strongest question answered |
|---|---|
| trust page | why does this family still earn its current bounded sentence |
| independent rerun dossier | can the family survive a second checked rerun or replay challenge |
| external review kit | what should a skeptical outsider open first to challenge the family sentence |
That pattern exists for dda, dia, lfq, ptm, and targeted.
multiplex is intentionally outside the outsider-facing kit set because its
current public posture still stops at internal support only.
Why The Index Exists¶
The index protects against three failures:
- starting with the smoothest page instead of the hardest challenge route
- shipping new public artifacts that do not add distinct review value
- letting weaker surfaces ride next to stronger ones without naming the difference
What This Says About The Current Product¶
- the repository now has enough public scientific and runtime substance that artifact coexistence itself has to be governed
- public scrutiny is now a first-class product surface rather than a maintainer-only concern
- artifact count is not the success signal; distinct challenge value is required for each public surface
Strongest Next Page¶
After this page, open the Public Artifact Role Matrix to see how stronger and weaker public artifacts sit beside each other.
Boundary¶
This index should explain opening order and coexistence. It should not replace the stronger challenge artifacts that it points to.