CANONICAL SOURCE
docs/reports/*.md preserves the supplied report bytes and hashes.
CANONICAL /DOCS · DISTRIBUTED .UAI MEMORY
THE RESEARCH, THE MEMORY, AND THE SOFTWARE ARE LINKED.
All 38 authorized public reports live canonically under docs/reports/, with every rendered heading addressable from distributed file memory. Protected customer reports remain under docs/private/ and private .uai compartments with no public route or public index entry. Distributed .uai project memory deep-links those immutable sources, records implementation decisions, and traces each report into platform modules, APIs, tests, and 3D/WebXR simulations.
FILE MEMORY MODEL
DEEP LINKS, NOT LOOSE SUMMARIES.
The report body remains authoritative. Memory files point to the exact source and identify how it should be used; they do not silently replace, reconcile, or rewrite the report.
DISTRIBUTED MEMORY
Domain, architecture, operations, testing, handoff, and per-report .uai records deep-link the corpus.
TRACEABILITY
Machine-readable and human-readable matrices map requirements to code, routes, APIs, simulations, and tests.
CONTROLLED DISCOVERY
Authorized public reports are exposed through research pages, the /docs atlas, sitemap routes, and raw Markdown endpoints. Protected customer reports remain in repository-local compartments with no public route.
SOFTWARE FROM RESEARCH
10 SPATIAL SIMULATIONS, ONE ASSURANCE PLATFORM.
01 Accountability Evidence Room →02 Decision Provenance Replay →03 Dynamic Assurance and Change Impact →04 Capability, Trust, Authority, and Permission Gates →05 Uncertainty Field and Abstention Space →06 Federated Data, Trust, Purpose, and Revocation →07 Resilience Web: Degrade, Quarantine, Reconcile →08 Modular Open Architecture and Vendor Swap →09 Governance Lifecycle and Qualified-Human Gates →10 Autonomous Drone Control Assurance Lab →
SOVEREIGN CONTINUITY DRILLS
INJECT THE FAULT. PRESERVE THE STATE. RESTORE ONLY WHAT CAN BE PROVEN.
Run forty-five bounded synthetic fault vectors against an append-oriented accepted-baseline registry, compare campaign generations, and inspect containment, minimum sovereign function, rekeying, reconciliation, and attested reconstitution evidence.
Open the recovery drill orchestratorCONTINUITY CAMPAIGN REVIEW
VERIFY THE CAMPAIGN BEFORE THE BASELINE MOVES.
Inspect exact scope, drill ordering, containment, minimum sovereign function, authority, reconciliation, reconstitution, qualifications, and immutable lineage. A review may propose a synthetic baseline; it never activates one automatically.
Open continuity campaign reviewAUTONOMOUS DEFENSE AUTHORITY KERNEL
INTERCEPT THE REQUEST. ENFORCE THE AUTHORITY. PROVE THE APPLIED ACTION.
Inspect identity, evidence, uncertainty, purpose, policy, delegated authority, nominal request, independent runtime assurance, applied defensive action, append-oriented history, claim impact, and attested recovery across thirty-seven bounded synthetic scenarios.
SOVEREIGN READINESS EVIDENCE FEDERATION
FEDERATE THE EVIDENCE. NEVER FABRICATE READINESS.
Verify exact continuity-review packages, expose shared lineage and correlated evidence, preserve contradictions, keep deployment and physical validation independent, and record a bounded recovery decision without activating a baseline or writing production authority.
AUTONOMOUS INDUSTRIAL RESILIENCE
KEEP THE INDUSTRIAL BASE ALIVE.
Detect degradation, preserve evidence, enforce maintenance authority, isolate compromised equipment, compare bounded robotic interventions, verify the repair, reconcile configuration, and return an asset to service only when the complete attestation chain agrees.