A repository proves there is source to inspect. A passing fixture proves something about the inputs, assertions, and environment that fixture exercised. Neither automatically qualifies a player-facing release.
Bridge makes the boundary explicit
The Bridge README instructs testers to read an exact candidate’s immutable release classification. A version number or a GitHub “Latest” label is not the approval criterion.
Profiles has its own boundary
Profiles describes synthetic checks and adapter compilation while explicitly leaving game-runtime qualification open. This is useful progress. It should remain visible without turning into a finished multi-profile product claim.
How we label the work
Project pages on this portal distinguish public source, public canary, in-development work, and research. These are editorial summaries dated to the last source review. The linked repository remains the place to confirm the current installation and qualification guidance.
Clarity about unfinished work makes it easier to invite useful testing and easier to understand what a result actually establishes.