Add failure-path journeys to the os-backlog system model after the design pass #1561

New issue

Open

opened 2026-11-05 13:10:01 +00:00 by jared · 0 comments

jared commented

2026-11-05 13:10:01 +00:00

Owner

Problem

The journey map touches 84 of 107 os-backlog classes. Catalog::Failure cleared the role question, so the failure classes no longer show as unclear-role, but the 23 journeys trace no failure path. Handoff 2026-11-04-2114 reports that 15 of the 23 untouched classes are failure or result objects.

Reproduce

n/a: this is a design ticket; the stats report records the figures.

Approach

Add failure-path journeys after the design pass. One exception comes first: trace the failure paths at the presenter-pass sites before that pass changes them. Those sites are CLI::IssueCommands and ProjectIndex::Registration (registration.rb:15 is a rescue warn).

VERDICT: CREATE

Origin

Trigger: docs/system-design-format/proof/2026-11-04-stats-after-catalog-widening.md section 1, coverage stays 84/107; ruling 12 in docs/decisions/rulings.tsv
Improvised this session: none
Chain: 23 classes untouched ← journeys start from entry points and follow the success path ← DESIGN: the journey trace, plugins/os-backlog/design/generated/journeys
Root candidate: none found; searched journey, failure, system model, system-model, os-backlog coverage, unclear-role, rescue warn, Registration
Where: plugins/os-backlog/design/generated/journeys
Session: f8d22c34-9721-49e2-9938-d99682e1850c
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/f8d22c34-9721-49e2-9938-d99682e1850c.jsonl

## Problem The journey map touches 84 of 107 os-backlog classes. `Catalog::Failure` cleared the role question, so the failure classes no longer show as `unclear-role`, but the 23 journeys trace no failure path. Handoff 2026-11-04-2114 reports that 15 of the 23 untouched classes are failure or result objects. ## Reproduce n/a: this is a design ticket; the stats report records the figures. ## Approach Add failure-path journeys after the design pass. One exception comes first: trace the failure paths at the presenter-pass sites before that pass changes them. Those sites are `CLI::IssueCommands` and `ProjectIndex::Registration` (`registration.rb:15` is a rescue warn). VERDICT: CREATE ## Origin - Trigger: `docs/system-design-format/proof/2026-11-04-stats-after-catalog-widening.md` section 1, coverage stays 84/107; ruling 12 in `docs/decisions/rulings.tsv` - Improvised this session: none - Chain: 23 classes untouched ← journeys start from entry points and follow the success path ← DESIGN: the journey trace, `plugins/os-backlog/design/generated/journeys` - Root candidate: none found; searched journey, failure, system model, system-model, os-backlog coverage, unclear-role, rescue warn, Registration - Where: plugins/os-backlog/design/generated/journeys - Session: f8d22c34-9721-49e2-9938-d99682e1850c - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/f8d22c34-9721-49e2-9938-d99682e1850c.jsonl

jared added the

plugin/os-sdlc

filed-by/agent

category/investigation

labels

2026-11-05 13:10:01 +00:00