docs(confidence-engine): checkpoint verified three-part report

2026-10-01 17:13:10 +01:00
parent 56b5f0099c
commit 8dc6e58d43
2 changed files with 47 additions and 0 deletions
@@ -50,6 +50,26 @@ Application-level isolation proven on deployed instance — User A does not see

 **Experiment:** Does exposing "What Remains Unresolved" information in the report synthesis prompt cause it to leak into the evidence-backed "understanding" section?

+#### Three-Part Report Increment — Loop 4/2 (VERIFIED)
+
+**Implementation commit:** `56b5f00`
+**Deterministic apparatus:** PASS (18 tests in `report-epistemic-ab-input-control.test.js`).
+**Rendered-product verification via Playwright:** VERIFIED.
+
+One actual Investigation Report demonstrated three distinct epistemic sections:
+1. What we understand — evidence-backed; unresolved questions excluded from understanding.
+2. What remains plausible — visibly separate (empty/default state in verified case).
+3. What remains unresolved — canonical Open Questions rendered as non-evidence, not answered/rank/interpreted.
+
+- Three-part report semantic/rendering: **VERIFIED** (one observed investigation, one scenario shape).
+- Unresolved questions remained non-evidence.
+- Zero additional experimental model calls during verification; no production/test changes.
+- `Update report` placement/ownership: OPEN PRODUCT QUESTION (separate from the verified increment).
+- Report lifecycle generation/reuse not re-established by this run.
+- Evidence does not generalise to universally solved or production-complete.
+
+**Next:** product-level review of Investigation Report experience.
+
 #### Loop 2 (final semantic run — 2/2 valid calls)

 Observed: