111 lines
4.1 KiB
Markdown
111 lines
4.1 KiB
Markdown
# Task-Specific Context Packs — Confidence Engine
|
||
|
||
> Routes future sessions to the minimal reading list for each task type. Choose exactly one pack. Add one document at a time only when a named gap requires it. Record why each additional document was loaded.
|
||
|
||
## Pack 1 — Engine Experiment Work
|
||
|
||
### Always read
|
||
- `docs/current-project-state.md`
|
||
- `docs/current-working-principles.md`
|
||
- `.claude/architecture-guardrails.md`
|
||
- `docs/current-implementation-verification.md`
|
||
|
||
### Then read only when relevant
|
||
- the specific implementation file;
|
||
- its focused tests;
|
||
- the immediately previous experiment entry in `docs/design-evolution-log.md`;
|
||
- the relevant contract or backlog entry.
|
||
|
||
### Do not load by default
|
||
- full design-evolution history; archived documents; UI mock reference; unrelated architecture documents.
|
||
|
||
### Stop and ask or record a gap when
|
||
- current documentation and source disagree;
|
||
- the task requires an undocumented contract;
|
||
- the experiment begins expanding into several capabilities.
|
||
|
||
## Pack 2 — UI and Mock Work
|
||
|
||
### Always read
|
||
- `docs/current-project-state.md`
|
||
- `docs/current-working-principles.md`
|
||
- `.claude/architecture-guardrails.md`
|
||
- `docs/ui-mock-reference.md`
|
||
|
||
### Then read only when relevant
|
||
- the affected component; its focused tests;
|
||
- the relevant UX guideline section;
|
||
- the named mock fixture.
|
||
|
||
### Do not load by default
|
||
- deferred UX backlog; archived UI reports; engine classifier documents; full design-evolution history.
|
||
|
||
## Pack 3 — Architecture or Contract Review
|
||
|
||
### Always read
|
||
- `docs/current-project-state.md`
|
||
- `docs/current-implementation-verification.md`
|
||
- `.claude/architecture-guardrails.md`
|
||
- `docs/current-working-principles.md`
|
||
|
||
### Then read only when relevant
|
||
- the named contract;
|
||
- `docs/architectural-principles.md`;
|
||
- the implementation files needed to verify the contract;
|
||
- a named historical experiment only when provenance matters.
|
||
|
||
### Important warning
|
||
Aspirational architecture must not be described as current implementation.
|
||
|
||
## Pack 4 — Knowledge-Management Work
|
||
|
||
### Always read
|
||
- `docs/current-project-state.md`
|
||
- `docs/project-knowledge-inventory.md`
|
||
- `docs/task-context-packs.md`
|
||
- `.claude/project-context.md`
|
||
|
||
### Then read only when relevant
|
||
- the document being reviewed;
|
||
- `docs/archive/README.md`;
|
||
- the immediately previous knowledge-management experiment.
|
||
|
||
### Do not load by default
|
||
- source code; tests; archived document contents; unrelated product or architecture documents.
|
||
|
||
## Common Rules
|
||
|
||
1. Start with the smallest pack.
|
||
2. Add one document at a time only when a named gap requires it.
|
||
3. Record why additional context was loaded.
|
||
4. Do not silently open the full experiment history.
|
||
5. Prefer named headings over fixed line numbers.
|
||
6. Source code decides what is implemented.
|
||
7. Current-state documents decide normal routing.
|
||
8. Historical documents explain how the project arrived there.
|
||
9. Leave a Return-to-Work Note after every completed experiment.
|
||
|
||
## Routing Test A — Engine Task
|
||
|
||
**Task:** Verify whether Behaviour Selection currently affects the user-facing response.
|
||
|
||
**Documents selected:** `docs/current-project-state.md`, `docs/current-implementation-verification.md`, `.claude/architecture-guardrails.md`.
|
||
|
||
**Documents excluded:** source code, full history, archived documents, UI mock reference.
|
||
|
||
**Sufficient?** Yes. current-implementation-verification.md §3b states Behaviour Selection has no callers outside its own module; current-project-state §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.
|
||
|
||
**Documents selected:** `docs/ui-mock-reference.md`, `docs/current-project-state.md`, `docs/task-context-packs.md`.
|
||
|
||
**Documents excluded:** deferred UX backlog, engine classifier documents, full history.
|
||
|
||
**Deferred UX backlog needed?** No. The mock reference already lists "Long investigation (10–15 turns)" and "Contradiction" with purposes matching the task. No extra file required.
|
||
|
||
---
|
||
|
||
*Created by Experiment 33. Branch: feature/user-workspace-ux-v0.7. Engine and UI experiments remain paused.*
|