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

docs: map reasoning requirements to production path

Browse Source
This commit is contained in:
robbond
2026-08-08 11:08:37 +01:00
parent 162ead2d69
commit 8c1036ecd0
4 changed files with 264 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–55E. Branch: `feature/user-workspace-ux-v0.7`. Status pending Rob's review.*
*Created by Experiment 34. Updated by Experiments 38–53, 54A–54Z, 55A–55F. Branch: `feature/user-workspace-ux-v0.7`. Status pending Rob's review.*
### Return-to-Work Note (Experiment 55E)
### Return-to-Work Note (Experiment 55F)
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.
The first implementation pass against the reasoning refinement requirements is deferred one more round while we map how meaning actually flows through the production update path — before committing to any schema or architecture changes. A source-inspection exercise traced the full answer-to-reasoning chain from prompt building, through LLM response parsing and normalization, into graph mutation. The key finding: no provenance fields exist on nodes or edges in the current schema, meaning R1/R2 separation has no structural carrier. The answer string is used only for a narrow comparability check, not for semantic verification against proposed changes. A complete path map lives in `docs/reasoning-production-path-map.md`. Tomorrow should decide whether to add provenance fields to schemas, modify the prompt structure, or both — grounded in this accurate production trace rather than architectural speculation. Branch: `feature/user-workspace-ux-v0.7`.
### Experiment 55A Summary — Clarification Uncertainty Preservation