experiment: create task-specific context packs

This commit is contained in:
2026-08-06 15:30:14 +01:00
parent 51f0c11bc8
commit b959cfa7a7
5 changed files with 176 additions and 0 deletions
+52
View File
@@ -1952,3 +1952,55 @@ Pending Rob's review. No source code or tests changed. Engine and UI experiments
Current principles now live in `docs/current-working-principles.md`. This short document contains only guidance supported by verified implementation, current project direction, and established product philosophy — organised into three sections: user experience, reasoning, and building the system. Broader and aspirational architecture remains in `docs/architectural-principles.md` as a task-specific reference; it has not been rewritten or deleted. Future sessions should use `docs/current-working-principles.md` by default for product and reasoning work. Engine and UI experiments remain paused after Experiment 25B. Branch: `feature/user-workspace-ux-v0.7`. First file to inspect when resuming: `docs/current-project-state.md`, then `docs/current-working-principles.md` for current guidance.
---
## Experiment 33 — Create Task-Specific Context Packs
**Branch:** `feature/user-workspace-ux-v0.7`
### Hypothesis
A single concise context-pack guide can give each task type a minimal reading list, clear exclusions, and a stopping rule — reducing unnecessary context loading while preserving access to deeper material when a specific gap appears.
### Source Documents Used
- `docs/current-project-state.md` — Context Loading Guide; Current Engine Capabilities; Work Currently Paused
- `docs/project-knowledge-inventory.md` — Current Working Context; Task-Specific References
- `docs/current-implementation-verification.md` — Active Capabilities; Passive or Isolated Capabilities
- `docs/current-working-principles.md` — entire file
- `docs/ui-mock-reference.md` — headings and routing information only
- `.claude/project-context.md` — routing notes only
- `.claude/architecture-guardrails.md` — headings only
- Experiment 32 entry in `docs/design-evolution-log.md` (lines 18951948)
### Deliverable
Created `docs/task-context-packs.md` (~110 lines) with four packs:
- **Pack 1 — Engine Experiment Work:** current-project-state, current-working-principles, architecture-guardrails, current-implementation-verification.
- **Pack 2 — UI and Mock Work:** current-project-state, current-working-principles, architecture-guardrails, ui-mock-reference.
- **Pack 3 — Architecture or Contract Review:** current-project-state, current-implementation-verification, architecture-guardrails, current-working-principles + aspirational warning.
- **Pack 4 — Knowledge-Management Work:** current-project-state, project-knowledge-inventory, task-context-packs, project-context.
Each pack lists what to always read, what to read only when relevant, and what to not load by default. Common rules prevent silent context inflation. Two routing tests verify sufficiency without loading history or source code.
### Routing Test A — Engine Task
**Task:** Verify whether Behaviour Selection currently affects the user-facing response.
**Result:** Pack sufficient. `docs/current-implementation-verification.md` §3b states "Called by: None" for Behaviour Selection; `docs/current-project-state.md` §3 classifies it as isolated. No extra file required.
### Routing Test B — UI Task
**Task:** Choose the correct mock scenarios for testing a long investigation and contradictory evidence.
**Result:** Pack sufficient. `docs/ui-mock-reference.md` lists "Long investigation (1015 turns)" and "Contradiction" with matching purposes. Deferred UX backlog not needed.
### Validation
- All referenced files exist; no pack relies on fixed line numbers.
- Each pack has a smaller default context than the full project documentation.
- Active and passive capabilities remain clearly separated.
- No source code or tests changed; no files moved or deleted.
### Return-to-Work Note
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`.
---