One governed map; twelve distinct referencesThe package connects shared authority without pretending that one application owns every rule, artifact, or implementation.
Open public walkthrough →Keep rule, evidence, and implementation separate
The package connects these layers through named references and provenance. It does not collapse them into one claim.
RuleDefines what must hold and where authority lives.
EvidenceShows what was observed, by which source, and when.
ImplementationIs the code or system behavior that can be tested against the rule.
Explore the 12-part public reference snapshot
Select a card to see its public role. Labels summarize the OQS Protocol Library map; they are not a live inventory or freshness assertion.
Cross-instance briefing carries the package safely
Source-linked packageNames the authority, reference, and public proof boundary.
→
Portable orientationLets another instance resume with provenance, without treating a handoff as execution evidence.
What this stand-in proves—and what it does not
It proves the public learning surface exists and explains the package shape. It does not prove registry freshness, reconciliation, code execution, or a live operational result. Those require their own current evidence.