Adoption only
Stop after documenting and validating an existing project without starting implementation.
Content: completeWorkflow: verified
Use adoption only when the immediate objective is to make an existing repository understandable and ready for later TCAF tasks, not to change the software now.
When this path is appropriate
Choose it when you need to:
- establish canonical project documents;
- record the actual architecture and capabilities;
- map an existing backlog or issue source;
- identify limitations and unknowns;
- prepare the repository for later work;
- pause before selecting the first implementation task.
Run:
tcaf adopt --target <existing-project>Required stop point
The adoption result must stop after documents, review and validation. A discovered bug, missing test or architectural weakness does not automatically become implementation scope.
Record collateral findings in the appropriate document or backlog source. Open a separate Task Contract only when the developer chooses to act on one of them.
Acceptance checklist
Adoption-only is complete when:
- canonical documents describe the repository as found;
- implemented, planned and unavailable capabilities are separated;
- no application code or dependencies changed;
- collateral findings are recorded without being fixed opportunistically;
tcaf validate --target <existing-project>passes;- the developer has reviewed and accepted the documentation.
Commit and push remain separate actions requiring explicit authorization.