UX artifacts and traceability
Scoped changes in the current context; extended baselines when requested.
- Status
- Proposed
- Last reviewed
- 2026-10-10
The jado-ux-artifacts procedure changes only the requested artifact. The main agent or active author reads the source and document, edits, verifies format and meaning, and delivers. It requires neither a separate Controller nor inherent delegation.
For a cross-team baseline or coverage review, use jado-ux-traceability: a dossier links sources, canonical documents and scenarios. There is no need to invent every artifact type to fill the matrix.
Independent verification required by the route remains separate from the author. Corrections return to the same instance within the remaining budget. Documentary evidence and user test results remain distinct.
In new projects, the root is docs/ux/; four collections preserve app formats, including JSON journeys. The UX Planner app and its ux-planner skill keep their own name and capabilities; JADO's procedure is jado-ux-artifacts.
Before moving an existing project to docs/ux/, check that your UX Planner version reads that root, then verify reading, saving, reopening and exporting. Correct JSON format alone does not prove location compatibility.