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

experiment: validate uncertainty proposition coverage live

Browse Source
This commit is contained in:
robbond
2026-08-14 06:23:03 +01:00
parent f94d47d813
commit 35a5efa804
2 changed files with 245 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+8
View File
@@ -183,6 +183,14 @@ Experiment 54N tested whether an interpretation disagreement can be judged for m
- `npx vitest run tests/graph/question-formulator.test.js` → PASS (37/37)
- **Still unproven live:** the exact 60B.27 customer-signing case through the full end-to-end runtime path.
### 60B.29 live uncertainty proposition coverage check
- A single live rerun was executed on `tests/fixtures/pre-anchored-product-launch-options.json` using the exact 60B.27-style customer-signing answer and the committed update-only harness.
- Core reasoning chain remained preserved live: decision stayed unresolved, customer-signing factor survived as a first-class unknown, material target remained selected, and no unrelated uncertainty was invented.
- The live customer node description used `Uncertainty over whether...` — **not** `Unknown whether...` or `Uncertain whether...` — so the new 60B.28 prefix-extension path was **not** exercised live.
- Final question regressed to generic wording (`What outcome would demonstrate enough value to justify launching?`) despite `selectedQuestion.nodeId` remaining the customer-signing node; full proposition preservation therefore remains unproven live.
- Rationale contamination remained absent.
### When This Knowledge-Management Phase Is Complete
Provisional criteria for review (all confirmed met by Experiment 38 cold-start test):