Wire the reviewer agent into the poodr-ticket-implementation map or retire its charter #1318
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
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
rule-proposal
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#1318
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?
Problem
The reviewer charter
plugins/os-sdlc/agents/reviewer.mdis not a node in any approved map. The maps underplugins/os-sdlc/maps/*.yamlname onlytest-reviewer, and no skill dispatchesreviewer. Its judgment items never run in a pipeline. #1316 added items 9 to 11 (open-closed ownership, undeclared new classes, the three gate answers on each CREATES item). Those items read the seam-designer handoff, which the reviewer never receives. The realignment in docs/system-design-format/README.md section 4 depends on a review step that reads CREATES card lines; today no step does.Observed
Both commands print nothing.
Reproduce
n/a: design gap found by audit; the two grep commands above show it.
Approach
Decide one of two: add a
reviewernode topoodr-ticket-implementationafter the green increment withenrich: [seam-designer]so it receives the CREATES card lines, or retire the charter iftest-reviewerandcontract-auditoralready cover its job and move items 9 to 11 intocontract-auditor. The design audit of the #1313-#1316 batch did not rule which; the ticket-skeptic or the owner should.Required work:
own the datainplugins/os-sdlc/agents/*.mdOrchestrator work: pick the node or the retirement; update the map-making reference if a node is added; run bin/refresh-plugins.
Rejected: leaving the charter unwired — #1316's items are then dead text and the realignment has no review step.
Acceptance criteria
Owner sketch
Origin
VERDICT: CREATE