Add os-sdlc journeys per entry family with a coverage figure per plugin (system-model step 7) #1481
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#1481
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
README section 6 step 7 asks for os-sdlc journeys. os-sdlc has 0 journeys on 2026-11-01 (os-me 47/125, os-backlog 23/98, os 3/25). Journey coverage biases role assignment, because
entry?feeds DrivingAdapter and CompositionRoot.Reproduce
n/a for the bug-free path: the build writes no journeys for os-sdlc today.
Approach
Find the real entry families in os-sdlc:
bin/*CLI, hook, pipeline runner, and any other family found. Count by family, not by a fixed number, and not one per bin. Add one tagged journey per family. Detector andbuildoutput print a coverage figure for each plugin.Ticket #1434 (the Tracer records zero journeys silently when the trace subprocess fails) is fixed inside this work, because the os-sdlc trace is likely to hit it.
Required work:
use_caseinplugins/os-sdlc/test/**/*.rbcoverageinplugins/os-sdlc/lib/os_sdlc/system_model/*.rbRefusalErrorinplugins/os-sdlc/lib/os_sdlc/system_model/tracer.rbAcceptance criteria
system-model build plugins/os-sdlcruns, then it writes at least one journey for each entry family found.Non-goals
A journey for every bin.
Origin
1b4ea2d5)VERDICT: CREATE
Resolution
Done: Journeys recorded for four os-sdlc entry families; coverage figure printed
Evidence:
8c28fd4f, mergef9051edb, coverage 92/903Follow-ups: #1484, #1485, #1486; families without a journey (standalone scripts, procman, eval bins): dropped by the step 8 course check — none of them feeds entry? or blocks the detectors