[P9] Inspect and correct finding history

[richhaase]

---

steward_contract: "3"
id: "finding-history-correction-ux"
title: "Inspect and correct finding history"
revision: 1
state: draft
created_at: "2026-07-30T16:34:04Z"
approved_at: null
approved_by: null
frozen_body_sha256: null
supersedes: null

Inspect and correct finding history

Outcome

Users can understand and correct semantic finding history without erasing the original judgment.

Acceptance

• AC1: A user can inspect the evidence and reasoning associated with a stored finding relationship.
• AC2: Uncertain relationships remain visible and actionable.
• AC3: Reopening or correcting a relationship adds an auditable action while preserving the original record.
• AC4: Restart, refresh, and later model changes do not rewrite stored history.

[richhaase]

Downstream impact from #191 / PR #221 dogfood — July 22, 2026

• Changed: The approved Epic amendment adds durable adjudication memory, review economics, convergence controls, and a PR [P1] Enforce trusted review-configuration sources #221 replay corpus.
• Contract now: Golden evaluation must replay PR [P1] Enforce trusted review-configuration sources #221 and fail on recurrence, promotion, false-positive, or convergence regressions.
• Compatibility or migration impact: Additive planning contract; no current CLI behavior changes.
• Required follow-up: The issue acceptance criteria are amended below and implementation must coordinate with #223 and #224 where applicable.
• Evidence: Epic amendment and PR #221.

[richhaase]

Steward reframe — July 30, 2026

Replay and quality evaluation were split from correction UX. #217 now owns inspecting and correcting stored finding history. #254 owns representative convergence and finding-history replay evaluation.