The checkpoint
The recovery record names generation 157 with 1,312 nodes and 515 edges as a recovery target. Those numbers describe a specified graph checkpoint. They are separate from the July/August corpus/entity counts and the million-neuron unified-substrate figures in retained context.
The intended runtime route
The directive connects gateway, ORACLE executive, canonical state, capability-selected organs, attributed retrieval, generation, semantic verification, gated action, outcome learning and replay. It requires explicit state ownership, event/trace records, rollbacks and acceptance evidence.
Device-first order
A superseding device-recovery directive requires preserving and repairing the machines and stores before integration. It excludes the failed M2 from production dependency and protects donor/runtime state. These historical rules explain the recovery sequence; they do not authorize this website to start old daemons or mutate databases.
Unrecovered acceptance state
The expected runtime registry, deployment manifest, state ownership, acceptance results and rollback records are tracked as required artifacts, not assumed successes. No fresh fleet acceptance run was performed for this research website.