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

experiment: test independent decision sufficiency

Browse Source
This commit is contained in:
robbond
2026-08-13 06:47:10 +01:00
parent 60a1befff7
commit 306f8392a1
2 changed files with 212 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+6
View File
@@ -2658,3 +2658,9 @@ Dev server disturbed: NO
Tested whether the engine resolves the existing "Which option leaves us better off overall?" decision when both options have quantified financial impacts and the user states no other material differences remain. Fixed answer provided: £600k one-off relocation disruption cost versus £2m/year recurring stay-put cost, with explicit closure condition ("no other material differences").
**Result:** Classification A — Decision Sufficiency Recognised. The engine preserved all three existing entity identities (opt_relocate, opt_stay_put, n_relocation_decision), created first-class metric nodes for both costs with correct option ownership and units (GBP vs GBP/year), recognised sufficient evidence to close the decision context, resolved n_relocation_decision in-place (status unknown → resolved) with direction favouring Relocate, created zero new uncertainties, and generated no follow-up question. One live call at qwen-claude:latest on http://192.168.1.111:11434. No production code changed.
## Experiment 60B.2 — Independent Decision Sufficiency Without Explicit Stopping Cue (2026-08-13)
Tested whether the engine independently recognises decision sufficiency when both options have quantified material costs (£600k one-off relocation vs £2M/year stay-put) but the user does NOT say "there are no other material differences" or any equivalent stopping statement. Answer provided exact financial comparison with no explicit closure language.
**Result:** Classification C — Generic Uncertainty Chasing. The engine preserved all three existing entity identities, set numeric newValue on each option (600000 on opt_relocate, 2000000 on opt_stay_put), performed an internal payback computation (~3.6 months), but treated the comparison as insufficient for decision resolution. Status changed unknown → supported (not resolved). No metric/evidence nodes created; no edges added; cost units not distinguished. Selected question "What outcome would demonstrate enough value to justify continuing?" is generic — does not identify a specific grounded missing factor. The engine demonstrated it can compute a meaningful financial comparison but does not use those computations as sufficiency triggers without an explicit user stopping cue. One live call at qwen-claude:latest on http://127.0.0.1:3000. No production code changed.