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

docs: record accepted answer-meaning capture

Browse Source
This commit is contained in:
robbond
2026-08-12 12:01:16 +01:00
parent c4431997b1
commit 6a04d62800
2 changed files with 62 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+8
View File
@@ -1659,3 +1659,11 @@ This satisfies 57J.77's boundary A recommendation: a committed update-only path
### Experiment 57J.80 — Incremental Meaning on Existing Uncertainty (PRE-ANCHORED)
**Objective:** When a savings-realism uncertainty already exists and the user supplies new concrete information relevant to it, does the model emit `structuralActionRequired=true`, preserve that new information structurally, and avoid creating a duplicate equivalent uncertainty? **Classification: I — BLOCKED.** The committed `FIXTURE_MODE=updateOnly` apparatus passed a null `previousQuestion` through to the production server, which rejected at `request_validation` stage with `"Expected string, received null"`. The rejection occurred before any model inference call. One update call was made (counted but not executed by the model). No graph mutation, no structural action output, no information preservation assessment possible. The pre-anchored fixture and harness from 57J.78 remain correct for their original intent; this experiment encountered a boundary condition where no prior Start means no selectedQuestion to carry forward. Configured Ollama: qwen-claude:latest at http://192.168.1.111:11434. No production code changed.
### Experiment 57J.82 — Incremental Supported Information on Anchored Uncertainty
**Objective:** With the savings-realism uncertainty already present, does new supported information cause the model to emit `structuralActionRequired=true`, preserve that information structurally, and keep a single savings-realism uncertainty identity? **Classification: G — FIELD MISSING.** The model extracted partial information as a newValue (~£2M/year (lease elimination)) onto the existing node, preserved exactly one uncertainty identity, but did not populate `structuralActionRequired`. Full results in `docs/experiment-57j82.md`. Configured Ollama: qwen-claude:latest at http://192.168.1.111:11434.
### Experiment 57J.83 — Direct Answer-Meaning Capture from updatedProposal
**Objective:** Verify the production path correctly reads `answerMeaning` and `structuralActionRequired` from inside `updatedProposal` (graphUpdate schema container) and that all test mock boundaries are coherent with this contract. **Classification: IMPLEMENTED.** Fixed mock boundary mismatch where some fixtures placed fields at root level while capture logic read from inside `updatedProposal`. All 49 harness tests pass. Full results in `docs/experiment-57j83.md`. No production code changed; only experiment apparatus (script + test harness).