os-sdlc phase 3: map validator + dry-run simulator #329
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#329
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?
Two deterministic tools, no LLM involved. (a) Load-time static validation per the ticket-1 conventions: DAG check on success edges, retry caps present and finite, all routes known, escalation reachable. (b) Simulator: dry-run a fake ticket through a map with stubbed gates and injected random failures; print the path taken each run. Purpose: prove a map coherent and visualize the layer before real states ship. Depends on #328.
Superseded: #328 (design dependency) closed; static validation (DAG/reachability/retry-cap) shipped in lib/os_sdlc/runner/transition_table.rb + transition_table/row_validator.rb via the #341 map-driven engine rewrite. No dry-run simulator, but the phase-3 plan itself is moot.