Reproduce and examine the evidence¶
The public package contains a complete teaching reference and the maintained sources for this research edition. Both can be examined without the original private vault, product repositories, production accounts or proprietary keys.
Execute the continuity exhibit¶
Use CPython 3.12 with its standard library. The release records the exact tested patch version and SQLite version. From the publication root, run:
python examples/continuity/verify.py
The command creates isolated temporary owner and witness databases, runs the witness in separate processes, deliberately terminates an owner after the witness commits, restarts it, and checks eleven positive and adversarial observations. It performs no network request, model call, payment or production operation. It exits unsuccessfully if any observation differs from the published expectation.
To retain a complete dated observation through the canonical reference/release path:
python tools/release.py --record-reference .build/reference-observation.json --reference-observation publication/reference-observation.json --observation-sha256 b45e40f4ae6f2c329f5396614470cf3a1c43ccf18876c67efde419a49a12e32f
The canonical command retains actual UTC start/completion times, a fresh observation identity, public source commitments, commands, environment and both reference result sets. The retained legacy continuity result inside it has a deterministic run_sha256 field: despite the historical name, this identifies result content, not a distinct execution. That result hash covers canonical result JSON before adding its own run_sha256 field. The bare exhibit command above checks behavior but does not issue the dated canonical receipt. The schema is evidence.schema.json; the recorded expected result is expected.json. The verifier compares actual observations with that expectation; it does not copy expected results into the observations.
What the controls test¶
| Case | Expected observation |
|---|---|
| Initial state | No effect has occurred. |
| Lost acknowledgement | One witness effect exists while the durable obligation remains pending. |
| Restart and reconciliation | The owner settles against a separately queried witness; the effect count remains one. |
| Sequential and concurrent replays | No additional effect is created. |
| Same identity, changed payload | The attempt is refused; the earlier effect remains unchanged. |
| Different institution | No authority is inherited from the first institution. |
| Revoked grant, new intent | No new effect is created. |
| Receipt tampering | A changed field is rejected. |
| Self-consistent forged commitment | Recomputing a hash does not make the forged statement agree with the witness. |
The witness's atomic identity/payload binding is an explicit provider assumption. The effect is a controlled notebook entry, not an autonomous citizen, browser task, purchase or production colony. Process interruption is exercised; power loss, malicious storage and compromise of the witness are outside this experiment. A hash commitment is not a signature or an authenticated identity.
Reproduce the publication artifacts¶
Follow BUILD.md for the exact locked renderer dependencies and complete build commands. The edition's build policy fixes SOURCE_DATE_EPOCH; the builder uses that value even when the caller supplies no environment override. Different values are rejected for release builds. Content hashes, generated bytes and actual behavioral observations are reported separately.
The positive public allowlist selects the maintained inputs. The disclosure tool rejects unknown tracked files and checks exact generated inventories. Public CI reads only this publication checkout. The release manifest identifies the exact allowlisted source tree and content digest, and each PDF, site archive, source archive, reference evidence and reviewer package. Source-only packaging does not require or distribute a Git commit, tag or history. A manifest does not include its own hash as an input; its detached checksum is stored beside it.
Independent reproduction¶
The public reference is independently inspectable. A reader can use the dated canonical command above and report the edition, source commitments, environment, complete new observation and any contrary result. The comparison never overwrites the recorded public observation or equates two event identities. Until an attributable external examiner has done so, this edition calls its own execution a public reference run, rather than an independent reproduction.
Private historical references and live system observations remain separately classified in the evidence guide and operational evidence page. Rebuilding the website does not reproduce those private experiments.
Successor investigations¶
The twelve original teaching cases run with standard-library Python only. They supplement the existing continuity exhibit without altering its bytes. See Research Depth & Proof, the public evidence catalog, and the successor offline build.
Exact package reproduction input¶
Use the immutable public observation supplied in the same source snapshot, verified by its content-manifest entry and the exact file digest in the command above. It is also distributed unchanged with the release assets and bound by their detached hashes. It contains no private input dependency. See recorded observation and fresh execution for producers, consumers and the focused regression.
The source epoch dates deterministic document/archive metadata only. Exact packaging consumes the recorded observation as immutable data; it does not assert that its execution happened again. A fresh independent rerun keeps its actual UTC times and its own observation identity even when its behavioral results match exactly. Use the original recorded input for exact package comparison, and retain the new receipt separately as reproduction evidence. Changing the selected observation changes the review/release package and requires new exact-bundle review and approval.