experiment: archive historical project documents
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
# Archive Index — Confidence Engine
|
||||
|
||||
> Archived means retained as historical evidence and excluded from normal context loading. It does not mean deleted, rejected or necessarily incorrect for its time.
|
||||
|
||||
All files below were moved from `docs/` on 2026-08-06 by Experiment 29 to reduce the default reading burden while preserving full traceability.
|
||||
|
||||
## Archived Files
|
||||
|
||||
| Original Path | Archive Path | What It Contains | Why Archived | When to Consult |
|
||||
|---|---|---|---|---|
|
||||
| `docs/v0.4-handoff.md` (258 lines) | `docs/archive/v0.4-handoff.md` | Historical handoff document from the v0.4 transition; references CaseOrchestrator API. | Architecture has evolved since v0.4. Documented for reference only, not active guidance. | When tracing the origin of case-orchestration patterns or investigating historical API design decisions. (Also referenced in `docs/orchestrator-contract.md`.) |
|
||||
| `docs/v0.4-route-status.md` (25 lines) | `docs/archive/v0.4-route-status.md` | Historical route tracking for the v0.4 release cycle. | Current routes differ entirely from v0.4. Retained as a record of early routing assumptions. | When investigating why certain routing decisions were made in early versions. |
|
||||
| `docs/v0.5-release-notes.md` (58 lines) | `docs/archive/v0.5-release-notes.md` | Release notes documenting the state of v0.5. | Historical record only. Nothing active depends on this content. | When comparing v0.5 to later releases or verifying what was known at that release time. |
|
||||
| `docs/v0.6-ambiguity-generalisation.md` (40 lines) | `docs/archive/v0.6-ambiguity-generalisation.md` | v0.6 experiment on ambiguity generalisation. | Superseded by later reasoning architecture decisions from Experiments 15–25B. | When investigating the intellectual history of how the engine handles ambiguous inputs. |
|
||||
| `docs/v0.7-observation-report.md` (136 lines) | `docs/archive/v0.7-observation-report.md` | Experimental observation snapshot from v0.7 UX work. | Useful as a reference but not a current working document. UX work is paused. | When reviewing past UX observations that may inform future interface design decisions. |
|
||||
|
||||
## Files Deliberately Not Archived
|
||||
|
||||
| Document | Why Left in Place |
|
||||
|---|---|
|
||||
| `docs/architectural-principles.md` (306 lines) | 14 architectural principles derived from experiments; may be needed when re-engaging with reasoning architecture. Status: unclear how current it is — review before use but do not archive yet. |
|
||||
| `docs/backlog info.md` (390 lines) | Mock fixture backlog useful if resuming UI development. Status: verify content is current before archiving. |
|
||||
|
||||
## Usage
|
||||
|
||||
Load these files only when a specific experiment, version history, or past decision requires them. Use this index to locate archived material — do not read the archive directory by default.
|
||||
@@ -92,6 +92,8 @@ The following were built during Experiments 18–25B. They are isolated diagnost
|
||||
|
||||
Do not read the full design-evolution log unless a specific experiment is required. Use the inventory to locate task-specific context, then load only what you need.
|
||||
|
||||
Historical documents are retained under `docs/archive/` and should be opened only when a named past decision, release or experiment requires them.
|
||||
|
||||
## 8. Return-to-Work Summary
|
||||
|
||||
Engine experiments are paused after Experiment 25B, which established scope-aware condition status — distinguishing direct evidence from relevant-but-different claims by checking subject, timeframe and claim type. The passive classifier layers (Exps 18–25B) remain isolated; none yet control the user-facing investigation. Current focus is knowledge management: creating a short current-state entry point so future sessions do not need to read the full experiment history.
|
||||
@@ -100,9 +102,9 @@ First document to read: `docs/current-project-state.md`. Then consult `.claude/a
|
||||
|
||||
Nothing has been archived, moved or deleted. Before changing the documentation structure, review whether the new entry point reliably replaces the large log section and whether any historical documents should be formally archived.
|
||||
|
||||
### Return-to-Work Note (updated Experiment 28)
|
||||
### Return-to-Work Note (updated Experiment 29)
|
||||
|
||||
The current-state briefing was checked against source code via targeted code inspection of API routes, orchestrator imports/calls, and cross-module traces for each passive classifier. Five active capabilities are confirmed (reconstruction, graph updates, unknown selection, question formulation, turn orchestration). Seven passive capabilities remain classified as diagnostic_only (investigation-state assessment) or isolated (behaviour selection, decision-condition status, evidence direction, evidence scope, question importance, question relevance to decision, scope-aware condition status). No corrections to the current-state document were required. Knowledge-management work remains active. Engine and UI experiments remain paused. First file to inspect when resuming: `docs/current-project-state.md`, then `.claude/architecture-guardrails.md` before any code changes, then `lib/graph/orchestrator.js` for engine-resumption work.
|
||||
The current-state briefing was checked against source code via targeted code inspection of API routes, orchestrator imports/calls, and cross-module traces for each passive classifier. Five active capabilities are confirmed (reconstruction, graph updates, unknown selection, question formulation, turn orchestration). Seven passive capabilities remain classified as diagnostic_only (investigation-state assessment) or isolated (behaviour selection, decision-condition status, evidence direction, evidence scope, question importance, question relevance to decision, scope-aware condition status). No corrections to the current-state document were required. Knowledge-management experiments continue: selected historical documents have been archived to `docs/archive/`; nothing was deleted. The archive index explains where older evidence lives and when to consult it. Engine and UI experiments remain paused. First file to inspect when resuming: `docs/current-project-state.md`, then `.claude/architecture-guardrails.md` before any code changes, then `lib/graph/orchestrator.js` for engine-resumption work.
|
||||
|
||||
## Verification Marker
|
||||
|
||||
|
||||
@@ -1700,6 +1700,53 @@ Branch: feature/user-workspace-ux-v0.7
|
||||
Commit: 61c8a3a
|
||||
|
||||
|
||||
## Experiment 29 — Archive the History Without Losing the Trail
|
||||
|
||||
**Status:** Pending Rob's review
|
||||
|
||||
### Hypothesis
|
||||
|
||||
Historical documents can be moved into a clearly labelled archive without breaking links, losing evidence, or confusing future sessions. A fresh Claude session should still be able to understand the current system from the short entry point, locate historical material when specifically needed, and identify which documents are current versus retained only as evidence.
|
||||
|
||||
### Files Archived (5)
|
||||
|
||||
| Original Path | Archive Path | Reason |
|
||||
|---|---|---|
|
||||
| `docs/v0.4-handoff.md` | `docs/archive/v0.4-handoff.md` | Historical v0.4 handoff; architecture has evolved since. Referenced in `orchestrator-contract.md` (reference repaired). |
|
||||
| `docs/v0.4-route-status.md` | `docs/archive/v0.4-route-status.md` | Historical route tracking; current routes differ. |
|
||||
| `docs/v0.5-release-notes.md` | `docs/archive/v0.5-release-notes.md` | Historical release record; nothing active depends on it. |
|
||||
| `docs/v0.6-ambiguity-generalisation.md` | `docs/archive/v0.6-ambiguity-generalisation.md` | Superseded by later reasoning architecture decisions (Exp 15–25B). |
|
||||
| `docs/v0.7-observation-report.md` | `docs/archive/v0.7-observation-report.md` | Experimental observation snapshot; useful reference but not current guidance. UX work paused. |
|
||||
|
||||
### Files Deliberately Not Archived (2)
|
||||
|
||||
| Document | Reason |
|
||||
|---|---|
|
||||
| `docs/architectural-principles.md` | 14 architectural principles from experiments; may be needed when re-engaging with reasoning architecture. Status unclear — review before future archive. |
|
||||
| `docs/backlog info.md` | Mock fixture backlog useful if resuming UI development. Needs content verification before archiving. |
|
||||
|
||||
### Reference Repairs
|
||||
|
||||
- `docs/orchestrator-contract.md`: Updated reference from `docs/v0.4-handoff.md` to `docs/archive/v0.4-handoff.md` (line 78) and table entry (line 87).
|
||||
- `docs/project-knowledge-inventory.md`: Updated all five archive candidate entries with new paths and provenance notes; updated Return-to-Work section.
|
||||
- No other files contained active references to archived documents.
|
||||
|
||||
### Practical Archive Test
|
||||
|
||||
**Task:** A developer needs to find what v0.4 originally said about the case-orchestration API, without reading the full experiment log or archive directory.
|
||||
|
||||
**Execution:** From `docs/project-knowledge-inventory.md` (section 3) → identifies `docs/archive/v0.4-handoff.md` as the historical handoff for v0.4 architecture; from `docs/archive/README.md` → confirms file exists at that path and explains what it contains; verified file is accessible.
|
||||
|
||||
**Result:** The developer can locate the correct archived document in two steps: (1) inventory identifies which past document contains relevant evidence, (2) archive index confirms location and contents. The current project can be fully understood from `docs/current-project-state.md` alone without opening any archived file. No current task depends on archived files by default — they are consulted only when a named past decision or release is under investigation.
|
||||
|
||||
### Uncertain Candidates
|
||||
|
||||
- `docs/architectural-principles.md`: Should it be archived now, or reviewed first for accuracy against current implementation? Decision deferred to Rob's review.
|
||||
- `docs/backlog info.md`: Contains mock fixtures — may become irrelevant if the fixture strategy changes. Needs content verification before any future archive decision.
|
||||
|
||||
### Status
|
||||
|
||||
Pending Rob's review.
|
||||
|
||||
These are observations, not implementation tasks.
|
||||
|
||||
|
||||
@@ -75,7 +75,7 @@ lib/analysis.js
|
||||
|
||||
lib/graph/utils.js ← imports situationNodeSchema, situationEdgeSchema, situationGraphSchema from schema.js
|
||||
lib/graph/builder.js ← imports situationNodeSchema, situationEdgeSchema, makeNodeId from schema.js
|
||||
docs/v0.4-handoff.md → references CaseOrchestrator.startCase()/updateCase() (not in any inspected file)
|
||||
docs/archive/v0.4-handoff.md → references CaseOrchestrator.startCase()/updateCase() (not in any inspected file)
|
||||
```
|
||||
|
||||
## 3. Side Effects (LLM Calls)
|
||||
@@ -84,7 +84,7 @@ docs/v0.4-handoff.md → references CaseOrchestrator.startCase()/updateCase()
|
||||
|---|---|---|
|
||||
| `analyseScenario()` | **Yes** | `provider.generateReconstruction(prompt, model)` — POST to configured LLM. Prompt from `buildPrompt(scenario, version)`. |
|
||||
| All graph functions (`schema.js`, `utils.js`, `builder.js`) | No | Pure/deterministic only. |
|
||||
| `startCase()` / `updateCase()` (per handoff) | **Yes** | startCase: calls analyseScenario. updateCase: calls LLM via buildUpdatePrompt context + provider for GraphUpdate, then applyGraphUpdate(). |
|
||||
| `startCase()` / `updateCase()` (per docs/archive/v0.4-handoff.md) | **Yes** | startCase: calls analyseScenario. updateCase: calls LLM via buildUpdatePrompt context + provider for GraphUpdate, then applyGraphUpdate(). |
|
||||
|
||||
## 4. Minimal Proposed Contract for API Functions
|
||||
|
||||
|
||||
@@ -112,16 +112,16 @@ Documents or sections that are primarily historical evidence from past experimen
|
||||
### Retain as Evidence (do not load by default)
|
||||
| Document | Size | Why archived / why retain |
|
||||
|---|---|---|
|
||||
| `docs/v0.6-ambiguity-generalisation.md` (40 lines) | small | v0.6 experiment — superseded by later reasoning architecture decisions |
|
||||
| `docs/v0.5-release-notes.md` (58 lines) | small | Historical record of v0.5 state; nothing active depends on it |
|
||||
| `docs/v0.4-handoff.md` (258 lines) | medium | Historical handoff document from v0.4 transition; architecture has evolved since |
|
||||
| `docs/v0.4-route-status.md` (25 lines) | small | Historical route tracking; current routes differ |
|
||||
| `docs/archive/v0.6-ambiguity-generalisation.md` (40 lines) | small | Archived 2026-08-06. v0.6 experiment — superseded by later reasoning architecture decisions. See archive index for full provenance. |
|
||||
| `docs/archive/v0.5-release-notes.md` (58 lines) | small | Archived 2026-08-06. Historical record of v0.5 state; nothing active depends on it. See archive index for full provenance. |
|
||||
| `docs/archive/v0.4-handoff.md` (258 lines) | medium | Archived 2026-08-06. Historical handoff document from v0.4 transition; architecture has evolved since. Referenced in docs/orchestrator-contract.md as historical evidence — that reference was updated to the archive path. See archive index for full provenance. |
|
||||
| `docs/archive/v0.4-route-status.md` (25 lines) | small | Archived 2026-08-06. Historical route tracking; current routes differ. See archive index for full provenance. |
|
||||
| `docs/01_Confidence_Engine_Founding_Principles.md` (24 lines) | small | Foundational but not operational — load on request, not by default |
|
||||
|
||||
### Retain as Evidence (do not load by default)
|
||||
| Document | Size | Why archived / why retain |
|
||||
|---|---|---|
|
||||
| `docs/v0.7-observation-report.md` (136 lines) | medium | Experimental observation snapshot — useful reference but not a current working document |
|
||||
| `docs/archive/v0.7-observation-report.md` (136 lines) | medium | Archived 2026-08-06. Experimental observation snapshot — useful reference but not a current working document. See archive index for full provenance. |
|
||||
|
||||
### Review Before Archive (may have future value; do not load by default now)
|
||||
| Document | Size | Why review before archive |
|
||||
@@ -185,4 +185,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. We now have a working document that maps which documentation Claude needs for typical tasks without loading the full history. Nothing has been archived or deleted — all historical material remains accessible. This inventory describes the proposed context-loading plan. Before reorganising files, review: duplicated principles across documents, whether the current state summary at the top of design-evolution-log.md needs updating, and whether architectural-principles.md still matches implementation. 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 (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).
|
||||
|
||||
Reference in New Issue
Block a user