From 425e2c1a9001f4cb13958856dd4c2b3d9a2df62e Mon Sep 17 00:00:00 2001 From: JohnnyT Date: Tue, 29 Sep 2026 06:40:57 -0600 Subject: [PATCH] CLAUDE.md: the tracker push follows the family shape The bd dolt push row moves from "the operator's call" to the shape the family's other packages use: a push once bead state changed locally and the git side of the same change has already reached origin; inside a campaign, the conductor pushes, atomically across the campaign's trackers. It stays unauthorized as a way to publish beads for work that is not on origin/main yet. Ruled by the operator, 2026-09-29. Every other row is unchanged. --- CLAUDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 2485731..348d743 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -60,7 +60,7 @@ irreversible step, and report. | `git push`, `gh pr create` | the same consent, **and** the terminology scan in the umbrella's `docs/terminology-firewall.md` clean over the full outbound content | any scan hit - that is a hard stop, not something to rephrase past | | merging a campaign PR | a campaign consent the operator adopted verbatim that names automatic merges, with every named condition met (full gate green, CI green, firewall scan clean with a positive control, any named review gate passed) | outside such a consent; any named condition unmet; any PR the consent's carve-outs hold for the operator | | `bd close ` | never for a mirrored bead whose other half is not merged to its own repo's `origin/main`; a mirrored bead whose other half has ALSO landed may be closed by the campaign conductor under a consent naming this exception, both halves together, each verified against its remote; otherwise the operator's call | for a bead whose description carries a `mirrors:` line while its other half is unlanded, campaign consent included | -| `bd dolt push` | the operator's call | inside a campaign that spans mirrored trackers - the conductor pushes those atomically | +| `bd dolt push` | bead state changed locally **and** the git side of the same change has already reached `origin`; inside a campaign, the conductor pushes (atomically across the campaign's trackers) | as a way to publish beads for work that is not on `origin/main` yet | | a release prep (a version bump and a changelog promotion) and its tag | a release bead the operator has named (in the campaign plan or their own words); the tag once that prep is merged to `origin/main`, naming its version at the merged commit | on any other bead or on `main`; the tag before the prep is on `origin/main`; always for the publish and the release itself | The organizing principle is the same one the other packages use: the human gate