experiment: separate ui mock reference from deferred backlog
This commit is contained in:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user