Status & next steps
Status & next steps
The core is built. These are the remaining gaps and deferred capabilities.
Where we are
The core harness is implemented: work has durable step state, declared routes, evidence checks, a driver, and interactive and headless hosts. The remaining work concerns specific gaps in entry, approval, completion, and operational verification.
| Area | Available now |
|---|---|
| Workflow state | Manifest routes, per-node progress, a single writer, and guarded metadata. |
| Decomposition | Verified child creation, conserved coverage, and container acceptance. |
| Execution | Driver, two hosts, leases, retries, and declared resume behavior. |
| Review and delivery | Commit-bound review and proof of landing on the integration target. |
| Autonomy | Inherited levels that relax selected human gates while retaining checks. |
Checked against the repository manifest, scripts, and the system reference on 8 September 2026. This is implementation status; operational gaps below still need resolution.
What still needs resolution
| Gap | Consequence | Next decision or action |
|---|---|---|
| Spec classification | An unattended run may stop where spec generation must choose leaf or container. | Since built: the spec records its own verdict, classification: leaf | compound, and a relaxed gate follows it. See generate-spec. |
| Campaign completion | Deep mode accumulates code on a campaign branch; no final merge checkpoint is built. | Define the human checkpoint for bringing the whole campaign to main. |
| Human-only approval | The current surface does not distinguish a person’s approval from an agent action. | Provide an approval mechanism that establishes who approved. |
| Enforcement installation | A hook file and settings entry do not prove the hook runs. | Add a registration and behavior verifier. |
| Competing completion paths | The periodic PR closer can close work at review without recording the delivery proof. | Bring that close path under the landing check. |
| Entry and missing checks | Initial design remains skippable; refine-design and implement have no deterministic floor. | Wire the intended design entry and settle checks appropriate to each step. |
| Board metadata | Older work can lack step state or usable pull request links. | Audit and repair legacy records so the board reflects the work. |
| Unattended wave validation | The expected wait for a human merge has not yet been observed through a real unattended run in the system record. | Exercise and observe the full wait, merge, and resume path. |
These are remaining decisions and verification tasks, not a new committed build sequence. They should be scoped against the workflows that need them.
Deferred work
These designs remain outside the implemented core.
| Area | Intended addition |
|---|---|
| Work entering a live run | Since built: the discover verb files work a step finds mid-run and enters it through the task door. See entry doors. |
| Scheduling | An interval trigger that invokes the existing runner. |
| Artifact identity | Content hashes, revision-aware approvals, and detection of in-place edits. |
| Document lifecycle | Automatic retirement of superseded artifacts and controlled rewind. |
| Evidence and events | A common evidence-package schema, structured transition verdicts, and typed event records. |
| Handoff locking | Heartbeat and staleness handling for the brief lock. |
Implementation detail belongs in the harness reference once a mechanism ships. This list records the remaining intent.
The completed build path
The rebuild moved from entry checks and recorded classification to verified fan-out, per-node progress, recursive acceptance, and the execution engine. That sequence is now historical context.
The lab's adopted plan, build reports and findings register, kept in its own repository, retain the decisions and the original diagnosis. The incident records give the two failures that started the rebuild.