Design the first official os-sdlc map and agent configuration (grill-with-docs session) #453
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#453
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
The shipped maps/coding.yaml is a draft example, not built around the real workflow: it has only programmer and reviewer nodes, leaving code-probe, seam-designer, test-writer, lint-fixer, and wiring orphaned from the map runner (audit 2026-08-21). The user wants a dedicated /grill-with-docs session to design the first official map and agent configuration: map the real workflow (code-probe → seam-designer → test-writer → programmer → wiring → reviewer), give each in-map agent the YAML stop-message handoff contract, and realign or retire the orphaned agent files.
Tasks
Origin
Requirement from the #467 first drive (skeptic MERGE-INTO ruling): the official map design must route lint-gate offenses in TEST files. Today the lint gate lints all changed files including tests, but programmer/programmer-repair may not edit tests and no lint-fail edge reaches test-writer — a test-file offense loops programmer-repair to bound exhaustion (O7, docs/os-sdlc-rebuild/poodr-map-first-drive.md). The drive fixed the offenses via a disclosed out-of-map deviation. Options to weigh in the design session: test-scoped lint exclusion, a lint-fail edge to test-writer, or a dedicated lint-repair role.
Resolution
Done: Superseded by an existing map; coding.yaml was always the draft/toy map, not the target for these agents
Evidence: code-probe agent abe0f36f530327170 (claude-sonnet-5): of the 5 agents the ticket names as orphaned, only lint-fixer and wiring actually have no map (grep for agent: lint-fixer|agent: wiring under plugins/os-sdlc/ returns no matches). code-probe, seam-designer, and test-writer are already wired into plugins/os-sdlc/maps/poodr-implementation.yaml, the production-focused map -- coding.yaml is the 2-node draft/toy map (per docs/os-sdlc-rebuild/map-runner-design.md:410-424, coding.yaml itself lands at slice 6, not slice 4 as the ticket cited).
Follow-ups: none