experiment: create single return-to-work handoff

2026-08-06 15:37:12 +01:00
parent b959cfa7a7
commit 1d92aa0b07
5 changed files with 126 additions and 2 deletions
@@ -2003,4 +2003,49 @@ Each pack lists what to always read, what to read only when relevant, and what t

 Task-specific context packs now exist in `docs/task-context-packs.md`, giving each work type a minimal four-document starting set plus targeted reading paths. Future sessions should start with `docs/current-project-state.md`, then choose one pack from `docs/task-context-packs.md`. Additional documents should be loaded only for a named gap, with the reason recorded. Engine and UI experiments remain paused. Branch: `feature/user-workspace-ux-v0.7`. First file to inspect when resuming: `docs/current-project-state.md`, then select the relevant pack from `docs/task-context-packs.md`.

---
+---
+## Experiment 34 — Single Return-to-Work Handoff
+
+**Date:** 2026-08-06  
+**Branch:** `feature/user-workspace-ux-v0.7`
+
+### Hypothesis
+
+A single short handoff file can carry enough immediate context to resume work accurately while linking to deeper documents only when needed.
+
+### Handoff Structure
+
+Eight sections: Where We Left It, What Is True Now, Why Work Is Paused, What Was Just Completed, What Remains Open, How to Resume, First Files by Work Type (table), Resume Check (five questions). Plus a maintenance rule replacing current-work sections when the project moves on.
+
+### Document Length
+
+`docs/current-handoff.md`: 68 lines (target range: 60–100).
+
+### Practical Resume-Test Result
+
+**Task:** Return after two weeks, remember almost nothing. Explain where the project stands, what is paused, what was completed most recently, and what to read before an engine task — using only `docs/current-handoff.md` and `docs/task-context-packs.md`.
+
+| Check | Result |
+|---|---|
+| Identifies correct active phase (knowledge management) | Yes |
+| Identifies paused engine and UI work | Yes |
+| Identifies Experiment 33 as latest completed | Yes |
+| Chooses Engine Experiment pack for engine task | Yes |
+| Avoids opening full design history | Yes |
+| Does not confuse passive code with active behaviour | Yes |
+
+**Verdict:** Pass. The handoff alone is sufficient to resume accurately.
+
+### Missing Information
+
+- "When knowledge-management work is complete enough to resume engine experiments" — no objective criterion exists yet; this is a judgment call for Rob.
+- "Whether tasks crossing pack boundaries can still stay concise" — unanswered in principle; requires testing with actual cross-boundary tasks.
+- Whether `docs/current-handoff.md` remains useful after several more knowledge-management experiments add to it.
+
+### Can This Replace Scattered Current Return Notes?
+
+Yes, for immediate resumption context. The handoff carries the latest stopping point without accumulating old notes. Historical return notes remain in `docs/current-project-state.md` and `docs/design-evolution-log.md` as evidence, not as current guidance. Rob should decide whether to purge older return notes once confident in the handoff model.
+
+### Status
+
+Pending Rob's review.