Reconcile project status

Reconciliation updates project evidence after implementation has been reviewed and accepted. It prevents documentation, backlog and repository state from drifting apart.

Start from accepted evidence

Use:

• the approved Task Contract;
• the final implementation diff;
• checks actually executed;
• limitations and pending verification;
• developer acceptance;
• any manual changes made before reconciliation.

Do not reconcile from the agent’s initial plan or an unreviewed result.

Typical updates

• mark accepted backlog work complete;
• record remaining work separately;
• update capability or architecture descriptions when behaviour genuinely changed;
• add decisions and validation evidence;
• correct status summaries;
• preserve historical entries and superseded decisions.

Separate scope

The reconciliation Task Contract should normally authorize only canonical documents, backlog records and status files. Application code remains outside scope.

If reconciliation reveals that implementation is incomplete or incorrect, stop and return to a development task rather than editing code inside the documentation step.

Validate and review

Run:

tcaf validate --target <project>

Then review the documentation diff against the accepted result. A passing validation confirms consistency rules, not the truth of unsupported claims.

Completion

Reconciliation is complete when current documents accurately describe accepted repository state and remaining work is still visible. Commit remains a separate authorized operation.