AD8 technical investigation¶
AD8 investigates how identity, authority, evidence, state and continuing effects could remain connected when their implementations change. A credential can identify permission at one boundary; a log can record an event. Neither by itself settles whether a current action matches its approval, whether its premises remain valid, or whether the reported effect fulfilled a continuing obligation. AD8's proposed architectural contribution addresses that conjunction. The complete composition remains an engineering and assurance obligation.
Edition 2026.10.7 adds original public teaching investigations to the existing AD8 paper. They are independent abstractions, with no native transport, generated carriers, private algorithms or product routing. The public examples establish only their stated model propositions.
Five connected review questions¶
- Approval binding — GA-SYN-001: can one-use accounting still execute a changed payload? Eight histories isolate the difference.
- Freshness — GA-SYN-002: can an authentic old read authorize after a material change? A stale-use counterexample separates authenticity from current eligibility.
- Founding — GA-SYN-003: what does consuming an exception establish, and what additional fairness premise supports progress? A retained-voucher fault and an endless waiting cycle answer different questions.
- Canonical encoding — GA-SYN-005: can a deterministic representation remain ambiguous, or disagree with another carrier's accepted values? A small text encoder and a width counterexample expose the limits.
- Construction obligations — GA-SYN-006: why do successful component calculations fail to establish a solution to a cyclic identity equation? Three fully enumerated functions separate existence, uniqueness and computability.
Epoch identity — GA-SYN-004 and uncertain effects — GA-SYN-008 supply adjacent questions. These links indicate conceptual alignment and unresolved refinement obligations. They do not define a native integrated stack.
Native evidence retains its own boundary¶
The inspected Rust reference supplies an encoder and generated transport carriers. It supplies neither a decoder nor an independent complete signed-object or authorization verifier. The Python reference additionally supplies decoding and bounded framing functions. Generated types compiling does not establish schema validation, equal accepted value languages or current authority. The synthetic text example above is intentionally a separate value language.
The current native assurance record withholds 215 broad claims and marks twelve authored traces as unexecuted. Earlier overbroad assurance labels were withdrawn. Three named finite native models have scoped recorded results, including deliberately faulty variants; the original paper's model discussion states their bounds. New author-stage checks of the accessible reference material remain private evidence for the separate reviewer. This public package advertises reproduction only of its disclosed synthetic examples.
v2 reviewed / original history incomplete. The available capture supports review of v2, not the complete original AD8 history. Reviewing the current proposal and reference files does not establish complete original-to-successor semantic preservation. Migration rows and source crosswalk proposals are not semantic equivalence proofs. Historical signatures and bytes must retain their original interpretation.
Open constructions and what they prevent¶
| Obligation | What remains missing | Conclusion withheld |
|---|---|---|
| Cyclic identity construction | A versioned construction with explicit preserved semantics and executable evidence | General construction of conforming receipt-bearing objects |
| Cross-format numeric values | A single agreed value domain and positive/negative boundary conformance | Equivalence inferred from compilation or small shared vectors |
| Prior and prospective anchors | A precise distinction between existing committed history and a candidate's own future inclusion | Authority inferred from an inclusion that has not happened |
| Original-to-successor migration | Available predecessor bytes, original interpretation and semantic preservation evidence | Complete original history or vault-wide supersession |
| Specification-to-execution | Implementing components, failure-route coverage and qualified observations | Complete runtime or product deployment of the proposal |
| Trust and revocation | Coverage, currentness, enforcement and realistic recovery evidence | Universal revocation, custody or external-effect guarantees |
A construction change cannot be smuggled into a proof by weakening the identity being proved. A successful bounded test cannot close a different obligation merely because both concern receipts or authority. The public evidence catalog therefore separates Research, Reference and Production for every new synthetic claim.
Fair comparison and production relationship¶
Protection principles, RATS, PROV-DM, RPC and TLA+ provide foundational distinctions. The collection does not claim priority for these ingredients or inherit their results as proof of its own composition. The architecture synthesis and prior-art review state the broader contribution and its obligations.
Cuttlefish and Freehold have separately published implementation and operational observations. Their existence does not establish that AD8 is their universal running control plane. See the dated implementation report, Engineering Methodology and claim register. To challenge a model or construction, submit its stable claim ID, edition, assumptions and counterexample through the review guide.