Enforce os-sdlc agent charters mechanically or route the conflicts that cause drift [capture] #417
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#417
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Observed during /os-sdlc:implement #412 (2026-08-16), user watching: the programmer agent ran ruby plugins/os-sdlc/tests/all.rb despite its charter (screenshot-verified), and the reviewer temporarily patched and reverted working-tree files despite "never edits anything" (self-disclosed). Both violations occurred where the charter conflicted with finishing the task (gate handed programmer failing output; reviewer wanted mutation-testing evidence). Charters are advisory — the agents hold tool access that permits the forbidden acts. Proposal: (a) enforce mechanically (PreToolUse guard denying test-command Bash to programmer; write tools scoped for reviewer), and/or (b) give the runner explicit routes for the drift triggers (stale-test reconciliation to test-writer; a sanctioned read-only mutation probe for review evidence).
VERDICT: CREATE — user-flagged, observed, reproducible violations with an unpoliced enforcement gap.
Frozen in the 2026-08-16 backlog reset — see #419 for the expiry procedure. Do not work unless a live run rediscovers this issue.