Repository navigation
CLAUDE.md: the tracker push follows the family shape - #41
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
bd dolt pushrow in the CLAUDE.md authority table read "the operator's call" as its trigger and "inside a campaign that spans mirrored trackers - the conductor pushes those atomically" as its limit. It now reads, as ruled by the operator, 2026-09-29, in the shape statifier-ex's row already uses: the trigger is "bead state changed locally and the git side of the same change has already reachedorigin; inside a campaign, the conductor pushes (atomically across the campaign's trackers)", and it stays unauthorized "as a way to publish beads for work that is not onorigin/mainyet". Review, done in turn before opening: the new row is the bead's acceptance text byte for byte; it grants nothing beyond that ruling (the campaign push stays the conductor's, and no merge, close, release or publish row moves);git diff --stat origin/mainshows one file and one line changed (one insertion, one deletion), so every other row is byte-identical; a grep of the file fordolt pushfinds no other sentence restating the tracker-push rule. No gate runs: the change touches no Elixir code and no path ingate.also_gated_paths. No changelog fragment:changelog.d/README.mdexcludes agent tooling.