experiment: separate ui mock reference from deferred backlog
This commit is contained in:
@@ -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
|
||||
|
||||
|
||||
@@ -1,22 +1,8 @@
|
||||
## Mock fixtures to note for later reasoning refinement
|
||||
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.
|
||||
|
||||
Keep a backlog of these mock scenarios so you can continue developing the UX independently of Ollama:
|
||||
Original source path: `docs/backlog info.md` (split by Experiment 31)
|
||||
|
||||
| Fixture | Purpose |
|
||||
| --------------------------------- | ------------------------------------------------- |
|
||||
| Happy path (multi-turn) | General UI flow |
|
||||
| Contradiction | Validate contradiction reasoning |
|
||||
| Comparison | Compare two options |
|
||||
| Definition | Clarify ambiguous terms |
|
||||
| Diagnosis | Fault-finding flow |
|
||||
| Prioritisation | Ranking and trade-offs |
|
||||
| Revision replay | Editing earlier evidence and rebuilding reasoning |
|
||||
| No-question (needs more evidence) | Non-terminal pause |
|
||||
| Genuine completion | Investigation finished |
|
||||
| Long investigation (10–15 turns) | History, scrolling, collapsing |
|
||||
| Slow provider | Loading experience |
|
||||
| Provider error | Error handling |
|
||||
| Malformed response | Robustness and recovery |
|
||||
---
|
||||
|
||||
# Confidence Engine UI Roadmap
|
||||
|
||||
@@ -100,11 +100,11 @@ Engine experiments are paused after Experiment 25B, which established scope-awar
|
||||
|
||||
First document to read: `docs/current-project-state.md`. Then consult `.claude/architecture-guardrails.md` before any code changes and `docs/project-knowledge-inventory.md` for task-specific references. The full experiment history remains available in `docs/design-evolution-log.md` but is no longer default reading.
|
||||
|
||||
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.
|
||||
Engine experiments remain paused after Experiment 25B. UI experiments are paused. Knowledge-management experiments: five documents archived per Experiment 29; backlog info.md split by Experiment 31 into a mock fixtures reference (`docs/ui-mock-reference.md`) and deferred UX backlog archive (`docs/archive/deferred-ux-backlog.md`). Architectural-principles.md kept as task-specific reference. No backlog items deleted or promoted. **First file to inspect when resuming:** `docs/current-project-state.md`.
|
||||
|
||||
### Return-to-Work Note (updated Experiment 30)
|
||||
### Return-to-Work Note (updated Experiment 31)
|
||||
|
||||
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: five historical documents have been archived to `docs/archive/` per Experiment 29; two deferred documents reviewed in Experiment 30 (architectural-principles.md kept as task-specific reference; backlog info.md retained temporarily pending revision — neither moved). 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: five historical documents archived per Experiment 29; backlog info.md split in Experiment 31 into `docs/ui-mock-reference.md` (mock fixtures reference) and `docs/archive/deferred-ux-backlog.md` (deferred UX planning). Architectural-principles.md kept as task-specific reference. 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
|
||||
|
||||
|
||||
@@ -1805,3 +1805,89 @@ Each deferred document can be classified by comparing it with the verified curre
|
||||
Pending Rob's review. Neither document moves. Both roles confirmed by evidence against verified implementation. When UI work resumes, backlog info.md's fixtures table will be the direct reference; architectural-principles.md is available for reasoning architecture context. Engine and UI experiments remain paused. Branch: `feature/user-workspace-ux-v0.7`. First file to inspect when resuming: `docs/current-project-state.md`, then Experiments 23–25B in design-evolution-log.md (lines 1218–1520).
|
||||
|
||||
These are observations, not implementation tasks.
|
||||
|
||||
---
|
||||
|
||||
## Experiment 31 — Separate Useful UI Reference From Unstructured Backlog
|
||||
|
||||
**Branch:** `feature/user-workspace-ux-v0.7`
|
||||
|
||||
### Hypothesis
|
||||
|
||||
The document `docs/backlog info.md` can be divided into:
|
||||
- a short task-specific mock/UI reference that remains in the normal documentation area;
|
||||
- a retained deferred backlog document that is excluded from default context loading.
|
||||
|
||||
This should make future UI work easier without losing previous ideas.
|
||||
|
||||
### Separation Method
|
||||
|
||||
Original file `docs/backlog info.md` (390 lines) was split into two new documents:
|
||||
|
||||
1. **`docs/ui-mock-reference.md`** (~62 lines) — practical mock-fixture reference extracted from the original lines 1–20, structured with available scenarios, fixture data locations, when-to-use guidance, and warnings.
|
||||
2. **`docs/archive/deferred-ux-backlog.md`** (376 lines) — deferred UX planning content from original lines 21–390, preserved with original header stating items are not commitments.
|
||||
|
||||
The original file was removed after complete accounting (every section accounted for in one of the two new documents).
|
||||
|
||||
### Content Accounting
|
||||
|
||||
| Original Section | Line Range | Destination | Treatment |
|
||||
|---|---|---|---|
|
||||
| Mock fixtures table + intro | 1–20 | `docs/ui-mock-reference.md` | Represented as structured reference (same scenarios, enhanced with fixture data locations and usage guidance) |
|
||||
| UI Roadmap header + intro | 21–26 | `docs/archive/deferred-ux-backlog.md` | Copied unchanged |
|
||||
| Phase 1 – Core Investigation Experience | 27–118 | `docs/archive/deferred-ux-backlog.md` | Copied unchanged |
|
||||
| Phase 2 – UX Polish | 119–169 | `docs/archive/deferred-ux-backlog.md` | Copied unchanged |
|
||||
| Phase 3 – Developer Experience | 197–218 | `docs/archive/deferred-ux-backlog.md` | Copied unchanged |
|
||||
| Phase 4 – Mock Scenario Library | 219–326 | `docs/archive/deferred-ux-backlog.md` | Copied unchanged (scenarios listed twice — once in original fixtures table, once here — no duplication introduced) |
|
||||
| Backlog – Reasoning Replay | 328–378 | `docs/archive/deferred-ux-backlog.md` | Copied unchanged |
|
||||
| Deliberately Out of Scope | 379–390 | `docs/archive/deferred-ux-backlog.md` | Copied unchanged |
|
||||
|
||||
**Material not transferred:** None. Every original section is represented in one of the two new documents.
|
||||
|
||||
### Files Created
|
||||
|
||||
- `docs/ui-mock-reference.md` (~62 lines) — mock fixture scenario reference
|
||||
- `docs/archive/deferred-ux-backlog.md` (376 lines) — deferred UX planning backlog
|
||||
|
||||
### Files Removed
|
||||
|
||||
- `docs/backlog info.md` (390 lines) — superseded by the split; all content accounted for above
|
||||
|
||||
### Files Modified
|
||||
|
||||
- `docs/archive/README.md` — added deferred-ux-backlog to Archived Files table; added Superseded Files section with backlog info.md entry
|
||||
- `docs/project-knowledge-inventory.md` — added ui-mock-reference to UI/UX task-specific references; added deferred-ux-backlog to archive candidates; updated backlog info.md role to "superseded"; updated Return-to-Work note
|
||||
- `docs/current-project-state.md` — updated Section 6 (Return-to-Work Summary) and section 8 header/note to reflect Experiment 31 split
|
||||
- `.claude/project-context.md` — added routing notes: UI mock work reads ui-mock-reference; deferred backlog only for named UX idea review
|
||||
|
||||
### Line Counts Before / After
|
||||
|
||||
| Document | Lines (before) | Lines (after) |
|
||||
|---|---|---|
|
||||
| Original combined document (`backlog info.md`) | 390 | removed |
|
||||
| New mock reference (`ui-mock-reference.md`) | — | ~62 |
|
||||
| New deferred backlog (`deferred-ux-backlog.md`) | — | 376 |
|
||||
| Total new content | — | 438 (62 + 376, including headers in both) |
|
||||
|
||||
### Practical Routing Test Result
|
||||
|
||||
**Scenario:** A developer wants to test the workspace against a long investigation and a contradictory-evidence scenario. Which mock scenarios should they use, and where is the fixture data defined?
|
||||
|
||||
**Answer:** They should use:
|
||||
- **Long investigation (10–15 turns)** — for testing history scrolling, collapsing, pacing;
|
||||
- **Contradiction** — for testing contradiction detection and user-facing messaging.
|
||||
|
||||
Fixture data is defined in `tests/e2e/fixtures/investigation-scenarios.js`. The mock client is in `lib/mocks/confidence-engine/mock-client.js`. Scenario names are set via `NEXT_PUBLIC_CONFIDENCE_ENGINE_MOCK_SCENARIO` env var in `components/scenario-form.jsx`. Reference details and usage guidance are in `docs/ui-mock-reference.md`.
|
||||
|
||||
**Was the deferred backlog necessary?** No. The practical routing test was answered entirely from `ui-mock-reference.md`, `project-knowledge-inventory.md`, `.claude/project-context.md`, and `architecture-guardrails.md`. The deferred backlog (376 lines of aspirational UX planning) was not required to answer a practical mock-scenario question.
|
||||
|
||||
**Was any practical mock information lost?** No. All 13 fixture scenarios are preserved in `ui-mock-reference.md` with enhanced guidance on where fixtures live and when to use each. The original fixtures table's content is fully represented.
|
||||
|
||||
### Gaps Found
|
||||
|
||||
- `docs/ui-mock-reference.md` references `tests/e2e/fixtures/investigation-scenarios.js` as the fixture definition location but does not list individual scenario keys or env var values (by design — those are implementation details that can be inspected directly in the fixture file).
|
||||
- The deferred backlog contains specific wireframe text and animation specifications that may still be useful when UI work resumes. The header note ("not commitments, priorities or active tasks") should prevent premature actioning.
|
||||
|
||||
### Status
|
||||
|
||||
Pending Rob's review. Both new documents contain all original content. Branch `feature/user-workspace-ux-v0.7` is clean after commit. Engine and UI experiments remain paused.
|
||||
|
||||
@@ -64,6 +64,7 @@ Grouped by task domain. Only load the group relevant to your work.
|
||||
|---|---|---|
|
||||
| `.claude/ux-guidelines.md` (97 lines) | Main user view, developer view priorities; "calm workspace" principle | Always loading the UX guidelines for any UI task |
|
||||
| `docs/v0.7-user-workspace-ux-first-pass.md` (157 lines) | First UX pass: card layout, progress summary, developer details boundary | When continuing v0.7 UX work or reviewing layout decisions |
|
||||
| `docs/ui-mock-reference.md` (≈62 lines) | Task-specific reference for UI mock scenarios and fixture data locations. Contains available scenarios, purposes, where fixture data lives, when to use each, and warnings against treating mock behaviour as live-engine evidence. | When working on UI mock development or testing scenarios |
|
||||
| `docs/v0.7-ui-mock-mode.md` (291 lines) | Mock investigation mode for UI development without Ollama | When developing UI features that need fixture-driven testing |
|
||||
|
||||
### Graph and reasoning architecture
|
||||
@@ -127,12 +128,13 @@ Documents or sections that are primarily historical evidence from past experimen
|
||||
| Document | Size | Why archived / why retain |
|
||||
|---|---|---|
|
||||
| `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. |
|
||||
| `docs/archive/deferred-ux-backlog.md` (376 lines) | large | Deferred and exploratory UX ideas retained for historical reference. Not commitments, priorities or active tasks. Split from `docs/backlog info.md` by Experiment 31. 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 |
|
||||
|---|---|---|
|
||||
| `docs/architectural-principles.md` (306 lines) | medium | 14 architectural principles from experiments. Experiment 30 confirmed: 6 current, 4 aspirational targets, 3 overlap guardrails but add context. Role: task-specific reference for reasoning architecture work. See `docs/document-role-review.md` §2. |
|
||||
| `docs/backlog info.md` (390 lines) | large | Mix of mock fixtures table (15 scenarios — useful when UI resumes) and deferred UX planning notes (aspirational, untracked). Role: retain temporarily pending revision. See `docs/document-role-review.md` §3. |
|
||||
| `docs/backlog info.md` (390 lines) | large | **Superseded by Experiment 31.** Content split into `docs/ui-mock-reference.md` (mock fixtures reference, ~62 lines) and `docs/archive/deferred-ux-backlog.md` (deferred UX planning, ~376 lines). See archive index for provenance. |
|
||||
|
||||
### Do Not Move or Delete (evidence of design evolution)
|
||||
These documents document the path from Phase 1 through Experiment 25B. Archiving them separately without review would lose the rationale behind later decisions.
|
||||
@@ -190,4 +192,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. Knowledge-management experiments continue: five historical documents have been archived to `docs/archive/` per Experiment 29; two deferred documents reviewed in Experiment 30 — architectural-principles.md assigned role "keep as task-specific reference," backlog info.md assigned role "retain temporarily pending revision." Neither moved to archive (both contain material with potential near-term utility). Document-role-review.md records all classifications and a practical routing test result. 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 archived per Experiment 29; backlog info.md split in Experiment 31 into `docs/ui-mock-reference.md` (mock scenarios reference) and `docs/archive/deferred-ux-backlog.md` (deferred UX planning). Neither backlog item deleted or promoted. First file to inspect when resuming: `.claude/project-context.md`, then Experiments 23–25B in `docs/design-evolution-log.md` (lines 1218–1520).
|
||||
|
||||
@@ -0,0 +1,62 @@
|
||||
# UI Mock Reference — Confidence Engine
|
||||
|
||||
> Created by Experiment 31. This document contains practical reference information for working with investigation mock fixtures. It is separate from deferred UX planning which lives in `docs/archive/deferred-ux-backlog.md`. Do not load the deferred backlog unless a named past UX idea is being reviewed.
|
||||
|
||||
---
|
||||
|
||||
## Available Mock Scenarios
|
||||
|
||||
The following scenarios are defined as e2e fixtures and can be replayed for UI development and testing:
|
||||
|
||||
| Fixture | Purpose |
|
||||
| --- | --- |
|
||||
| Happy path (multi-turn) | General UI flow |
|
||||
| Contradiction | Validate contradiction reasoning |
|
||||
| Comparison | Compare two options |
|
||||
| Definition | Clarify ambiguous terms |
|
||||
| Diagnosis | Fault-finding flow |
|
||||
| Prioritisation | Ranking and trade-offs |
|
||||
| Revision replay | Editing earlier evidence and rebuilding reasoning |
|
||||
| No-question (needs more evidence) | Non-terminal pause |
|
||||
| Genuine completion | Investigation finished |
|
||||
| Long investigation (10–15 turns) | History, scrolling, collapsing |
|
||||
| Slow provider | Loading experience |
|
||||
| Provider error | Error handling |
|
||||
| Malformed response | Robustness and recovery |
|
||||
|
||||
---
|
||||
|
||||
## Where Fixture Data Lives
|
||||
|
||||
- **Fixture definitions**: `tests/e2e/fixtures/investigation-scenarios.js` — shared scenario content (central statements, answer sequences, expected headings).
|
||||
- **Mock client**: `lib/mocks/confidence-engine/mock-client.js` — interceptor + scenario replay logic.
|
||||
- **Test harness**: Components under `tests/e2e/specs/` drive each scenario through the UI.
|
||||
- **Scenario selector**: Set `NEXT_PUBLIC_CONFIDENCE_ENGINE_MOCK_SCENARIO` env var in `components/scenario-form.jsx`.
|
||||
|
||||
---
|
||||
|
||||
## When to Use Each Scenario
|
||||
|
||||
| Scenario | When to use it |
|
||||
| --- | --- |
|
||||
| Happy path (multi-turn) | General UI flow testing; verifying turn-by-turn progression and history updates. |
|
||||
| Contradiction | Testing contradiction detection, user-facing contradiction messaging, reasoning display. |
|
||||
| Comparison | Two-option comparison flows; validating side-by-side or prioritised presentation. |
|
||||
| Definition | Clarifying ambiguous terms; testing definition-mode responses. |
|
||||
| Diagnosis | Fault-finding / troubleshooting flows. |
|
||||
| Prioritisation | Ranking and trade-off scenarios. |
|
||||
| Revision replay | Testing evidence revision, graph rebuild, and reasoning chain updates. |
|
||||
| No-question (needs more evidence) | Non-terminal pause states — "no further question available" UI. |
|
||||
| Genuine completion | Investigation completion messages, confidence threshold UI. |
|
||||
| Long investigation (10–15 turns) | History scrolling, collapsing, pacing, memory behaviour over extended sessions. |
|
||||
| Slow provider | Loading spinners, feedback messages during delayed responses (30–60s). |
|
||||
| Provider error | Connection failure handling, error state UI recovery. |
|
||||
| Malformed response | Invalid or partial JSON — robustness and resilience testing. |
|
||||
|
||||
---
|
||||
|
||||
## Important Notes
|
||||
|
||||
- These mock scenarios are **fixture-driven only**. Their behaviour does not represent live-engine capabilities unless the corresponding engine features are implemented and enabled.
|
||||
- The fixture content (central statements, answer sequences) is fictional data. Do not treat mock evidence as real reasoning output.
|
||||
- For scenario names usable in `NEXT_PUBLIC_CONFIDENCE_ENGINE_MOCK_SCENARIO`, consult `tests/e2e/fixtures/investigation-scenarios.js` directly.
|
||||
Reference in New Issue
Block a user