Demonstration corpus

Expert workflows, captured inside the software they happen in.

Every sample below is a real modelling session — not a screenshot library. Clicks, the named UI element under each click, the alternatives that were available and rejected, window geometry, narration and per-step file state, all on one clock.

42Workflows
13Packages
12Disciplines
4Vendors

What sits behind each card

The image is the artefact. The value is the trace that produced it — recorded by a desktop agent that reads the application's own accessibility tree rather than guessing from pixels.

Action
Click, double-click, drag, scroll and keystroke, timestamped on a single monotonic clock.
Element
The control actually hit — name, role, automationId and bounds, read from UI Automation.
Action space
Sibling controls that were available and not chosen, disabled ones included. The rejected options are the training signal.
Context
Window title and geometry, display bounds, normalised in-window coordinates, and a crop of the region before and after the click.
Intent
Spoken narration on the same clock, plus step marks and typed notes the demonstrator adds while working.
Artefact
The working folder committed at every step, so each action pairs with the file state it produced.
ESC / click to close