# Journey result: Veritas retraction cascade (customer view)

- **Walked**: 2026-05-29 by Claude (Opus 4.8) against commit `9455bc53ad`
- **Verdict**: **pass (surface)** — `/veritas/retraction` renders the
  soft-correction view; full cascade depends on a retracted source (mock data).
- **Walker**:
  `/tmp/claude-oshun-lt-2-walkthrough/walk.mjs veritas-retraction-cascade-customer-view`

## Observations

- `/veritas/retraction` renders (title "Veritas · soft correction | OSHUN") with
  a proper heading; 0 page errors, 0 persistent failures.
- Retraction/drift data is served via the BFF mock adapters and the
  `/veritas/evidence` two-pane (drift vs retractions) surfaces it.

## Not exercisable without seed data

- The live retraction cascade (a real source being retracted and propagating to
  saved items / briefings) needs a retracted-source fixture; the customer-facing
  surface renders and is reachable.

## 2026-06-29 notebook-drill addendum

- `apps/oshun/web/e2e/veritas-retraction-cascade.spec.ts` now covers the
  polished customer cascade surfaces for the private `/veritas/retraction`
  letter, Library saved-claim notice/removal, and `/nisaba/notebook`
  retraction-notice disclosure.
- The notebook pass opens the native disclosure, asserts the affected citation
  row and original quote, verifies the keep-with-marker action remains an honest
  placeholder, and follows the corrected-source link to the Veritas source
  profile.
- `apps/oshun/web/e2e/veritas-retraction-cascade-bff.spec.ts` remains the live
  backend cascade proof for source retract → Postgres/Redis → Sophia
  re-grounding verdict.
- Remaining gaps: customer-shell subscriber/audit fan-out, persisted notebook
  acknowledgement writes, Library confidence enum for retracted state, and the
  kept-offering re-render surface.