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

experiment: rerun equivalent uncertainty identity with hardened capture

Browse Source
This commit is contained in:
robbond
2026-08-12 05:48:18 +01:00
parent 47509d307b
commit f022d6f4ad
2 changed files with 122 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+6
View File
@@ -221,6 +221,12 @@ Fixed a co-occurring bug where the accepted-update block referenced `startResult
---
### Experiment 57J.63 — Equivalent Uncertainty Identity Rerun with Hardened Capture
**Objective:** Once Update 1 establishes a persistent savings-realism uncertainty, does a semantically equivalent Answer 2 reuse that same unresolved node? **Classification: D — UPDATE 1 DID NOT ESTABLISH ANCHOR.** One start + one update. Start HTTP 200 (8 nodes). Update 1 returned HTTP 422 at `proposal_compatibility` with error: "answerMeaning.userSupportedMeaning is populated, but the proposal contains no graph mutation." The model extracted userSupportedMeaning ("I am unsure whether the projected office savings from the relocation are realistic.") with possibleInference but proposed zero graph mutations (addedNodes=[], addedEdges=[], updatedNodes=[{nodeId: nz4k4ep, newValue: null}]). No persistent savings-realism unknown was established. Update 2 not reached. Confirms same blocking class as 57J.61 but with full diagnostic evidence captured (57J.62 hardening works). Configured Ollama: qwen-claude:latest at http://192.168.1.111:11434. No production code changed.
---
### Experiment 57J.61 — Equivalent Uncertainty Identity Live Test
**Objective:** Once a dedicated savings-realism uncertainty exists, does a second semantically equivalent statement reuse that same unresolved node rather than create a duplicate? **Classification: D — UPDATE 1 FAILED.** One start + two updates. Start HTTP 200 (6 nodes). Update 1 returned HTTP 200 at update_applied but the harness crash prevented detailed proposal capture. A cold-start variant confirmed that when userSupportedMeaning is populated for savings-realism uncertainty, the model extracts meaning but proposes zero graph mutations — updatedNodes=[{nodeId: X, newValue: null}], addedNodes=[], addedEdges=[]. The gateway rejects this at proposal_compatibility with "answerMeaning.userSupportedMeaning is populated, but the proposal contains no graph mutation." Update 2 was reached (total 3 calls) and was rejected for the same reason. **Neither turn established a persistent savings-realism unknown.** The identity invariant cannot be tested when neither turn produces a valid, persistent unknown node. Configured Ollama: qwen-claude:latest at http://192.168.1.111:11434. No production code changed. Full record in `docs/experiment-57j61.md`.