One policy file
blueprint/config.json contains deterministic workflow settings shared by every
installed adapter. It is user-owned, so Blueprint updates preserve it. A missing
file uses the built-in defaults.
Read-only status reports invalid configuration and falls back safely. Commands
that change project state stop and point to /doctor instead of guessing.
Available settings
| Setting | Allowed values | Default |
|---|---|---|
workflow.stepReview |
every, feature |
every |
workflow.checkpointCommits |
enabled, disabled |
enabled |
git.featureBranchPrefix |
lowercase prefix ending in / |
feature/ |
git.fixBranchPrefix |
lowercase prefix ending in / |
fix/ |
git.rollbackBranchPrefix |
lowercase prefix ending in / |
rollback/ |
verification.logicTests |
when-configured, required |
when-configured |
verification.uiEvidence |
when-available, required |
when-available |
qualityGates.regular.audit |
manual, when-sensitive, always |
manual |
qualityGates.regular.check |
manual, when-behavioral, always |
manual |
qualityGates.regular.tryGuide |
manual, when-user-facing, always |
manual |
qualityGates.continuous.audit |
manual, when-sensitive, always |
manual |
qualityGates.continuous.check |
manual, when-behavioral, always |
manual |
qualityGates.continuous.tryGuide |
manual, when-user-facing, always |
manual |
continuous.maxFeatures |
positive integer or null |
null |
continuous.maxRepairAttempts |
integer from 0 through 10 |
2 |
continuous.finalIntegrationAudit |
true, false |
false |
Quality gate modes
All audit, check, and try-guide gates default to manual, so nothing runs
automatically only because configuration exists.
when-sensitiveaudits work involving security boundaries, user data, payments, secrets, migrations, destructive operations, external effects, or unusually broad changes.when-behavioralchecks work that needs observed runtime behavior, such as a click, request, download, command, or multi-screen flow.when-user-facingcreates a manual try guide for UI, CLI, public API, output, and other workflows a person directly uses.alwaysapplies that gate to every work item in the selected workflow.
qualityGates.regular applies to the normal workflow and Autopilot.
qualityGates.continuous applies to each feature in Continuous Mode.
Boundaries configuration cannot change
Configuration never grants permission to commit, merge, push, deploy, publish, send, delete data, waive a failed check, or accept a finding. Those actions keep their normal approval and safety gates.
Commands stay in AGENTS.md, communication preferences stay in
blueprint/context/ai-interaction.md, and installed-version metadata stays in
blueprint/.state/manifest.json.