confidence-engine/docs/current-handoff.md

Current Return-to-Work Handoff — Confidence Engine

This file describes only the latest stopping point. Replace its current-work sections when the project moves on. Historical evidence remains in the design log and archive.

1. Where We Left It

• Engine experiments are paused after Experiment 25B;
• UI experiments are paused;
• Knowledge-management experiments are complete;
• Experiment 34 created a single return-to-work handoff file to replace scattered current-state notes;
• The working tree was clean at commit 1d92aa0.

This handoff describes the latest stopping point only. When work moves on, replace stale current-work details rather than appending another historical note. Historical experiment and commit information belongs in docs/design-evolution-log.md.

2. What Is True Now

• Main active engine path: deterministic reasoning pipeline (scenario reconstruction, graph update, unknown selection, question formulation, turn orchestration).
• Passive experimental classifiers from Experiments 18–25B remain isolated diagnostic layers; none control the user-facing investigation.
• Keyword and phrase-based scope detection remains provisional scaffolding.
• docs/current-project-state.md is the main entry point for active project state.
• docs/task-context-packs.md chooses the minimum context documents for each work type.

3. Why Work Is Paused

Engine and UI work were deliberately paused because documentation had grown large enough to overload Claude and make returning across sessions difficult. The current phase is simplifying what a fresh session must load to understand the project, without losing evidential history. Historical material remains available under docs/archive/.

4. What Was Just Completed

Experiment 37 corrected the routing defect from Experiment 36 and tested a cross-boundary engine/UI task. It validated that two context packs can be combined deliberately while keeping working context small, explicit and accurate. All seven knowledge-management criteria are now met. No source code changed. No files moved or deleted.

Commit: pending (experiment: validate cross-boundary context routing)

5. What Remains Open

• Whether the handoff stays accurate and concise after further project advances (tested by this experiment);
• Whether tasks crossing pack boundaries can still stay concise without loading excessive context;
• When knowledge-management work is complete enough to resume engine experiments.

When This Knowledge-Management Phase Is Complete

Provisional criteria for review:

1. A fresh session can resume from the handoff and one context pack; — met
2. Current state has been verified against implementation; — met
3. Historical material is outside default loading; — met
4. Current principles are separated from aspirational architecture; — met
5. Task-specific routing works for engine and UI tasks; — met
6. A cross-boundary task has been tested; — met (Experiment 37)
7. Maintaining the handoff does not require reading the full history. — met

Knowledge-management structure is ready for Rob's review before engine experiments resume.

6. How to Resume

1. Read docs/current-handoff.md.
2. Read docs/current-project-state.md.
3. Choose one pack from docs/task-context-packs.md.
4. Read .claude/architecture-guardrails.md before any code change.
5. Load extra context only for a named gap — record why.
6. Check Git status before continuing.

7. First Files by Work Type

Work type	Start with
Engine experiment	Engine Experiment pack
UI or mock work	UI and Mock pack
Architecture or contract review	Architecture or Contract pack
Knowledge management	Knowledge-Management pack

8. Resume Check

Answer before continuing:

1. What work is currently active?
2. What work is paused?
3. What was the latest completed experiment?
4. Which context pack applies to the next task?
5. Is there any uncommitted work?

---

Created by Experiment 34. Updated by Experiment 37. Branch: feature/user-workspace-ux-v0.7.

Return-to-Work Note (Experiment 37)

The routing defect from Experiment 36 was corrected (Routing Test B now names docs/ui-mock-reference.md as the source of mock scenario names). A cross-boundary engine/UI task was tested: displaying passive condition-status information in the workspace. Primary pack — Knowledge-Management; second pack — UI and Mock (ui-mock-reference.md for scenario routing). All seven knowledge-management completion criteria are met. Engine and UI experiments remain paused pending Rob's review. First file to inspect when resuming: docs/current-handoff.md, then docs/task-context-packs.md.