- tags
- #help #journeys #inherited
Journeys¶‹ Previous
A journey is a person's path through an app's pages to a goal: from where they start to where they are done. Open them at /page/Journey.
Review a journey with your AI¶
Your agents create the journeys; you review and adjust them on the fly. Walk your app the way a person would, one step at a time, with your AI beside you. On any step, say what to change (make Add to cart green, and say Buy): your AI changes the page and you see it at once. Step on, and when it reads right say lock it in: your AI publishes the page and writes its spec and test lines. Open a journey on /page/Journey (its Flow tab draws it as above), start it with Run now, and talk to your AI in its chat.
Find a journey¶
One search box finds specified journeys, features and pages (d2's built-in pages and its Page: and App: pages). Narrow it with All · Journeys · Features · Pages.
Specified or reverse-engineered¶
- Specified (green): written as a
Story:topic taggedjourney(once SpecUijourneyfences). Each step names its page, the link that leads there and the behaviours it uses. - Reverse-engineered (amber): pick any page and d2 follows its links, two pages deep. It stops where a page moves on by script, and says so.
- A hop of a specified journey whose page has no link to the next one is marked ⚠ no link from the step before (drift).
Read a journey¶
- Steps run top to bottom; branches sit side by side and join again.
- Tap a step: its page shows on the right, and around the step its features and classes (left) and tickets and topics (right). Tap one to open it on the right.
- ◀ and ▶ between the panes fold one side away; on a phone, switch with Journey · Page · Item.
A feature's journeys¶
Pick a feature to see its behaviours and every journey that uses them, with its steps highlighted. Every feature should have at least one.
Addresses¶
/page/Journey?journey=<id>, /page/Journey?page=Page:SetupMaster, /page/Journey?feature=<id>.