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

docs: consolidate reasoning refinement requirements

Browse Source
This commit is contained in:
robbond
2026-08-08 09:08:39 +01:00
parent fcb7218407
commit 162ead2d69
3 changed files with 242 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+3 -3
View File
@@ -160,11 +160,11 @@ Answer before continuing:
---
*Created by Experiment 34. Updated by Experiments 38–53, 54A–54Z, 55A–55D. Branch: `feature/user-workspace-ux-v0.7`. Status pending Rob's review.*
*Created by Experiment 34. Updated by Experiments 38–53, 54A–54Z, 55A–55E. Branch: `feature/user-workspace-ux-v0.7`. Status pending Rob's review.*
### Return-to-Work Note (Experiment 55D)
### Return-to-Work Note (Experiment 55E)
55C showed preserved meaning can protect later resolution, but weak-priority meaning was already strengthened in Stage 1. 55D isolated that first interpretation step using a single-call stated-vs-inferred separation with four fixed answers across risk preference cases. Weak priority stayed as relative importance only (direct improvement over 55C's constraint-language strengthening). Conditionality survived through the conditional trade-off case. Explicit and uncertain controls stayed clean — no unsupported meaning leaked into statedMeaning. Stronger implications were kept separate in possibleInference for Cases 1 and 2, though Cases 3 and 4 showed unnecessary inference generation (hygiene issue, not leakage). This does not yet prescribe production architecture. Graph, Behaviour Selection, UI and production remain untouched. Same host/model (qwen-claude:latest on http://192.168.1.111:11434). Branch: feature/user-workspace-ux-v0.7. First test/file to inspect when resuming: tests/reconstruction/semantic-clarification-stated-vs-inferred.test.js for the full experiment and results. Status pending Rob's review.
This round of semantic experimentation is deliberately paused. The requirements synthesis for the next implementation pass lives in `docs/reasoning-refinement-requirements.md` — read it first. The key problem is preserving user-supported meaning, model inference, qualification, and unresolved uncertainty distinctly enough that later reasoning cannot silently convert one into another. Tomorrow should begin with code inspection against the requirements and regression pack rather than more semantic exploration. Production architecture is still undecided; no graph fields, Behaviour Selection changes, or UI layout have been prescribed. Branch: `feature/user-workspace-ux-v0.7`. This commit consolidates all findings into that single bounded document.
### Experiment 55A Summary — Clarification Uncertainty Preservation