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

experiment: test customer signing decision closure

Browse Source
This commit is contained in:
robbond
2026-08-14 08:10:59 +01:00
parent bcbcb65020
commit 1331fe94f1
2 changed files with 203 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+9
View File
@@ -217,6 +217,15 @@ Experiment 54N tested whether an interpretation disagreement can be judged for m
- Deterministic harness validation passed via `npx vitest run tests/reproduce-multi-turn-investigation.harness.test.js` (`64/64`).
- This apparatus now enables the next bounded live experiment: answering the existing customer-signing unknown directly and verifying in-place update plus correct decision-state transition without factor duplication or unrelated uncertainty reopening.
### 60B.37 customer-signing decision closure
- Fixed input: user confirms enterprise customer signing in writing (£700k revenue confirmed), states no other material uncertainties remain.
- Single live update (updateOnly mode, one harness call). **Classification: C — FACTOR RESOLVES BUT GENERIC CONTINUATION REMAINS.**
- The engine correctly: reused `n_enterprise_customer_signing` (no duplication), resolved that unknown in place, recognized "no other material uncertainties remain" at the decision level, resolved `n_product_launch_decision` status to known, preserved both option identities, created no new nodes or edges.
- Inconsistency observed: despite `n_product_launch_decision` becoming known with correct rationale, a `selectedQuestion` (`"What outcome would demonstrate enough value to justify launching?"`) still points to this newly-resolved node — suggesting incomplete closure at the orchestration layer even though reasoning correctly determined resolution.
- £700k figure preserved semantically (in reason text, not dedicated value field). No directional recommendation recorded for the decision.
- Status pending Rob's review.
### When This Knowledge-Management Phase Is Complete
Provisional criteria for review (all confirmed met by Experiment 38 cold-start test):