experiment: create task-specific context packs

docs/project-knowledge-inventory.md

@@ -47,6 +47,12 @@ These are the documents Claude should normally read before continuing Confidence
 - **Why required:** Self-referential — use it as a loading checklist.
 - **Size:** small
 
+### docs/task-context-packs.md (new — Experiment 33)
+- **Purpose:** Task-specific routing — four minimal context packs, common rules, and two routing tests proving each pack's sufficiency. Serves as the task-routing entry point after reading current-project-state.md.
+- **Sections to read:** The pack matching your work type; Common Rules; relevant routing test for confidence.
+- **Why required:** Provides a smaller starting context than the full inventory. Eliminates ambiguity about which documents to open first for each work type.
+- **Size:** small (~110 lines)
+
 ### docs/03_Confidence_Engine_Language_Guide.md
 - **Purpose:** Exact language rules for user-facing output (voice, translations, what to avoid).
 - **Sections to read:** Entire file (~27 lines).
@@ -107,6 +113,7 @@ Grouped by task domain. Only load the group relevant to your work.
 | Document | Purpose | Loaded When |
 |---|---|---|
 | `docs/document-role-review.md` (140 lines) | Classification of deferred documents; practical routing test for UI mock and reasoning tasks | When reviewing which documents to load; when a task involves architectural guidance or mock fixture reference |
+| `docs/task-context-packs.md` (~110 lines) | Task-routing entry point — four minimal packs for engine, UI, architecture review, and knowledge management work | Always for any new task — determines which pack to follow first |
 
 ### Testing and contracts
 | Document | Purpose | Loaded When |