Skip to content

fix(skills): refuse a top bead that names work no bead carries - #106

Merged
GraemeF merged 2 commits into
mainfrom
worktree-yard-ux4b
Oct 26, 2026
Merged

GraemeF merged 2 commits into
mainfrom
worktree-yard-ux4b

Conversation

@GraemeF

@GraemeF GraemeF commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

A top bead could name a switch, a check or a post in prose with no bead behind it. The push gate walks only the graph, so that work was never staffed and lived only in a steward's context.

The bar now requires a bead for each piece of work the top bead's description names, except seeing the evidence that closes the top bead itself. Muster's readiness gate and its adversarial review check for it, and the steward's push gate reads the description against the graph before it walks the strands.

A top bead could name a switch, a check or a post in prose with no bead behind it, and the work stayed invisible because the push gate walks only the graph. The bar now requires a bead for each piece of work the top bead names, and muster's readiness gate and the steward's push gate both check it.
@GraemeF
GraemeF marked this pull request as ready for review October 26, 2026 14:36
@GraemeF
GraemeF merged commit 795be85 into main Oct 26, 2026
2 checks passed
@GraemeF
GraemeF deleted the worktree-yard-ux4b branch October 26, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant