Task: Write the user journey extraction standard

Table of Contents

This page documents a task in the Extract the user journeys that replace the ores.qt screens story. It captures the goal, current status, acceptance, and any notes or results.

1. Goal

Every component with a UX can extract its journeys the same way the IAM journeys were extracted, with the legacy Qt screens as an added input.

2. Status

Field Value
State DONE
Parent story Extract the user journeys that replace the ores.qt screens
Now Nothing.
Waiting on Nothing.
Next Nothing.
Last touched 2026-09-23

3. Acceptance

  • The User Journey Extraction Standard lists the steps the IAM journey work took, plus the pass over the legacy Qt screens, each with its evidence.
  • The journeys index links it.

4. Plan

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

5. Notes

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

The User Journey Extraction Standard has 31 items in six sections: inventory, legacy Qt screens, vocabulary and screen rules, journeys, documents, and verification and gaps. It is drawn from the sprint 25 tasks of "Prototype the post-setup IAM journeys in ores.web": the functionality inventory, the vocabulary and screen rules, the journey catalogue, the user_journey document type and the fourteen journey documents with their verification. The legacy Qt section is new: the IAM work did not read the Qt screens.

The story scopes it to the thirteen areas that had screens, from the Qt tree at /home/marco/Development/OreStudio/ores.qt, the same tree as af67db3062^:projects/ores.qt.

Emacs 29.3 (Org mode 9.6.15)