Round r73

r73 proper shaping

Status · INCOMPLETEReviewed status is transcribed from rounds/STATUS.md. The original narrative and its qualifications remain below.

Source-reported narrativeRound README and results text are source material. Numeric values that are not tied to a claim ledger record remain source-reported.

Round source README · rounds/r73/README.md

Round date: HISTORICAL (before 2026-10-09) Publication badge: INCOMPLETE; KEPT FOR AUDIT Why not VALID: The historical inventory retains INCOMPLETE because of NOT_RUN, NO_OUTCOME. See the round evidence and limitations below. Recomputation status: OBSERVED SOURCE ONLY

Recomputation limit: Published summary figures: planned/observed counts, outcome totals/rates, and numeric estimates as present in README.md and RESULTS.md. These figures cannot be recomputed from repository inputs because no public per-round analysis script with a complete, identified input bundle is published. See the round README, MEASURED.md, and MISSING.md for recorded scope and gaps; historical execution inputs/toolchains/grading are not bundled.

Status

INCOMPLETE

  • NO_OUTCOME — The registered scored phase has executed n = 0.
  • NOT_RUN — No outcomes or scored cells are recorded in the public export.

Required reproduction metadata

  • Kogen commit: not recorded in the cited round source.
  • Harness commit: not recorded in the cited round source as a Git commit; any adapter or runtime fingerprints are not Git commits.
  • Model and effort: a complete per-cell mapping is not recorded in the cited round source; values present in the source summary remain as stated above.
  • Task IDs: not recorded in the cited round source.
  • Historical execution command: not recorded in the cited round source.
  • Raw records: the cited sources do not provide a complete public round-specific request and grade bundle; public delivery and outcome exports are linked above where applicable.

Terminology: public round glossary.

STATUS: INCOMPLETE

Data completeness: N/A (0 deliveries; NO DELIVERED DATA). Measurement contract; declared gaps.

Pre-registered: yes Label: CONFIRMATORY Question: Does Sol shaping with the ledger, probes, prototype checks, lint and auditor raise Build success after approval versus Sol shaping alone? n: Planned 9-cell screen and 144-cell confirm round, plus one conditional 144-cell extension under the frozen decision rule; executed scored n = 0 and no outcome exists. Headline: The decision rule is frozen; no r73 outcome is recorded in the current public export.

Sources: frozen decision rule.

Public delivery and outcome reconciliation

No standard scored benchmark cells are attributed to this round in the public export. The planned counts, executed scored n = 0, and absence of outcomes are stated above.

Captured run records

Standard-schema records assigned to this round in the indexed snapshot.

No per-round file is listed. Check the run-record index for the complete partition list.

Reproduction inventory

Published analysis replay and full experiment replay are reported separately.

Replay type
unavailable
Script
No per-round analysis script is published.
Inputs
No identified public input bundle.
Full execution replay
Unavailable
Scope
No public per-round analysis script with a complete, identified input bundle is published. See the round README, MEASURED.md, and MISSING.md for recorded scope and gaps; historical execution inputs/toolchains/grading are not bundled.

View the complete per-round reproduction inventory · Repository reproduction guide