18 / Verify, protect, and record

Finish With a State the Next Agent Can Trust

The work is not durable if the next session has to reconstruct scope, files changed, checks run, unresolved risks, permissions, and the next action from a long chat transcript.

Failure mode

The agent acts from stale memory, loads unrelated guidance, assumes a source exists, silently resolves contradictory instructions, applies a reference brand literally, or declares completion from one narrow check.

Applied correction

Update the project’s current-state record and finish with one exact next action plus any approval required.

Field test

Does the handoff reflect actual repository state and verification rather than a conversational summary? Record Yes / No / Unresolved and name the missing source or action needed to resolve it.

Ask your agent

At completion, report files changed, behavior preserved, decisions made, checks run/results, unresolved risks, production-only verification, permission boundaries, and one next exact action. Update the project’s established progress/handoff record when authori