experiment: facilitator progress panel (Version B)

2026-08-05 14:37:43 +01:00
parent 54acf0d565
commit ebea15c970
4 changed files with 361 additions and 3 deletions
@@ -470,6 +470,69 @@ A persistent two-thirds conversation column beside a one-third supporting column

 #### Evaluation

+Visual review completed.
+
+#### Status
+
+Closed.
+
+## Result
+
+Partially confirmed.
+
+## What did we learn?
+
+- The investigation workspace is beginning to feel like a genuine facilitated investigation rather than a document.
+- The two-column workspace (conversation on the left, reference material on the right) is proving to be a stronger mental model than previous layouts.
+- Keeping Situation and Investigation Map fixed while History grows vertically feels more natural.
+- The investigation question, response and history now read as one continuous conversation.
+- Developer Details have become extremely valuable.
+- The graph produced by the reasoning engine is far richer than previously realised. The graph now contains structured concepts including:
+
+  - observations
+  - unknowns
+  - assumptions
+  - relationships
+  - metrics
+  - state
+
+This suggests the UI should increasingly become a human-friendly projection of the graph rather than inventing separate state.
+
+The current "Investigation in progress" panel exposes developer-oriented statistics (nodes, edges, unknowns etc.) which are useful during development but are not the most helpful representation for an end user.
+
+---
+
+## Emerging Direction — Facilitator Translation Layer
+
+> The UI should progressively become a translation layer over the reasoning graph rather than maintaining separate duplicated summaries. Internal graph concepts should remain available for developers, while end users see a facilitator-style explanation of what is currently understood and what remains uncertain.
+
+The current technical progress panel (nodes, edges, unknowns, assumptions) exposes developer-oriented statistics. These are valuable during development but not the most helpful representation for an end user.
+
+The next direction is to explore presenting the same underlying graph data as a facilitator's notebook — what is known, what remains uncertain, and a quiet summary of the reasoning state underneath.
+
+---
+
+### Experiment 11 — Facilitator Progress Panel (Version B)
+
+#### Hypothesis
+
+The same underlying reasoning graph can be presented in a much more human-friendly way without changing the reasoning engine, API contracts, or graph generation.
+
+A facilitator-style panel should communicate:
+
+- what is known (resolved nodes and observations)
+- what remains uncertain (unresolved unknowns and assumptions)
+- a quiet summary of the reasoning state underneath
+
+#### Questions
+
+- Can the same graph data be translated into a facilitator-style view that end users understand more naturally?
+- Does separating "known" from "still investigating" reduce cognitive load compared to node/edge counts?
+- Is a quiet reasoning summary sufficient, or does it need more context?
+- Does the translation-layer principle hold — presenting the graph as a notebook rather than raw data?
+
+#### Evaluation
+
 Pending visual review.

 #### Status