Skip to content
Reading guide

On this page

Research Depth & Proof

A technically useful claim names the property, its assumptions, a way to falsify it and the evidence actually obtained. This edition retains the twelve substantial investigations added in 2026.10.7 to the sixteen-paper library. Each has a worked synthetic trace, a deliberate fault, reproduction commands and explicit limits. These are synthetic technical investigations retained in edition 2026.10.9; their evidence and limitations are scoped individually.

For a five-minute review, read Engineering Methodology, AD8's open constructions and uncertain external effects. For an hour, follow the approval, freshness and observation cases through their negative results. A specialist can download the successor source, run every case and compare the public evidence records with the propositions. No private input is required for the advertised public reproductions.

Technical investigations

Claim Investigation Decisive negative case
GA-SYN-001 Approval binds the action consumed One-use accounting still executes a changed payload
GA-SYN-002 Evidence freshness Authentic old read admits stale use
GA-SYN-003 One-shot founding and progress Retained voucher; endless waiting without fairness
GA-SYN-004 Epoch identity Old permission survives a name-preserving restart
GA-SYN-005 Canonical value language Unframed pairs collide; carrier widths disagree
GA-SYN-006 Unresolved constructions Total components do not imply a unique fixed point
GA-SYN-007 Atomic observation Reader sees a partial installed revision
GA-SYN-008 Uncertain effects Lost acknowledgement hides a committed effect
GA-SYN-009 Projection meaning Quantity matches while the unit changes
GA-SYN-010 Independent custody Two voter labels have one controller
GA-SYN-011 Resource accounting A burned subset is counted twice
GA-SYN-012 Calibration comparator Mismatched baseline reverses the skill conclusion

The sixteen maintained research areas

The maturity below describes the research treatment, unless a row explicitly identifies production evidence. The synthetic teaching cases have their own reference_implemented status. Analytical exposition is not production conformance, and a narrower reference does not upgrade its entire parent domain.

Area and technical synopsis Engineering / assurance Strongest open question and proof path
Institutional thesis: initiative, duty, permission and amendment power belong to different subjects specified / analytical Can institutional controls remain independent under founder capture? Custody
Architecture synthesis: connect continuing work to authority, evidence and recovery without conflating the component roles conceptual / analytical What contracts and refinement evidence justify each integration? Responsibility map
MIRAGE: constrain consequential operations and observation at a resource boundary reference_implemented in bounded studies / fault_tested within named references Are all real observation and effect routes mediated, including recovery and administrators? Visibility
CSSL: semantic change identity, causal closure and consistent observation specified / analytical, with scoped reference counterexamples How are unresolved identities constructed and relevant distributed observations covered? Construction, visibility
IC/POAR: preserve explicit intentions and obligations through realization and repair specified / analytical, with scoped finite studies Does a real lowering preserve the right observable relation? Projection
AD8: connect identity, authority, receipts, state and continuity specified; limited references / broad assurance withheld Can the open identity, numeric and execution obligations be closed? Technical investigation
Freehold: durable institutions originate work within founded scope product_implemented; dated production_observed evidence is separate / source-inspected and scoped observation Can a changed worker preserve outstanding duties without restoring stale authority? Epoch, implementation
Cuttlebone: connect founding grants, causal origin and external-effect ceilings specified / analytical and contract regressions Does every real effect preserve the originating ceiling? Approval
SEPION: qualify generated artifacts within declared evaluation context specified / analytical and scoped binding tests Which observations distinguish apparent agreement from equivalence? Projection
RCFS: preserve authority and resource invariants across adaptation specified / analytical and arithmetic counterexamples Which amendments and split/merge constructions preserve the declared laws? Budget
Semantic OS: maintain application meaning outside transient model context specified / analytical Can drift detection and authorized correction be refined to actual application behavior? Projection
Cuttlefish operating environment: connect persistent objectives, tools, current authority and external observations product_implemented; dated production_observed evidence is separate / source-inspected and scoped observation Which journeys have witnessed fulfillment and recovery evidence? Uncertainty, implementation
CHROMATIC: keep user-visible action, permission, feedback and recourse coherent specified / analytical Which receipt, validation and reversal promises apply to irreversible actions? Uncertainty
Experience Economy and ISE: govern the conditions and provenance of experience reuse specified / analytical and scoped arithmetic/graph tests What can actually be withdrawn after influence has entered learned weights? Freshness
The Reckoning: distinguish forecast quality, calibration and epistemic accountability specified / analytical, with arithmetic counterexamples Do composite incentives retain the properties of their scoring components? Calibration
Human–LLM capability elicitation: study how interaction changes attainable supported capability conceptual / hypothesis and analytical definitions Which prospective controlled experiments show benefit beyond polished output? Calibration, methodology

The remaining domains warrant serious investigation, but their broader empirical, legal, economic or interoperability claims cannot be made true by adding more toy models. Current evidence supports the cases above; proposed experiments and missing constructions remain in the research agenda. No paper receives a proof score from its registry size.

How to challenge this edition

Select a claim ID, identify its observation and assumption set, then run the disclosed reference. A model counterexample challenges the proposition inside that scope. A deployment counterexample requires evidence about the actual implementation and route. A prior-art correction may narrow the contribution even when every test passes. The review guide accepts all three kinds of feedback. Prior-art comparisons identify foundational work without implying endorsement.