R12 SD-CST Complete Physical Fresh-Board v1.3 Preregistration

Status: implementation and evaluator regression coverage complete before source freeze, board seed, training seed, or scored access.

Claim class: bounded fresh renderer/name compilation into the retained source-deleted categorical executor. Passing is not broad natural-language or general reasoning.

1. Reason for v1.3

Fresh-board v1.2 completed both frozen fits and one development compilation, but its pilot failed while assembling the report. fit_arm returns renderer metrics under train_metrics; the frozen helper incorrectly iterated the entire fit mapping, including integer metadata. The checkpoint, hard packets, pointer evidence, and source-blind executor outputs were preserved, but no frozen report or independent assessment was produced. Development access is 1/0, confirmation remains sealed, and that board is permanently ineligible for rescore or confirmation.

A read-only post-hoc diagnostic over only those preserved source-free artifacts found 2,048/2,048 exact treatment packets, pointers, final states, and answers across all four unseen renderer compositions; the matched family-deranged arm had 0/2,048 exact packets and 131/2,048 exact states. This is motivation, not an authorizing score.

V1.3 changes only the report aggregation path and schema/protocol identities. The helper now validates and reads fit["train_metrics"]. A realistic nested- fit regression test and a complete synthetic checkpoint/config/packet/ evidence/executor/ledger assessor test must pass before source freeze. All architecture, data, arms, optimization, thresholds, controls, and claim boundaries remain unchanged. A new source commit, board seed, board, and training seed are mandatory.

2. Fresh board and custody

After source freeze, one independent board seed generates:

• 12,000 latent training programs x four views = 48,000 rows;
• 512 disjoint development programs x four views = 2,048 rows; and
• 512 disjoint sealed-confirmation programs x four views = 2,048 rows.

Training uses four even-parity combinations of two declaration, two event, and two query renderers. Development and confirmation use the four odd-parity combinations. Opaque names, operation sequences, and latent families are split disjoint. All exact prompt, 13-gram, name, and operation-sequence overlap gates remain zero. Every row must independently parse and simulate, contain exactly nine bounded physical records and one HALT, and satisfy the 144-byte record/query limits. Board admission executes the production parser over all 52,096 rows. Confirmation is mode 0600.

The checkpoint and immutable gate config are written before an O_EXCL development ledger. Development may be opened once only after both arms finish. Confirmation stays at zero unless a separately committed authorization follows a complete development report and independent assessment.

3. Frozen system contract

The endpoint reconstructs hash-bound joint, physical-record, complete-local v1, and occurrence-head v1.2 parents. Treatment and matched control train the same 102 tensors and 12,152,855 parameters: the physical record encoder/decoder, local query path, and nonlinear occurrence head. Every inherited global path, obsolete declaration path, exact packet executor, motor, reader, and Shohin trunk remains frozen.

No parameter may be added after source freeze.

4. Arms and optimization

Treatment receives true compiler fields. The equal-parameter control receives one deterministic nonidentity three-cycle of entity roles per latent family; all four renderer views share that false mapping. Both arms share exact initialization, rows, family minibatch order, optimizer, schedule, updates, and parameter count.

Each arm trains two epochs / 3,000 updates with family batch eight (32 rendered rows/update), AdamW lr 2e-4, betas (0.9, 0.95), weight decay 0.01, warmup 100, cosine decay, gradient clipping 1.0, and renderer consistency weight 1.0.

5. Source deletion and independent assessment

The compiler emits 25 categorical program bytes plus one query byte. Source tensors are poisoned after packet sealing. A separate process receives only hard packets and the hash-bound categorical execution core. The pilot emits checkpoint, immutable config, hard packets, pointer-range evidence, and executor outputs. The separate assessor recomputes packet, pointer, state, answer, renderer, executor, control, hash, parameter, and custody gates.

The matched controls remain family-deranged labels, uniform packet, shuffled packet, reset, freeze, post-HALT perturbation, force-alive after HALT, query rotation, and initial/kind/identity/amount interventions.

6. Immutable development gates

All gates must pass:

1. treatment minimum fit-renderer packet at least 99%;
2. development packet at least 90% overall and 85% per renderer;
3. development state, answer, and joint each at least 90% overall;
4. development joint at least 85% per renderer;
5. each packet field at least 95% overall;
6. each line/binding/initial/event pointer at least 90% overall;
7. treatment packet at least +50 points over family-deranged labels;
8. family-deranged packet at most 25%;
9. gold and conditional execution exact;
10. post-HALT perturbation invariant;
11. shuffled-packet state at most 35%;
12. reset and freeze state each at most 75%;
13. source deletion and separate execution pass;
14. frozen state is byte-identical;
15. complete deployed system is strictly below 200M; and
16. development/confirmation access is exactly 1/0.

Passing both pilot and independent assessment yields authorize_one_sealed_confirmation. Any failure yields reject_complete_physical_fresh_v1_3; no threshold repair, rescore, extra epoch, or confirmation read is allowed on that board.