robbond/confidence-engine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

experiment: review deferred project documents

Browse Source 
Experiment 30 classified two deferred documents against verified current state:
- architectural-principles.md → keep as task-specific reference (6 current, 4 aspirational, 3 duplicates)
- backlog info.md → retain temporarily pending revision (mixed mock fixtures + deferred UX planning)
Neither moved to archive — both contain material with potential near-term utility.
Created docs/document-role-review.md with evidence, routing test, and return-to-work note.
This commit is contained in:
robbond
2026-08-06 14:33:10 +01:00
parent 97e4f3029e
commit 78c98fb973
4 changed files with 197 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/project-knowledge-inventory.md
+8 -3
View File
@@ -96,6 +96,11 @@ Grouped by task domain. Only load the group relevant to your work.
| `docs/02_Confidence_Engine_Product_Story.md` (31 lines) | The product story, problem, idea, how it works, commercial value | When defining new features or evaluating product fit |
| `docs/04_Rob_Thinking_Model.md` (32 lines) | Rob's thinking model — the working pattern that inspired the engine | When questioning whether a feature adds real value or just architecture |
### Knowledge management
| 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 |
### Testing and contracts
| Document | Purpose | Loaded When |
|---|---|---|
@@ -126,8 +131,8 @@ Documents or sections that are primarily historical evidence from past experimen
### Review Before Archive (may have future value; do not load by default now)
| Document | Size | Why review before archive |
|---|---|---|
| `docs/architectural-principles.md` (306 lines) | medium | 14 architectural principles derived from experiments — may be needed when re-engaging with reasoning architecture |
| `docs/backlog info.md` (390 lines) | large | Mock fixture backlog — useful if resuming UI development; verify content is current before archiving |
| `docs/architectural-principles.md` (306 lines) | medium | 14 architectural principles from experiments. Experiment 30 confirmed: 6 current, 4 aspirational targets, 3 overlap guardrails but add context. Role: task-specific reference for reasoning architecture work. See `docs/document-role-review.md` §2. |
| `docs/backlog info.md` (390 lines) | large | Mix of mock fixtures table (15 scenarios — useful when UI resumes) and deferred UX planning notes (aspirational, untracked). Role: retain temporarily pending revision. See `docs/document-role-review.md` §3. |
### Do Not Move or Delete (evidence of design evolution)
These documents document the path from Phase 1 through Experiment 25B. Archiving them separately without review would lose the rationale behind later decisions.
@@ -185,4 +190,4 @@ None. The five questions were answered accurately from the minimum context set.
## Return-to-Work Note
Engine experiments paused after Experiment 25B, which established scope-aware condition status classification — distinguishing direct evidence from relevant-but-different claims by checking subject, timeframe, and claim type. Present-state evidence does not settle future-feasibility conditions. The passive classifier layers remain isolated; no active integration yet. Knowledge-management experiments continue: five historical documents have been archived to `docs/archive/` per Experiment 29 (archive index at `docs/archive/README.md`). Nothing was deleted. Two candidates (`architectural-principles.md`, `backlog info.md`) were deliberately retained in `docs/` pending review. This inventory has been updated with archive paths and provenance notes. Branch: `feature/user-workspace-ux-v0.7`. First file to inspect when resuming: `.claude/project-context.md`, then Experiments 23–25B in `docs/design-evolution-log.md` (lines 1218–1520).
Engine experiments paused after Experiment 25B, which established scope-aware condition status classification — distinguishing direct evidence from relevant-but-different claims by checking subject, timeframe, and claim type. Present-state evidence does not settle future-feasibility conditions. The passive classifier layers remain isolated; no active integration yet. Knowledge-management experiments continue: five historical documents have been archived to `docs/archive/` per Experiment 29; two deferred documents reviewed in Experiment 30 — architectural-principles.md assigned role "keep as task-specific reference," backlog info.md assigned role "retain temporarily pending revision." Neither moved to archive (both contain material with potential near-term utility). Document-role-review.md records all classifications and a practical routing test result. First file to inspect when resuming: `.claude/project-context.md`, then Experiments 23–25B in `docs/design-evolution-log.md` (lines 1218–1520).