Evidence and reproducibility¶
A useful review connects a claim to the evidence that could support or defeat it. A design requirement, a successful reference run, and an observed deployment answer different questions. This guide explains how to read those distinctions throughout the collection and how to reproduce the published documents.
The papers develop conceptual arguments, conditional results, and illustrative cases. Where they discuss reported tests or historical implementations, they identify the relevant scope. Proprietary construction details are excluded, so implementation claims that depend on those details remain outside what readers can independently verify here.
What each kind of evidence establishes¶
- SpecificationWhat is required or proposed?
- Executable referenceWhat does this bounded implementation do?
- Machine-checked propertyWhat was checked, on which model or domain?
- Refinement proofWhich descriptions are related, and how?
- Empirical observationWhat happened on the stated inputs and workload?
- Independent reviewWhat did an identified external reviewer inspect?
Figure 1. Six forms of evidence, each with a different subject and method. Strengthening one form does not automatically establish another.
| Evidence | What a reviewer needs to establish |
|---|---|
| Specification | The requirement or proposal, the subject it governs, and its assumptions and unresolved dependencies. A specification describes intended behavior. |
| Executable reference | The named artifact, inputs, environment, and observed behavior. Its conclusions apply to the cases examined and depend on the reference's assumptions. |
| Machine-checked property | The property, formal model, checking method, and exact domain or bound. A document-structure check is a different kind of validation. |
| Refinement proof | The source and target descriptions, the relation between them, and the assumptions under which it preserves the claimed properties. Deployment conformance requires additional evidence. |
| Empirical observation | The method, sample, denominator, environment, exclusions, and measured outcome. Illustrative scenarios supply explanation rather than measurements. |
| Independent review | The examiner, method, scope, evidence, relationship to the work, conflicts of interest, and period of validity. The review's conclusions remain bounded by that examination. |
A single work can have several kinds of support. It may contain a mathematical argument, an executable reference, and a practical hypothesis that has not been measured. Each claim should retain its own basis.
For a conditional result, “under stated assumptions” should point to an actual premise-and-conclusion register. A reviewer needs to distinguish the abstract implication from evidence that its premises hold in a realization. Similarly, an executed finite model should identify its variables or case domain, tool, checked property, observed result, and control that demonstrates the checker can detect the relevant defect. Generated formal source and an aggregate status count do not supply those facts.
The collection uses source-reported for a result record inspected in the source material, publicly inspectable reasoning for an argument stated here with its premises, public reference run for the disclosed teaching example executed for this edition, and independently reproduced only when an identified third-party examiner reruns a check with its artifact, environment, and method recorded. Another pass by the same editorial system is not independent reproduction. Inspecting a recorded successful run does not reproduce it. Building these publication files reproduces their presentation, not the research experiments discussed in them.
How to read the collection's claims¶
Governed Autonomous Institutions develops design commitments and conditional arguments about identity, authority, obligations, and continuity. Implementation conformance, legal recognition, and the effectiveness of a real governance arrangement each require evidence about the particular institution.
The architecture synthesis compares responsibilities across separate works. It distinguishes relationships expressly defined by a source from conceptual correspondences, proposed integrations, and open adoption decisions. Those distinctions identify what a composition study would need to establish.
The topic papers develop definitions, arguments, examples, assumptions, and research questions. Their examples are illustrative unless a different basis is identified. The papers' evidence sections state the conditions under which a stronger implementation, empirical, or formal claim could be made.
MIRAGE: the scope of the reference model¶
MIRAGE distinguishes a master architecture, a native design, and a bounded semantic reference. The reference assumes a hostile guest while retaining trust in the host and relevant administration and emission environment. Its results concern a declared channel model and an enumerated release language; they do not establish unrestricted natural-language confinement.
The MIRAGE result register identifies the reference revision, input bounds, checked predicates, interruption schedule, and reported outcomes. Its storage result concerns nine positions in one local transaction probe, reporting the complete old or new tuple rather than a mixture. It is source-reported process-interruption evidence, without a power-loss, malicious-storage, administrator, or anti-rollback result. A reference behavior, a restriction in software, and closure of every relevant route through real infrastructure are separate claims. The mappings among doctrine, architecture, and reference identify scoped obligations rather than completed refinement proofs of the whole system.
The reference implementation and its private qualification material are not distributed with this collection. Its historical results are discussed at their reported scope, without presenting them as tests reproduced by this edition.
Conditional arguments and finite models¶
The thesis register and derivation identify the conditions for fixed-mode activation convergence and for growth of knowledge without authority creation. The disclosed convergence implication is an ordinary mathematical argument about a contraction on a complete domain. Whether a particular activation design satisfies those premises remains a separate question. Convergence in one fixed mode does not establish sparse dependency completeness or stability during arbitrary switching.
The RCFS register makes the premises and limits of the paper's structural arguments explicit. Its permission-separation derivation holds current authority fixed while changing methods. It does not assume that qualification grants authority, that formal accounting guarantees real-world fulfillment, or that a model replacement preserves competence without a separate qualification relation.
The AD8 finite-model register identifies three selected TLC studies: approval payload binding, receipt coverage and freshness, and one-time initialization with conditional progress. The source records four distinct reachable states in each base model and counterexamples from four deliberately faulty controls. These studies examine their finite definitions, not the entire AD8 system. They do not qualify the broader formal portfolio, prove real-world fairness, or supply missing object constructions.
The AD8 dependency account and CSSL foundation account identify what a missing construction prevents a reader from claiming. Bounded encoding, commitment arithmetic, or a detector for an incomplete projection may remain valid at their stated scope while a complete object or transition cannot yet be claimed. The CSSL observation criterion defines permitted and forbidden old/new views for a declared atomic change; it is an intended invariant whose implementation still needs conformance evidence.
Current implementation and public reproduction¶
The implemented systems page records a dated examination of actual Freehold and Cuttlefish source and deployment evidence. It distinguishes fresh authenticated metadata from retained readiness observations and source-only behavior. Private implementation and operational records are withheld. Their inspection does not become third-party reproduction merely because exact commitments are published.
The public continuity exhibit has a different contract: disclosed source, deterministic fixture, separate effect witness, actual process interruption, eleven checks, expected observations, and a run commitment. Reproducibility provides the one-command route and its assumptions. A reader can reproduce that reference without any private system or AWS access. Its result does not establish the private product's behavior under the same faults.
The claim register maps material assertions to their exact text, source scope, support type, method, exclusions, and inspection route. A public reference run performed for this edition is labeled as such. No third-party reproduction or independent audit is claimed.
Historical implementation claims¶
An implementation claim applies to an identified version, environment, and method of inspection. Some sources discuss earlier examinations of Cuttlefish implementation material. Such records can explain the development of an idea, while current product acceptance requires current evidence.
Withheld or unavailable material limits independent review. It does not establish that a system is absent or defective. A conclusion about present behavior needs the relevant artifact, method, and observations.
Examples, counterexamples, and studies¶
A worked scenario explains a distinction. A counterexample challenges a general claim by satisfying its premises while defeating its conclusion. An experiment measures identified subjects under an actual method.
For example, a recommendation based on genuine observations may still lack authority for execution. This conceptual case challenges the inference from provenance to permission. Testing whether a particular runtime enforces that distinction requires observations at its actual decision and effect boundaries.
A proposed study should specify what is measured, how the sample is obtained, how incomplete attempts are counted, and what result would count against the hypothesis. A denominator of zero cannot support a success-rate estimate. Excluding interrupted or difficult work can materially change a result.
Reproducing the publication¶
The build guide provides the dependency versions and commands for producing the website, individual papers, and collected volume from the same Markdown. The download records identify the content and the resulting files.
Publication checks cover source completeness, metadata, local links, generated pages, PDF text, navigation, and rendering bounds. Visual inspection complements those checks by examining layout and legibility. These procedures verify the publication artifacts; research claims require the methods appropriate to their subjects.
A practical review standard¶
For a material claim, identify its source and version, assumptions, method, inputs, observed result, and remaining uncertainty. For a relationship between systems, also identify what is mapped and what still requires a decision or demonstration.
The review guide explains how to submit a correction, counterexample, or proposed study. The author statement describes responsibility and editorial assistance.
Successor observation dates¶
Implementation inspection and production observations retained in this successor come from the historical author-directed examination dated 10 October 2026. They are not new product observations by the successor author pass. Fresh authenticated metadata in that historical examination remains distinct from retained workload readiness. The successor's own executable evidence is the disclosed teaching references; no private product test, customer action or independent production audit was performed.