From 6af2ccbd5174c0832a11510dcb140fca206e7a38 Mon Sep 17 00:00:00 2001 From: YurenHao0426 Date: Mon, 27 Jul 2026 15:07:11 -0500 Subject: experiment: make ResNet 27-cell R2 executable --- RESNET_CROSSOVER.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'RESNET_CROSSOVER.md') diff --git a/RESNET_CROSSOVER.md b/RESNET_CROSSOVER.md index 126c051..ee1b28e 100644 --- a/RESNET_CROSSOVER.md +++ b/RESNET_CROSSOVER.md @@ -110,6 +110,23 @@ and its manifest records the resolved physical UUID. Formal launch occurs from a detached worktree so unrelated main-branch commits cannot mix revisions inside a shard. +The R2 executable contract is +`experiments/resnet_crossover_r2.py`. It refuses any selector that is not the +complete 19-record P1 pass, requires the selector itself to be committed, +binds its hash and selected rates into a new clean-source launch lock, and +materializes all 27 method--depth cells before sharding. The two shards +interleave EP, Dual Propagation, and Forward--Forward rather than assigning all +expensive state methods to one GPU. +`experiments/analyze_resnet_crossover_r2.py` requires every manifest, retains +timeout/nonfinite outcomes, rejects test access and +source/split/architecture drift, and checks method-specific presentation, +relaxation, local-VJP, and logical-query counts. The registry and schedule can +be checked before P1 finishes with: + +```bash +python experiments/resnet_crossover_r2_smoke.py +``` + ## R3 untouched confirmation No R3 test endpoint opens until all 27 R2 records and the complete analyzer -- cgit v1.2.3