experiment: separate ui mock reference from deferred backlog

2026-08-06 14:47:34 +01:00
parent 78c98fb973
commit a4bbe0ef3f
7 changed files with 172 additions and 27 deletions
@@ -13,13 +13,15 @@ All files below were moved from `docs/` on 2026-08-06 by Experiment 29 to reduce
 | `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. |
+| `docs/archive/deferred-ux-backlog.md` (376 lines) | `docs/archive/deferred-ux-backlog.md` | Deferred and exploratory UX ideas from original `docs/backlog info.md` (lines 21–390). Retained for historical reference. Not commitments, priorities or active tasks. | Superseded `docs/backlog info.md`. Deferred UX planning separated from mock reference in Experiment 31. | When a named past UX idea from the deferred backlog is being reviewed; not loaded by default. |

-## Files Deliberately Not Archived
+## Superseded Files

-| 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. |
+The following files were superseded by a structured split in Experiment 31 and are no longer in use. Their contents remain fully represented in the documents below.
+
+| Original Path | Archive Paths (superseding) | Note |
+|---|---|---|
+| `docs/backlog info.md` (390 lines) | `docs/ui-mock-reference.md` (mock fixtures), `docs/archive/deferred-ux-backlog.md` (deferred UX planning) | Superseded 2026-08-06. Split into task-specific mock reference and deferred backlog archive. See Experiment 31 entry in design-evolution-log.md for content accounting. |

 ## Usage

@@ -0,0 +1,376 @@
+This document contains deferred and exploratory UX ideas retained for historical reference. Items are not commitments, priorities or active tasks unless they are reintroduced through a future experiment.
+
+Original source path: `docs/backlog info.md` (split by Experiment 31)
+
+---
+
+# Confidence Engine UI Roadmap
+
+The reasoning engine has reached a point where the next priority is not adding more capability, but improving the experience of using what already exists. The goal is to make the investigation feel coherent, understandable and satisfying while keeping the underlying reasoning visible enough for development without exposing unnecessary complexity to end users.
+
+---
+
+# Phase 1 – Complete the Core Investigation Experience
+
+## 1. Investigation History
+
+Finish the investigation history so it reads like an investigation notebook rather than a chat log.
+
+Each completed question should record:
+
+- The question asked
+- The user's answer
+- The resulting understanding (optional where appropriate)
+
+Example:
+
+```text
+✓ Were both figures measured over the same period?
+
+Answer
+Yes. Both covered the same quarter.
+
+Outcome
+The figures can now be compared directly.
+```
+
+This should become the permanent chronological record of the investigation.
+
+## 2. Current Understanding
+
+Replace "What we've established" with something closer to:
+
+Current understanding
+Confidence so far
+
+The purpose is to show how uncertainty is reducing over time.
+
+Example:
+
+```text
+Current understanding
+
+✓ Same reporting period confirmed
+
+✓ Comparable baselines confirmed
+
+• Complaint rate still requires investigation
+```
+
+This card should update cumulatively after every answer.
+
+## 3. Current Investigation
+
+This becomes the primary focus of the interface.
+
+Keep it deliberately simple.
+
+```text
+Current investigation
+
+Question
+
+...
+
+Why this matters
+
+...
+```
+
+Nothing more.
+
+The user should always understand:
+
+- what they're answering
+- why it matters
+
+## 4. Loading Experience
+
+Replace generic loading messages with investigation-specific feedback.
+
+Examples:
+
+```text
+Reviewing your answer...
+
+Checking what changes...
+
+Updating our understanding...
+
+Choosing the next question...
+```
+
+Avoid fake progress bars or percentages.
+
+# Phase 2 – UX Polish
+
+### Animated progression
+
+Instead of updating the page instantly:
+
+```text
+Answer submitted
+
+↓
+
+History updates
+
+↓
+
+Current understanding updates
+
+↓
+
+Next investigation appears
+```
+
+Small animations should reinforce the feeling of progressing through an investigation.
+
+### Progressive completion
+
+Completed investigation steps should gradually become:
+
+```
+✓ Same reporting period
+
+✓ Comparable baselines
+
+✓ Complaint rate
+
+► Reporting consistency
+```
+
+### Collapsible history
+
+Once the investigation becomes long:
+
+```
+Investigation history (8)
+
+▼
+
+Allow older questions to collapse.
+```
+
+### Better ending states
+
+Avoid generic messages such as:
+
+```
+No further questions.
+```
+
+Instead distinguish between outcomes.
+
+For example:
+
+```
+Current evidence has taken us as far as it can.
+
+Further investigation requires additional evidence.
+```
+
+or
+
+```
+The investigation is complete.
+
+Current confidence is sufficient to make a decision.
+```
+
+Different endings communicate different reasoning outcomes.
+
+## Phase 3 – Developer Experience
+
+Developer Details are becoming crowded.
+
+Split them into logical sections:
+
+```
+Developer Details
+
+Overview
+
+Graph
+
+Diagnostics
+
+Raw JSON
+
+Mock Data
+```
+
+This keeps debugging information available without overwhelming the interface.
+
+## Phase 4 – Mock Scenario Library
+
+Before returning to reasoning refinement, build a richer set of mock scenarios.
+
+These allow UI work to continue independently of the reasoning engine.
+
+#### Existing
+
+- Happy path
+- Complete investigation
+- Error state
+- No question available
+
+#### Required
+
+Contradiction
+
+Two observations conflict.
+
+Example:
+
+```
+Observation A
+
+Observation B
+
+↓
+
+Contradiction detected
+
+↓
+
+Question
+Comparison
+```
+
+Compare two options.
+
+#### Examples:
+
+- House A vs House B
+- Product A vs Product B
+
+#### Definition
+
+Clarify an ambiguous term.
+
+#### Example:
+
+"What do you mean by..."
+
+#### Diagnosis
+
+Fault finding and troubleshooting.
+
+#### Prioritisation
+
+Several competing options requiring selection.
+
+#### Revision
+
+Support changing an earlier answer.
+
+Example:
+
+```
+Q1
+
+A1
+
+Q2
+
+A2
+
+User edits A1
+
+↓
+
+Reasoning rebuilds
+```
+
+Even if replay isn't implemented yet, mock the behaviour.
+
+### Long investigation
+
+10–15 question investigation.
+
+Used for:
+
+- scrolling
+- collapsing history
+- pacing
+
+### Slow provider
+
+Simulate very slow model responses (30–60 seconds).
+
+Used for refining loading behaviour.
+
+### Provider error
+
+Connection failure.
+
+### Malformed provider response
+
+Invalid or partial JSON.
+
+Useful for resilience testing.
+
+## Backlog
+
+Reasoning Replay
+
+Create a replay mode for completed investigations.
+
+Example:
+
+```
+Statement
+
+↓
+
+Question 1
+
+↓
+
+Answer
+
+↓
+
+Graph updates
+
+↓
+
+Question 2
+
+↓
+
+Answer
+
+↓
+
+Graph updates
+
+↓
+
+...
+```
+
+Uses include:
+
+- demonstrations
+- debugging
+- explaining the reasoning process
+- validating graph updates
+
+This reinforces the principle:
+
+    The graph remembers. The conversation explains.
+
+## Deliberately Out of Scope
+
+The following should wait until repeated real-world testing reveals genuine reasoning issues:
+
+- Reasoning algorithms
+- Graph architecture
+- Confidence calculation
+- Decomposition improvements
+- Reasoning pattern expansion
+- Investigation strategy changes
+
+The current focus is making the investigation experience clear, understandable and enjoyable before expanding the reasoning engine further.