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

experiment: validate cross-boundary context routing

Browse Source
This commit is contained in:
robbond
2026-08-06 15:58:41 +01:00
parent 7849b2f215
commit 544573af75
5 changed files with 152 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/design-evolution-log.md
+66 -1
View File
@@ -2131,6 +2131,71 @@ One genuine failure: **Routing Test B in task-context-packs.md**. The test state
### Overall Assessment: Mostly ready
Three of four tasks completed from initial context only. One routing defect found (Task 2). After fixing Routing Test B to include ui-mock-reference.md, the reduced context system is ready for normal work.
Two of four tasks completed from initial context only. One routing defect found (Task 2; corrected by Experiment 37). After fixing Routing Test B to name ui-mock-reference.md as the scenario source, the reduced context system is ready for normal work.
---
## Experiment 37 — Validate Cross-Boundary Context Routing
**Branch:** `feature/user-workspace-ux-v0.7`
### Hypothesis
The context-pack system can support cross-boundary work if Claude:
1. starts with one primary pack;
2. adds a second pack only for a named boundary;
3. records why each extra document was loaded;
4. avoids loading the full history.
### Initial Documents Loaded (328 lines total)
1. `docs/current-handoff.md` — 85 lines; first return-to-work entry point
2. `docs/current-project-state.md` — 131 lines; active state and capabilities
3. `docs/task-context-packs.md` — 110 lines; routing for four work types
### Additional Documents Loaded
| Document | Lines | Why Needed | Routing Should Include? |
|---|---|---|---|
| `docs/ui-mock-reference.md` | 62 | Cross-boundary boundary: the task requires identifying a mock scenario for workspace display. This is the second pack (UI and Mock) needed because no other loaded document names scenarios or UI fixtures. Yes — it is part of the UI/Mock pack, not an ad-hoc addition. |
### Cross-Boundary Task Result
**Task:** Display passive condition-status information in the workspace for a mock investigation without changing the active reasoning loop.
| Finding | Details |
|---|---|
| Condition-status capability | Passive: decision-condition status evaluation records signals but has no integration into the turn cycle; never controls user-facing decisions or path selection |
| Active reasoning loop | Unchanged: deterministic pipeline (scenario reconstruction → graph update → unknown selection → question formulation → turn orchestration); none of these pathways are affected by passive data |
| Mock scenario | "Long investigation (10–15 turns)" from `ui-mock-reference.md`; workspace can display accumulated diagnostic signals over time without interrupting the active reasoning cycle |
| Implementation areas to inspect later | decision-condition-status evaluation module; evidence scope detection module; UI workspace components for passive display integration |
| Both packs genuinely needed? | Yes: Engine pack identifies which capabilities are active vs passive; UI pack identifies how the workspace presents state. Neither alone suffices |
| Archive or full history required? | No |
**Context remained manageable:** Yes. 390 lines total (328 initial + 62 additional). Each document loaded for a specific named purpose. No blind expansion.
### Knowledge-Management Completion Criteria Review
| Criterion | Status |
|---|---|
| 1. Fresh session can resume from handoff + one pack | met |
| 2. Current state verified against implementation | met |
| 3. Historical material outside default loading | met |
| 4. Current principles separated from aspirational architecture | met |
| 5. Task-specific routing works for engine and UI tasks | met |
| 6. Cross-boundary task tested | **met** |
| 7. Maintaining handoff does not require reading full history | met |
All seven criteria are now met.
> Knowledge-management structure is ready for Rob's review before engine experiments resume.
### Routing Defects Discovered
None in this experiment. The correction to Routing Test B (naming `ui-mock-reference.md` as the scenario source) was applied before testing. No new defects found in the cross-boundary test.
### Overall Assessment: Ready
The context-pack system handled a genuine engine/UI cross-boundary task by combining two packs deliberately with full documentation of each loaded document and its purpose. Context remained small (390 lines). All knowledge-management criteria are met.
---