Level 2 · One lens
How people work in the system
Where a working sitting begins, the route taken from there, how far it gets, and how that differs by role. Sittings are keyed on the person: the platform’s own session identifier rotates mid-run and would report one morning as several visits.
Recorded work spans 4636 days. 10,606 automated transitions are held out of these journeys and kept for coverage: a trigger firing is evidence a path ran, but it is not part of anyone’s day.
How a sitting starts
The first action of each sitting, after repeats collapse. Five drafts in a row is one intent, not five.
What follows
Keyed on position in the sitting rather than drawn as a from-to graph. These actions cycle, and a graph rendered left to right would invent a direction the data does not have.
| First action | Then | Sittings |
|---|---|---|
| Open a matter | Close a matter | 288 |
| Close a matter | Open a matter | 267 |
| Open a matter | Raise a task | 112 |
| Open a matter | Complete a task | 89 |
| Complete a task | Open a matter | 83 |
| Raise a task | Open a matter | 79 |
| Open a matter | Reopen a matter | 59 |
| Reopen a matter | Open a matter | 36 |
47,502 sittings ended after a single action.
By role
A role is held on a matter, not by a person, so it is resolved for every event against the file the event happened on, climbing to the matter when the event landed on one of its child tasks (2,469 of them did). Resolution rate 78%.
When
Hour and weekday are both converted to Australia/Sydney. Converting one axis and leaving the other in UTC is what puts a Monday morning on a Sunday.
What was open on screen
The screen capture covers 7 days, against the 4636 days of recorded work above. The two windows differ, so the two halves are never averaged together.
1,028 requests carried an intent. 4 were furniture (the platform refreshing a widget, checking a permission, or re-sorting a list) and are held out of every measure on this page. Matched on exact path, never a substring.
| Held out | Requests |
|---|---|
/app/_widget/matter-summary | 2 |
/app/_permission/check | 1 |
/app/matter/list/sort/limitation-review | 1 |
What this evidence cannot say:
- navigation is a whitelist of known intents, not a complete log: absence from it is never evidence that something did not happen
- the request carries the endpoint, not the query text, so what a person searched for is not recoverable from it
How the actions were named
100% of recorded moves map to a named action. Every recorded move mapped to a named action. Actions that end an item’s life are kept separate from actions that advance it: reaching the end of a file is not the same kind of event as working on one, and a catch-all that merges them changes which action looks like the most common way in.