Context Circuit
Concepts

Completion and reconciliation

Record the result and make the next change start from accurate knowledge.

Template 2.5.0CLI 2.5.0

Two parts of one request

When a person marks a plan complete, the CLI appends their note and stamps completed_at. It returns catalog candidates scoped to the plan's repositories as reconcile_required when applicable.

The agent compares those notes with the actual change. It updates affected notes and catalog entries together, including their reviewed dates. If no durable concept changed, it reports that explicitly. Recording a timestamp alone does not finish the request.

Complete against real work

The plan is intended work; the branch and diff show what happened. Complete only when the work has actually landed. Dependency ordering uses completion to release dependents. Reconcile several completed plans across their combined effect.

Borrowed knowledge remains read-only and is not a local obligation. Worktrees and branches remain after completion; removing them needs a separate request.

Commit, then offer to archive

record complete also returns commit_recommended when the plan's files, its intent's file, or the ID files are uncommitted. The agent asks one question: commit and push those files, or commit only. While you have finished records not archived, the result also carries archive_offer, and the agent offers to archive them. Archiving is optional: record archive moves your own finished records under _archive/, keeps every ID reserved, and returns its own commit_recommended. Declining the offer changes nothing.

Follow complete plans and update knowledge.

On this page