experiment: inventory project knowledge and context needs

2026-08-06 13:26:06 +01:00
parent 0ba927230b
commit 4661b8e8e5
2 changed files with 241 additions and 0 deletions
@@ -1499,6 +1499,59 @@ Engine experiments are now paused while project knowledge and context-loading ar
 Branch: feature/user-workspace-ux-v0.7
 Commit: 273f715

+
+## Experiment 26 — Inventory Project Knowledge and Context Needs
+
+**Status:** Pending review
+
+### Hypothesis
+
+The existing documentation can be separated into clear roles: current working context, task-specific references, historical evidence, and gaps to review. A simple inventory and loading map may reduce context without losing important knowledge.
+
+### Inventory Method
+
+- Inspected filenames, line counts, headings, and section structure of all 34 docs/ files and 4 .claude/ markdown files (38 documentation files total).
+- Did not print full contents of large documents (>100 lines).
+- Inspected headings via `grep`, file sizes via `wc -l`, and key sections (Experiments 23–25B, Return-to-Work notes) via targeted `sed`.
+- Created one inventory document: `docs/project-knowledge-inventory.md`.
+
+### Proposed Minimum Context
+
+For routine Confidence Engine work, Claude should normally load only:
+
+1. `.claude/project-context.md` — entire file (product direction, current stage)
+2. `.claude/architecture-guardrails.md` — entire file (hard boundaries, invariants)
+3. `docs/design-evolution-log.md` — lines 1–90, 824–838, 889–910, 1218–1520 (phase overview + Experiments 16–25B history)
+4. `docs/03_Confidence_Engine_Language_Guide.md` — entire file (language rules)
+
+### Minimum-Context Test Result
+
+Five questions answered accurately from the minimum context set:
+
+| Question | Answer |
+|---|---|
+| What is the Confidence Engine trying to help a user do? | Help people take justified next steps when a problem feels too big to know where to start — by breaking complexity into small pieces, building a reasoning graph, asking one question at a time, and updating until confidence is sufficient or remaining uncertainty is clear. |
+| What is the current engine experiment status? | Paused. Experiments concluded with Exp 25B (scope-aware condition status). Current focus: UX presentation improvements (v0.7 user workspace). |
+| What did Experiment 25B establish? | Scope-aware evidence-condition comparison: present-state evidence does not settle future-feasibility conditions. All 39+ tests pass across Exps 23–25B. |
+| What remains provisional? | Phrase-based scope detection (Exp 25A/B); passive classifiers not yet integrated into active reasoning; next-question selection pipeline needs re-evaluation. |
+| What work is intentionally paused? | All engine experiments beyond Exp 25B. No reasoning architecture changes. Current work: UX usability, presentation clarity, loading feedback. |
+
+### Missing Context Discovered
+
+None. The five questions were answered accurately from the minimum context set. No additional document was required.
+
+### Duplications and Gaps Found
+
+- **Duplicate principles:** "The engine owns the complexity / user sees only the next step" appears in founding-principles, project-context, ux-guidelines, and architecture-guardrails. Consider consolidating or cross-referencing.
+- **Buried current state:** Experiment 25B sits at line ~1,483 of a 1,542-line log. A developer must scroll past 14+ phases to find active status.
+- **No short entrypoint for active engine state:** project-context.md covers product direction but not experiment details (Exps 23–25B).
+- **Potentially stale architecture description:** v0.6-reasoning-architecture.md does not reference later additions from Experiments 15–25B.
+
+### Status
+
+Pending review. Nothing has been archived, moved, or deleted. The proposed context-loading plan is documented in `docs/project-knowledge-inventory.md`.
+
+---
 ---

 ## Current Open Questions