docs(confidence-engine): close v0.60 multi-investigation work

2026-09-04 12:19:20 +01:00
parent cc3a5dabd4
commit e6f2249413
2 changed files with 96 additions and 13 deletions
@@ -711,12 +711,94 @@ v0.60h: Migrate Report route to use route `[id]` for all identity operations (in
 - No localStorage used, no provider imported, no module-cache manipulation
 - All mocks at application-facing boundary only

-### Live verification pending
+### Live verification (accepted)

---
+- same Portfolio card remained
+- same durable ID remained
+- same scenario remained
+- second Investigation unaffected
+- old reasoning state absent
+- clean Analyse state visible
+- no model call caused by Restart
+
+## v0.60 is structurally complete
+
+No remaining current production identity migration is known. v0.60 is structurally complete.
+
+The established multi-Investigation architecture:
+
+```
+Portfolio
+→ durable-ID Investigation collection
+
+Create New
+→ allocate crypto.randomUUID()
+→ navigate to /investigations/{id}
+→ no empty Investigation persisted
+
+Investigation route
+→ route [id] owns Investigation identity
+
+ScenarioForm
+→ hydrates by durable ID
+→ saves identified snapshots
+
+Report route
+→ loads/saves by route [id]
+
+Restart
+→ preserves Investigation container/id/scenario
+→ clears reasoning/Report state
+→ leaves other Investigations untouched
+```
+
+v0.60 result: **STRUCTURALLY COMPLETE**.
+
+### Acceptance evidence
+
+- case-1 production dependencies: 0
+- current production unscoped load dependencies: 0
+- current production unidentified save dependencies: 0
+- current user-facing clear/delete Restart callers: 0
+- Portfolio navigation: durable-ID owned
+- Report navigation/persistence: durable-ID owned
+- legacy singleton compatibility: still present internally, unused by current product, non-blocking deferred cleanup
+
+### Investigation culmination semantics
+
+Report is the point-in-time culmination of an Investigation.
+
+The flow:
+
+```
+Open Questions investigated
+→ user chooses Done for now
+→ question parked
+→ graph reconsidered
+→ Current Understanding regenerated
+→ user chooses what to investigate next
+→ eventually zero Open Questions
+→ milestone invitation
+→ "Review current understanding"
+→ /investigations/{id}/report
+```
+
+There is NO active intermediate overview/review surface between "Review current understanding" and Report. The control performs direct route navigation.
+
+Report represents: Situation, What we understand, What remains plausible when applicable. It does NOT represent a decision recommendation, confidence score, readiness judgement, or proof that the user should act.
+
+The user retains ownership of whether the understanding is sufficient, whether to act, whether to return to the Investigation, whether to re-open and investigate further.
+
+Report provenance remains: `generatedFromRevision` against `investigationRevision`, so a Report can later become "Update available" without ceasing to be the valid point-in-time Report generated from its earlier Investigation revision.
+
+Zero Open Questions ("You've now worked through all of the questions we surfaced") means: the currently surfaced Open Questions have been worked through. It does NOT mean: the user's decision is complete, sufficient confidence, or ready to act. The Engine facilitates the culmination. The user owns what that culmination means for their decision/action.
+
+Report is the established Investigation culmination. No further product boundary is selected.

 ## Next restart point

+> v0.60 is complete. Report is established as the culmination of an Investigation. No next product boundary is currently selected. Begin the next session by choosing the next unresolved user/product reasoning boundary from current product behaviour and founding principles, rather than continuing storage migration or assuming an old backlog item is next.
+
 Consult `docs/design-evolution/README.md` for progressive loading of product reasoning and provenance chronology; load the relevant chapter only when a specific historical question requires it.

 The current handoff captures all operational facts needed to resume today. For historical decisions, experiment evidence, or methodology evolution — consult the design evolution archive index or task-context packs as appropriate.