Records and review history

On this page

Start with the guides below, then open a record for its scope, source revision, environment, and result.

Current record map

Question	Current entry point	Structured record
Which sources are available?	Component index, source coverage	Source index, import receipts
What is complete, checked, or still open?	Status guide, evidence catalogue	Project status
What remains to finish?	Finalization queue	Queue entries in project status
How are collection records maintained?	Maintenance guide and selected cleanup checkpoints	Git history
What is publicly distributed?	Publication status, distribution notice	Public publication record
What did a particular check establish?	Verification guide, dated reports below	Execution evidence
What did the earlier collection record?	Historical snapshots	Historical manifests

The filename release-candidate.json is retained for compatibility. Its current status is PUBLIC_SOURCE_COLLECTION. It does not mean the public repository is still a private candidate. The earlier private-candidate record has its own historical path.

Bounded review history

These reports appear in review order, including those written on the same date. Later totals include earlier reviews, so do not add them together. Read each result with its scope, limitations, and source details. Updating this index does not add a review.

Date	Report	Recorded scope	Evidence binding
2026-10-27	Focused soundness and reader-list review	Editorial screening of seven entries, three focused claim audits, and two inspections of implementation limits.	JSON record
2026-10-27	SRIC admission audit: three acceptance gaps	Block 24 Python admission counterexamples and Block 23 documentation scope comparison.	JSON record
2026-10-27	SRIC admission repair: runtime 0.3.3	Known admission defects repaired in a separate source edition. Finite qualification only.	JSON record
2026-10-27	Machine Societies: three additional proof reviews	Three written proofs only: deterministic quotient, erasure reconstruction, and repair budget.	JSON record
2026-10-27	Machine Societies: memory, composition, and governance review	Eight written statement/proof pairs: identifiability, memory, composition, simulation, symmetry, governance quotient/refinement, and institutional language transport.	JSON record
2026-10-27	Machine Societies: stochastic closure and error bounds	Six written statement/proof pairs: controlled lumpability, finite-horizon closure, implementation dependence, transport defects, finite-block averaging, and robust reduced-model enforcement.	JSON record
2026-10-27	Machine Societies: safety, amendment, and computability review	Six written statement/proof pairs: inductive safety, finite-horizon viability, amendment confluence, quiescent replication, exclusive service, and the computability boundary.	JSON record

Current written-proof coverage

For Machine_Societies_v1.0.0.tex, the bound records cover 38 of 62 distinct pairs: 36 recorded passes, 2 requiring restrictions, and 24 unreviewed. Coverage and exact claim labels.

Restrictions and unresolved findings remain in the component evidence catalogue and finalization queue. Review coverage is not a correctness percentage, whole-book certification, or independent peer review. The finalization queue records the current maintenance priority. Scheduling does not change these verdicts.

Other dated reports

Additional registered evidence

These files include test contracts, source records, run outputs, publication receipts, and editorial assessments. Each describes its own purpose and scope.

Reading and updating a record

Identify the component and exact source edition or commit.
Read the stated claim or tested input range, environment, outcome, and limitations.
Check whether the record describes source identity, compiler acceptance, a written argument, or an experiment. These are different kinds of evidence.
Follow a later correction through its own record. Preserve the earlier result and its source binding, including failures and incomplete checks.

The collection workflow validates registered hashes, links, and generated pages. Source integrity and a green workflow do not rerun or certify every scientific claim.

Documentation · Record formats · Preserved history