Build #438 slice 5: fail edges, LoopLedger bounds, error-node routing #444
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#444
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?
Parent
#438 (map-driven os-sdlc runner build spec). Design: docs/os-sdlc-rebuild/map-runner-design.md. Settled decisions + guard-manifest process: docs/os-sdlc-rebuild/interface-sketches.md.
Pre-build gate
First step before any code: run the seam-design pass per docs/os-sdlc-rebuild/seam-design-prompt.md to produce this slice's interface sketch. The sketch is the guard manifest: any class, public method, or signature change beyond it → stop, comment on this ticket, do not write it.
What to build
Routing follows fail edges per the map; per-edge loop bounds act as anti-infinite-loop traversal guards (never implementation retries — ADR-0133); an exhausted bound routes loudly to the map-declared error node, which itself routes per the map. No skippable vocabulary anywhere. Sketch-time decision to settle: the ledger lives in NextStep per the amended design doc (D4 — spend! is a write), reconciling the stale Router-constructor comment in the slice-4 sketch.
Acceptance criteria
Blocked by
Origin
Work started: slice 5 via the TDD loop, branch build/438-slice-5 to follow. User gave tracer go after slice 4; seam-design pass running first per the pre-build gate, covering the two carried questions (routing-only agent: null nodes; implementation_failed terminal ownership) plus the loop ledger deferred from D4.
Resolution
Done: Slice 5 built TDD-first on build/438-slice-5, merged to main at
7a4865f. LoopLedger spends bounded map edges per (implementation, from_node, verdict) with rows only for bounded edges (D27, schema 10 edge_spends, failed_step renamed failed_reason); exhaustion re-routes through the node's error edge via the existing Router seam (D26); routing-only agent:null nodes transit in the same next call, never dispatched (D24); RoutingApplier owns Implementation.fail! with named reasons like bound_exhausted:node/verdict (D28/D30); repeated next after failure is byte-identical idempotent (D29); dead-pocket validation relaxed to every-node-reaches-a-terminal (OQ1-A, amending D1) with dead_pocket.yaml rewritten; escalation-node shape deferred to slice 6 (OQ2-A).Evidence: ruby -Ilib tests/all.rb: 842 runs, 2151 assertions, 0 failures (verified by orchestrator). rubocop zero offenses on all 11 dirty files, no disables. New loop_ledger_test.rb (6), bounded_loop.yaml exhaustion walk incl. named-reason terminal payload and no-new-rows repeat.
Follow-ups: Slice-6 seam pass owes the escalation-node shape (OQ2-A deferral) and the first real coding map + AgentVerdict. map-runner-design.md §1.6 stale pseudocode (route arity, spend!(position), map.error_decision) is owned by the slice-7 doc sweep. No new tickets filed; both owners are existing #438 child tickets.