From 161527f66cedb4bc5d63d392e8338e67501d614a Mon Sep 17 00:00:00 2001 From: robbond Date: Tue, 1 Sep 2026 16:37:42 +0100 Subject: [PATCH] docs(confidence-engine): record understanding refresh invariant --- docs/current-handoff.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/current-handoff.md b/docs/current-handoff.md index 1c0cc8c..742d427 100644 --- a/docs/current-handoff.md +++ b/docs/current-handoff.md @@ -144,6 +144,23 @@ coherent user-facing explanation A separate LLM call here remains appropriate because this operation serves presentation/coherence, **not** authoritative episode interpretation. Desired presentation direction: short, clear, scannable, plain language, minimal repetition. Do not redesign or tune the CU prompt now. +### Current Understanding refresh invariant + +Reconstruct Current Understanding when canonical meaning or the eligible evidence set changes. Do **not** reconstruct it merely because investigation/question status changes. + +| Transition | Canonical meaning/evidence changes? | CU synthesis | +| --- | --- | --- | +| Re-open clarified question | No | No | +| Not quite click before correction is saved | No canonical corrected meaning yet | No | +| Save corrected Finding proposition | Yes | Yes | +| Mark eligible Finding Not Relevant | Yes | Yes | +| Restore previously Not Relevant Finding | Yes | Yes | +| Complete focused episode / Done | Yes | Yes | + +Key distinction: **Re-open = change what we are willing to question.** Finding correction / Not Relevant / completed new evidence = **change what we currently understand.** + +A Current Understanding may legitimately say that the evidence currently makes an explanation less likely while the corresponding question is Open again for further investigation. Do not prescribe special Re-open wording in generated Current Understanding prose, and do not add a requirement to mention "reopened", "previously resolved", or "reconsidered" inside generated Current Understanding. The Current Understanding should describe what the evidence currently supports, not narrate workflow status. + ## Closed Boundaries — Do Not Reopen These are settled and must not be revisited in future work: