Task: Extract the ores.workspace user journeys

Table of Contents

This page documents a task in the Extract the remaining component user journeys story. It captures the goal, current status, acceptance, and any notes or results.

1. Goal

Every journey a person had in ores.workspace is documented as a user journey, and every action its legacy Qt screens offered is covered by a journey or recorded as dropped. Order 2 of 13.

2. Status

Field Value
State ABANDONED
Parent story Extract the remaining component user journeys
Now Nothing. Abandoned; see Result.
Waiting on Nothing.
Next Nothing.
Last touched 2026-10-05

3. Acceptance

  • Every item of the User Journey Extraction Standard passes, with its evidence recorded below.
  • Every Qt action has a disposition: kept, changed or dropped.
  • Every defect found is captured, and every recurring gap is recorded.

4. Plan

Work the User Journey Extraction Standard in its section order and record each item below.

  1. Inventory (I01 to I05).
  2. Legacy Qt screens (Q01 to Q05).
  3. Vocabulary and screen rules (V01 to V03).
  4. Journeys (J01 to J08), ending with the catalogue agreed.
  5. Documents (D01 to D05).
  6. Verification and gaps (X01 to X05).
Item Result Evidence
     

5. Notes

  • Legacy screens: ores.qt/workspace at /home/marco/Development/OreStudio/ores.qt, or git show af67db3062^:projects/ores.qt/.... Survey on 2026-09-23: 2 .ui files and 4 headers declaring a window, dialog, wizard, widget, view, panel or page.
  • Starts after Clean ores.workspace to the component clean standard, because the coverage tables check against the generated protocol.

6. Test Scenarios

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

Scenario State Notes
     

7. PRs

PR Title
   

8. Review

Comment summary File Decision Notes
       

9. Result

Abandoned on 2026-10-05: ores.workspace is removed by Remove workspaces from every component, so it has no user journeys to extract.

Emacs 29.3 (Org mode 9.6.15)