robbond/confidence-engine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

experiment: confirm live sufficiency decision detection

Browse Source
This commit is contained in:
robbond
2026-08-15 05:59:35 +01:00
parent 47f42b24cc
commit 887a9710c8
2 changed files with 141 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+16
View File
@@ -3601,3 +3601,19 @@ Fixed the deterministic bug: removed `node.kind !== "unknown"` from State B dete
Tests updated to production shape (`kind: "unknown"` for decisions). Added 6 focused tests in 60B.75 block. All 22 tests pass. No schema/prompt/provider/harness changes.
Status: resolved.
#### Experiment 60B.76 — Live Verification of Sufficiency Question Fix (FAIL)
**Date:** 2026-08-15
**Branch:** `feature/sufficiency-decision-detection-v0.46`
**Type:** Live regression of 60B.75 fix
**Result: C — DECISION CLOSES + F — STRUCTURAL REGRESSION**
The deterministic sufficiency-closure gate in `apply-proposal.js` fires *before* question formulation when all material factors resolve. The decision (`n_product_launch_decision`) was auto-resolved with status=resolved before `formulateQuestion()` could fire the sufficiency confirmation template.
The 60B.75 kind-gate removal successfully exposed State B to reasoningPattern detection in the tests, but the live path hits an earlier gate: deterministic closure via `hasRemainingMaterialFactors()` returning false. The decision closes prematurely, no question fires, and activeUnknownNodeId becomes null.
Customer resolves correctly (negative meaning preserved). But the no-confirmation guard cannot prevent deterministic auto-closure because it operates after closure, not during.
Status: unblocked — need to address `apply-proposal.js` sufficiency closure gate before State B question selection can be tested live.