Claim register and evidence index¶
The register preserves each substantive paragraph and table row in the sixteen papers, together with the implementation, exhibit, evidence, terminology, assurance and prior-art discussions. Each entry gives its exact maintained wording, stable identifier, section, evidence type, source fingerprints, assumptions, observation date, reproduction route and exclusions. Table rows retain their premise and conclusion cells together.
The complete JSON register and CSV evidence matrix contain 1449 entries. They are generated from the visible public text; there is no separate hidden set of stronger assertions. Headings, links, metadata and citations receive their own publication checks.
Read an evidence type correctly¶
| Type | Interpretation in this register |
|---|---|
| Proposed | An authored design requirement, conceptual distinction, interpretation or research question. It is not represented as demonstrated system behavior. |
| Conditional derivation | A stated conclusion under an explicit domain and premises. Inspect the deduction and whether the premises hold in the intended application. |
| Formally checked within specified bounds | An identified finite model and result. The entry names its recorded method and retains the excluded broader claims. |
| Reference-implemented | An implementation path inspected at an identified source revision. Source inspection and test definitions are distinct from a newly executed behavioral test. |
| Tested | A specified executed reference or an explicitly labeled source-reported test. The status and date tell the reader which applies. |
| Production observed | Dated operational evidence with separate labels for fresh authenticated metadata and retained workload observations. It does not imply every user journey was tested. |
| Independently reproduced | Reserved for an attributable external examiner and method. No entry in this edition has this status. |
Sixteen complete papers¶
| Publication | Registered statements |
|---|---|
| Governed Autonomous Institutions | 134 |
| Architecture of Governed Autonomous Systems | 112 |
| MIRAGE | 97 |
| CSSL | 72 |
| IC/POAR | 54 |
| NTVBCD/AD8 | 75 |
| Freehold | 92 |
| Cuttlebone | 80 |
| SEPION | 69 |
| RCFS | 75 |
| Cuttlefish Semantic OS | 58 |
| Cuttlefish Operating Environment | 64 |
| CHROMATIC | 68 |
| Experience Economy and ISE | 73 |
| The Reckoning | 65 |
| Human–LLM Capability Elicitation | 68 |
Operational and public-reference evidence¶
The implementation account identifies the examined image and source commitments. Its source-inspection claims, fresh registry observations, retained workload observations and unmet behavioral assurance conditions stay separate. The raw implementation and production records remain confidential.
The continuity exhibit is an actual public reference run. Its eleven observations can be rerun with the disclosed standard-library source and fixture. Its provider assumptions are explicit. It establishes a result for that teaching reference; it does not establish the same guarantee for an arbitrary external service or the private production system.
Qualifications are part of the assertion¶
The assurance boundaries and individual papers retain the exact research limits. In particular, the finite AD8 results do not establish its 215 broader claims or execute its twelve authored traces. The construction dependencies, compatible value domains, current authority, evaluation independence and external-effect contracts remain consequential premises.
When challenging a claim, cite its identifier, edition, section, method and a counterexample or observation. A stronger future result requires a new evidence record and reviewed wording. A successful document build, a healthy workload and an independent reproduction remain distinct observations.