Sync project state
Re-read current repository evidence after out-of-run changes and reconcile only the smallest approved project-state update.
Use sync when project reality may have changed outside the current AI run.
Typical triggers include:
- manual developer edits;
- a new or revised specification;
- external changes;
- accepted implementation that changed documented capabilities;
- any out-of-run repository change that may affect planned work or project state.
Run sync
tcaf sync --target <project-path>
tcaf sync --target <project-path> --request "<new information>"
tcaf sync --target <project-path> --input <new-specification-or-material>A request or input is evidence to inspect, not automatically approved project truth.
First pass: inspect and propose
Sync re-reads the current repository and relevant project evidence. It identifies:
- material drift;
- planned tasks that may be affected;
- conflicts or unresolved information;
- the smallest useful reconciliation.
The first pass is read-only. It preserves developer changes, completed history and unresolved conflicts.
Apply only an approved update
If reconciliation is appropriate, approve a sufficiently identified and bounded update set. Without current approval, sync must not write or overwrite developer work.
Typical approved changes can include project state, capability records, backlog status or other canonical evidence. Application implementation is a different operation.
Sync does not implement features
When sync discovers new implementation work, send it through tcaf plan or a separate tcaf task as appropriate.
After an accepted task, sync can also reconcile documentation and planned work with the accepted repository state. This is one use case of sync, not its only use case.
Validate updated project documents when appropriate and review the actual diff before acceptance.