# 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 active;
- Experiment 33 created task-specific context packs (four minimal document sets);
- The working tree was clean at commit `b959cfa`.

## 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 33 created four task-specific context packs — one for each work type — giving each a minimal four-document starting set plus targeted reading paths. Routing tests for engine and UI tasks passed. No source code changed. No additional context was required beyond the existing documents.

**Commit:** `b959cfa` (experiment: create task-specific context packs)

## 5. What Remains Open

- Whether a single handoff is enough to resume accurately after an extended break;
- Whether tasks crossing pack boundaries can still stay concise without loading excessive context;
- Whether old return notes should remain historical evidence rather than being treated as current;
- When knowledge-management work is complete enough to resume engine experiments.

## 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. Branch: `feature/user-workspace-ux-v0.7`.*