PUBLIC RECORD / WORKER 2.0
Worker 2.0 Wave 1 closure record
Terminal result: WORKER2_WAVE1_STATE_BLOCK_CANARY_DEPLOYED_VERIFIED
Scope, stated narrowly on purpose. This closes the Wave 1 State Block canary only. It is not full Worker 2.0 migration, not D1 activation, and not closure of later waves.
What the record contains
- 11 code-successor repairs, each opened by an independent finding and closed by a narrow repair with permanent controls. They sit inside a 13-entry code lineage that also includes the Wave 1 base and route wiring.
- 6 execution packets. 3 were held at CHANGES_REQUIRED before anything ran.
- 2 deploy invocations and 1 rollback.
The attempt that failed
One deployment failed and was rolled back. It is kept here rather than removed, because a record that only holds successes has not been tested.
| Event | Traffic | Note |
|---|---|---|
| baseline before Wave 1 | integer 100 | COORD-0406 cybersecurity surface |
| COORD-0424 candidate deploy | integer 100 | one authorized deploy; broker refused success on a probe defect and rolled back |
| COORD-0424 exact owned rollback | integer 100 | restored the exact baseline version; one rollback, never retried |
| COORD-0426 candidate deploy | integer 100 | TERMINAL SUCCESS, zero rollback |
Verify this yourself
The machine-readable record is byte-identical to the file this page was rendered from:
- /records/worker2-wave1-closure.json
- sha256 848D703B14BB086D3E7C4348F1075B40EC89FDADA0F83CC04126C1CF56C5D592
- Bound entries: 118, each recorded as path, byte count, and digest.
Receipts are evidence, not authority. Nothing in this record grants any person or system permission to do anything. It documents what happened, including what went wrong, so a later reader can check the claim rather than take it.
For curious readers: open F12 and try article11.help() or article11.breadcrumbs().