[P9] Reconcile findings across review revisions

[richhaase]

---

steward_contract: "3"
id: "finding-reconciliation"
title: "Reconcile findings across review revisions"
revision: 1
state: draft
created_at: "2026-07-30T16:34:04Z"
approved_at: null
approved_by: null
frozen_body_sha256: null
supersedes: null

Reconcile findings across review revisions

Outcome

Each completed review receives an honest, durable account of how its findings relate to the preceding active findings.

Acceptance

• AC1: Reconciliation records a stable relationship when a new eligible review completes.
• AC2: A missing finding is not considered resolved without supporting evidence.
• AC3: Ambiguous continuity remains uncertain rather than being silently matched or resolved.
• AC4: Prior user dispositions influence later judgments but do not become unchallengeable.
• AC5: Stored judgments include enough evidence to be inspected and are not re-derived during refresh.

[richhaase]

Downstream impact from #193 / PR #222

• Changed: run-local identity survives FP filtering even when two groups have identical content.
• Contract now: transition-time reconciliation starts from distinct stable records; semantic similarity may relate them later but must not retroactively collapse their within-run identities or dispositions.
• Compatibility or migration impact: reconciliation inputs need stable IDs in addition to semantic content.
• Required follow-up: add a golden case with identical groups where only one is filtered and verify transition output remains unambiguous.
• Evidence (PR, tests, fixtures): PR [P1] Extract typed headless review service #222 f11439a; TestServiceTracksDuplicateFindingGroupsByFilterIdentity.

[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: Semantic reconciliation must use adjudications as evidence, require grounds to reopen them, and keep uncertain recurrence visible.
• 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.