Long-term standards memory
Canonical files preserved
under /docs/standards/.
This directory mirrors the current standards release, machine catalog, mission schema, example fixture, and record schema so the project’s long-term document memory remains complete and directly addressable.
Archived publication files
Human and machine records.
Use the root publication routes for current public claims. Use these `/docs/standards/` paths when durable project memory or source-preserving handoff is required.
MARKDOWNIARPG-OPS-2 complete releaseAll canonical records, normative requirements, and report links in one document.→
JSONStandards catalogCurrent release metadata and all 70 canonical records.→
JSON SCHEMAMission brief contractRequired mission fields and current enumerated policy values.→
JSON FIXTUREOperation Hollow SignalComplete Level D — Simulatable mission brief example.→
JSON SCHEMAStandard record schemaMachine contract for individual canonical standards records.→
MIGRATIONOPS-1 to OPS-2Compatibility, new fields, and explicit migration actions.→
CONFORMANCELevels A through DBriefable, Playable, Auditable, and Simulatable requirements.→
RECORD INDEXAll 70 recordsStable human and JSON routes by category and code.→
JSON SCHEMAOperation PackagePortable mission, authority, roles, evidence, simulation, debrief, conformance, migration, and checksums.→
PACKAGE FIXTUREHollow Signal packageComplete local operation lifecycle fixture.→
RELEASE DIFFOPS-1 to OPS-2Preserved codes, changed records, added records, and migration actions.→
FIXTURE TESTSDeterministic resultsMachine-readable package, mission, migration, comparison, and archive checks.→
CANONICAL JSONIARPG-CJSON-1Project-local deterministic bytes, duplicate-key rejection, and SHA-256 vectors.→
CONFORMANCE VECTORSBrowser and build parityPassing and required-rejection vectors for the project canonicalization profile.→
PORTABLE INTEGRITYIntegrity bundle schemaDetached package and component digest evidence without identity claims.→
PROVENANCEWorkflow envelopeDeclared local workflow lineage without authentication overclaim.→
COMPATIBILITYTested release matrixImport, export, migration, round-trip, limitation, and fixture evidence.→
UAI MEMORYStandards publication memoryConcise identity, routes, release boundaries, and deep documentation pointers.→