Bootstrap a new project
Start a new project from ordinary source material and establish only the project state needed for the next engineering decisions.
Use bootstrap when you are starting a project that does not yet have reliable TCAF project state.
Bootstrap organizes evidence and proposed project state. It does not implement the application.
Start from what you already have
You can start with an inline request:
tcaf bootstrap --target <project-path> --request "<starting request>"Or with ordinary project material:
tcaf bootstrap --target <project-path> --input <notes-or-specifications>README files, specifications, analyses, architecture notes, plans and roadmaps can remain exactly what they are. They are source evidence; no TCAF-specific preprocessing is required.
What bootstrap should establish
Only enough state to make the next decisions explicit, for example:
- product goal and important boundaries;
- confirmed architectural decisions;
- constraints and open questions;
- authoritative source material;
- the next planning or development step.
When separate canonical project state is useful, TCAF can derive it from the evidence. It should not duplicate adequate source documents without a reason.
Review before moving on
Check that facts are supported by the supplied evidence, uncertainties remain visible and architecture has not been invented or silently decided by the AI.
Then choose the next operation:
tcaf plan --target <project-path> --request "<broad feature or outcome>"Use plan when the next result needs decomposition. If the next unit of work is already small and clear, go directly to:
tcaf task --target <project-path> --request "<bounded change>"If working code already exists and was developed without TCAF, use Adopt an existing project instead.