Skip to content

Commands

Campaign commands are subcommands of the architecture bin (see the CLI). check also verifies every campaign against its ledgers, and explain <file> shows a file’s sector, phase and each objective’s result.

Command What it does
campaigns status table: progress, owner, stalls, phases, per-objective burn-down
campaigns status --changed the nudge for the current diff
campaigns attest record that a sector passed an attested phase
campaigns note leave a remark on a sector for the next person
campaigns history the ledgers’ git history, one row per commit
objectives clear reconcile the ledgers with the code
objectives concede record why a count may rise

Every command takes optional roots to walk after its arguments. campaigns clear and campaigns concede are aliases for the objectives verbs. campaigns init, prune and allow were removed and are refused with a pointer to their replacement.

Where a command records an author, it uses --by <email>, else git’s user.email, else GIT_AUTHOR_EMAIL. attest, note and concede fail without one.

$ architecture campaigns
1 campaign under packages
lowering-reports-not-throws 21% 15 left @dataquail
throws-in-lowering 21% 15 left 4 cleared 2 conceded
Terminal window
architecture campaigns status --changed [--base <ref>] [--json] [--hotfix "<reason>"] [--by <email>]
Flag Meaning
--changed required
--base <ref> compare against this commit instead of the ledger and HEAD
--json print the JSON document
--hotfix "<reason>" concede growth ratchet or paydown would refuse; verdict becomes hotfix
--by <email> author of the hotfix concession

Exits non-zero when any sector’s verdict is back or no-paydown.

Terminal window
architecture campaigns attest <sector> <phase> --reason "<why>" [--evidence <url>] [--by <email>] [--campaign <id>]

--reason is required. Accepted only while the sector is at that phase. Run objectives clear afterwards to move the sector on.

Terminal window
architecture campaigns note <sector> "<text>" [--by <email>] [--campaign <id>]

attest and note need --campaign <id> when the policy declares more than one campaign.

Terminal window
architecture campaigns history [<campaign>] [--since <ref>] [--json]

Walks the git history of the ledgers and manifest from --since <ref>, one row per commit. Without <campaign>, covers every campaign.

Terminal window
architecture objectives clear [<campaign>[/<objective>]] [--by <email>]

Reconciles every ledger, or just the one named: removes holdouts that stopped firing, rewrites drifted ones, records sectors entering a window, closes sectors leaving one, re-baselines after a phase concession, and writes each sector’s reached and the plan. It never adds a holdout. For a scalar objective, it records an improved value.

Terminal window
architecture objectives concede <campaign>[/<objective>] --reason "<why>" [--sector <name>] [--holdouts a,b] [--by <email>]
Flag Meaning
--reason required
--sector <name> only this sector
--holdouts a,b only these holdouts; the rest still fail. Alias --entries. Not for scalars
--by <email> author

Name the objective when the campaign has more than one. For a scalar objective, concede records the rise as { from, to }.