Choose during onboarding
Onboarding asks whether Blueprint workflow files should be committed or kept local. Committing them gives collaborators and future machines the same context. Local-only mode keeps that state on one checkout.
What to ignore
Local-only mode adds the Blueprint workflow paths to .gitignore:
# AI Blueprint local workflow files
.agents/
.claude/
blueprint/
CLAUDE.mdAGENTS.md stays tracked as the lightweight public project guide for commands and conventions.
Ignoring blueprint/ also keeps the installed version and managed-file baseline in blueprint/.state/ local to this checkout. In committed mode, keep blueprint/.state/manifest.json tracked while its nested .gitignore excludes backups and staging files.
Tradeoffs
| Committed workflow | Local-only workflow |
|---|---|
| Portable context and shared history | No workflow files in the remote repository |
| Reviewable changes to plans and standards | Each checkout needs separate setup |
| Easier cross-tool and cross-machine continuation | History can disappear with the working copy |
Local-only mode changes storage, not safety. Commit, merge, push, deployment, and external-action boundaries still apply.
Independent review
Independent review supports ignored specs through an exact local snapshot. Application code stays in the approved checkpoint; the spec and snapshot stay ignored and untracked. The reviewer must use the same local files, with a fresh session in the original checkout when automatic access is unavailable. See Audit.
This does not make local history portable. Rebuild and rollback selection still need proven archive commits; ignored history without that proof cannot establish an earlier build or reversal.