Verify It Works

Finish the Control Panel with final verification, approval, and a durable release record. I should be able to inspect the result, approve the version that passed, and reopen its files and report later.

Check The Finished Application

After the last stage, keep the run in running while final verification executes. Rerun baseline checks, health checks, final acceptance commands, and every stage's script gates. These must remain valid on the finished application. Record new evidence and retain earlier results.

Review The Requirements

Use a fresh read-only reviewer with the master plan, stage requirements, final diff, and check results. Ask for missing behavior, disconnected components, and weakened tests. Preserve the verdict and its supporting findings.

Stop On Unresolved Results

A failed or unavailable check, invalid review, or unresolved finding moves the run to waiting_review. Final verification does not open another automatic repair loop. Preserve the failure for a deliberate correction and Recheck.

Prepare A Candidate

Once verification passes, stop all writers and copy the checked files into candidate storage outside agent workspaces. Record the manifest, content hash, base commit, final checkpoint, and diff. Set waiting_review with a final_approval reason and a new decision id.

Show The Evidence

Display requirements, changed files, check results, review findings, repairs, and limitations beside the candidate. Link to full logs. Show its artifact reference next to Approve, and distinguish final approval from an earlier stage gate.

Record Final Approval

Accept the final approval, requiring the decision id, artifact reference, and reviewer name. Confirm the evidence and current files match the candidate. Save the approval and timestamp, leaving the run waiting for Release. Reject a stale or repeated decision.

Invalidate Changed Work

Recompute the workspace manifest at approval and release. Any changed, added, or deleted deliverable invalidates the candidate and approval, even without a new commit. Record the mismatch, clear release readiness, and refuse the release as a conflict.

Verify Again After A Correction

Recheck repeats final verification and creates a new decision requiring fresh approval. Preserve old candidates as history. Restoring earlier file contents must not reactivate an invalidated approval. Missing or skipped required checks continue to block release.

Release The Approved Files

Accept a release request with the candidate and approval ids. Lock execution, confirm no writer is active, and validate the state, current files, candidate hash, evidence, and approval. Release the stored candidate the engine already checked.

Keep Release Local

Label the action “Release locally.” It records the approved result and exposes its files, patch, and run branch. Merging, pushing, and deploying are separate actions.

Save Completion Atomically

Write one release record and set completed in the same SQLite transaction. Include the candidate, commits, approval, verification attempt, evidence references, and completion time. A failed write leaves the run uncompleted and available for retry.

Repeating the same successful release returns its existing record. An incompatible candidate or state stops the release with a conflict. Serve downloads by stored artifact identifiers and retain the released files.

Generate The Report

Build the run's report from the persisted records. Include the objective, frozen revision, artifacts, stage outcomes, attempts, checks, decisions, elapsed time, and release or failure reason. An incomplete report should identify the outstanding work.

Report Usage Honestly

Show reported token counts and sourced costs. Label incomplete totals as partial and missing figures as unavailable. Mark simulated runs clearly and keep them ineligible for a normal release. Model-written explanations must link back to evidence.

Copy A Debug Brief

Add a Copy Debug Brief action backed by an endpoint that assembles the brief. Include the requirement, workspace, artifact, current operation, failed checks, relevant output, attempted repairs, and next decision. Link the full logs and offer selectable text if copying fails.

Demonstrate The Full Path

Provide a small fixture repository with independent tests. A suitable pipeline implements saving ordered steps to SQLite, then adds updates while preserving earlier behavior. Run it through the editor, a real agent, verification, approval, and local release.

Restart the panel and reopen the report. Follow the generated project's setup in a fresh directory and run its acceptance tests. Record the observed results and any unfinished verification.

Check Release Failures

Try missing approval, edited files, unavailable checks, exhausted repair, an interrupted worker, and a failed release write. None may produce a completed run. Concurrent release requests must create only one record.

Check the browser flow, reloads, keyboard access, and narrow layouts. Update the README and knowledge base with setup, agent configuration, checks, and remaining limitations.

September, 2026