Delivery profile
| Key | Shape | Setup value or absent behavior | Purpose |
|---|---|---|---|
profile |
"prototype", "standard" or "extended" ("enterprise" is retired since 3.12.0 and is read as standard, said out loud) |
Setup asks; absent means extended from 3.49.0 (standard before), and /devstride:doctor reports it as key absent, shipped default |
The repository’s default delivery profile. "extended" (from 3.6.0) is standard with fewer, larger leaves: only leaf size, spec depth, understand readers and review breadth move; every safety knob and floor is standard’s. A plan root’s Delivery profile: marker overrides it for that plan, and a bare profile word in a skill’s arguments overrides both. |
profileOverrides |
object of knob → value | absent | Pins individual profile knobs for every profile, for example {"maxLocalReviewRounds": 2, "reviewBreadthCeiling": "HIGH-RISK"}. Keys are the knob names from the profile contract and values use its vocabulary. The knobs you can pin are grain and specDepth (each takes another profile's name, so "specDepth": "extended" slices at your profile but writes extended-depth specs), understandReaders (0 to 6), reviewBreadthCeiling, verificationDefault, verificationGrouping, fixFloor (p1-security, likely-important or all-confirmed), localCliEngine, maxLocalReviewRounds (capped by the two-cycle review target, and never a limit on the extra cycles a serious finding opens), storyVerify (touched or full), perStoryPullRequest, releaseCiOrdering, reviewerRegistrationWindowMinutes, pollTimeoutMinutes and autoRelease. A dedicated key elsewhere in this file (epicIntegrationBranches.autoRelease, epicIntegrationBranches.fastStoryMerges.enabled, review.pollTimeoutMinutes) beats an override of the same knob. fixFloor, storyVerify and understandReaders carry the rigor of the retired enterprise profile: on top of extended, {"fixFloor": "all-confirmed", "storyVerify": "full", "maxLocalReviewRounds": 2, "understandReaders": 6} with review.pollTimeoutMinutes: 20 reproduces every former enterprise knob except its grain. verificationGrouping accepts "per-file" (the default everywhere) or "per-finding", which restores one verifier per finding at the widest review breadth; the default groups findings one verifier per file-group, and a security finding is always verified singly either way. An override cannot go below a floor; targetAdversarialCycles is a fixed two-cycle floor rather than an override key, and an attempt to set it is reported and ignored, as is an unknown knob name. |
Four profile knobs also exist as keys of their own elsewhere in this file. A key that is present is the operator’s decision and always wins; the profile fills in only when the key is absent, and setup writes each key consistent with the profile it was told so a fresh config and its profile agree.
epicIntegrationBranches.autoRelease— when absent,prototypesuppliestrueand the other profilesfalse; setup writes the same.epicIntegrationBranches.fastStoryMerges.enabled— when absent ortrue,prototyperuns fast mode whenever an integration branch exists; a presentfalsewins and is reported. The other profiles follow the key.review.pollTimeoutMinutes— when absent, the profile supplies 5 minutes (prototype) or 10 (standardandextended); setup writes the same.review.openPullRequestsAsDraft,review.readyForReviewReleasesCi,review.ciHeldUntilReviewSettled— these describe what your workflows support, not what a profile does with it. Review first and CI last is a floor under every profile,prototypeincluded; setup writes all three as detected facts.
review.localCommand is different: it names the local CLI reviewer, it does not schedule it. A present command puts the engine on the roster, and it reviews every release pull request and every pull-request-path item under every profile — never a fast-merged item with no pull request. The profile decides only how many rounds it gets at those boundaries: one under prototype, standard and extended; profileOverrides.maxLocalReviewRounds raises it. null removes the engine everywhere.
/devstride:doctor reports the effective profile, its source, and any key that contradicts it — for example a prototype profile beside autoRelease: false, which is honored as configured and reported.