Skip to content

Data and reproducibility

Research materials

Download the observations behind the figures, follow individual calls to their receipts, and inspect the registered implementation references.

Data behind the results

Each extract preserves its unit of observation and identifies its original study records. The manifest defines the fields, records provenance and supplies SHA-256 digests for all 15 extracts.

Study designs and observations

Evidence from individual worlds

Engineering records

Start with the world and branch

Event and decision identifiers are local to a named world. A physical call record has its own identifier. Follow the named branch, tick and local call ID before joining an event to a model decision.

R01/B · Sale

Words, then a transfer

Ilan’s inherited call 36 mentions a crate and two coins. Mara responds in branch call 51. The settled transaction appears later, in branch call 55, event 112. It records two crates for four coins. The projected before-and-after balances allow the transfer to be checked.

Sources · Selected journal cases

R07/A · Memory

Retrieved, shown, cited

Call 133 requests a search. Records 94, 185 and 146 appear in the merchant’s later packet and are cited when he offers stock to the smith at call 138. This is evidence of exposure and citation. Testing whether those records changed the choice requires a controlled intervention.

Sources · Selected journal cases

Reproduce a claim from public rows

The numerical figures and their underlying data are included in this publication. Counts from the public tables can be checked with a spreadsheet or any CSV reader.

  1. Recreate a pairGroup the Long-Life table by history. For each metric and each of R01–R08, subtract the A count from the B count. Those are the points in the paired figure.
  2. Check a denominatorFilter the joint-rest opportunity table by schedule. Count the rows with a completion receipt, then count all displayed turns. A gives 32/38 and B gives 36/74. The paired-history table includes branches where the option never appeared.
  3. Verify an extractCalculate SHA-256 on the downloaded bytes and compare it to the file’s manifest entry. The optional verifier checks the hashes and recomputes the main comparisons.

With Python 3, run python verify.py from this resources folder, or supply the directory containing the manifest as the first argument. The site itself needs only a browser.

What the release can verify

Public tables reproduce the reported counts. The architecture reference locates the implemented mechanisms at a pinned revision. The complete SQLite databases, full communication logs and private resident notebooks are retained in the research archive.

Long-Life registration

Study long-life-20261118-r01-r08
Revision 4f5a2bf3e2331bde4b88f4d69917c6e1409e2a19

Original archive SHA-256
ffecd50531eca3c1ec2442fe6ade54b02d62d87a1493ade202ea106c0f3b0eb1

These identifiers support comparison with an authorized archive copy. They are archival references.

Read the mechanisms

Examine how local perception feeds a decision packet, where engine authority begins, and how the runtime distinguishes saved-reply recovery from fresh inference.