experiment: archive historical project documents

This commit is contained in:
2026-08-06 14:24:52 +01:00
parent 354ba26aad
commit 97e4f3029e
11 changed files with 86 additions and 11 deletions
+2 -2
View File
@@ -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