36 lines
1.5 KiB
Markdown
36 lines
1.5 KiB
Markdown
# Action-aware constraint pilot v2 amendment
|
|
|
|
Status: **FROZEN AFTER V1 CONTROLLER STOP AND BEFORE V2 GPU RUNS**.
|
|
|
|
Date: 2026-07-14 (Asia/Singapore).
|
|
|
|
The V1 configuration matrix and every scientific gate remain unchanged. V2
|
|
fixes one controller bug and reruns every configuration and repetition fresh.
|
|
|
|
## V1 controller failure
|
|
|
|
The MNS64/MBBT2048 burn-in completed all 510 requests in 61.259 seconds, below
|
|
the frozen 90-second operational limit. However, the controller accidentally
|
|
assigned the preceding 16-request warm-up result to `burnin_result`; its state
|
|
therefore recorded 4.376 seconds and evaluated the wrong object.
|
|
|
|
The first measured replay was terminated after 75 seconds, before it produced
|
|
a result. No target configuration had started. V1 consumed
|
|
0.3184109431 H20-hours and contributes no action label or telemetry to V2.
|
|
|
|
## V2 correction and regression gate
|
|
|
|
- The completed burn-in `run_client()` return value is assigned to
|
|
`burnin_result`.
|
|
- A dedicated `burnin_gate()` rejects any non-anchor object, any request count
|
|
other than 510, and elapsed time above 90 seconds.
|
|
- Unit tests explicitly pass a warm-up object and require rejection, then test
|
|
accepted and over-limit burn-ins.
|
|
- All five configs and 15 measured runs use a new run root; no V0/V1 runtime
|
|
artifact is reused.
|
|
|
|
V0 and V1 together consumed 0.7043978426 H20-hours. V2's incremental hard cap
|
|
is therefore 7.2956021574 H20-hours, preserving the original global 8.0
|
|
H20-hour cap. The authoritative accounting file is
|
|
`runs/action-aware-v0/prior-attempts-v2.json`.
|