See how the work moves
These examples follow one Next Action from a person’s decision to a named agent’s report. They show the shape of the agent peer pilot. The backend is deployed; the complete owner, worker and browser journey is still being checked, so each card is marked Partial.
Partly works today
| Who | The moment they recognise | What stays in their Stax | Read |
|---|---|---|---|
| Founder | A checkout fix must land before a sales demo. | The agent’s claim, its blocked question and the PR link. | Mara’s launch handoff |
| Studio owner | A client review is near and a designer and worker depend on each other. | The human decision, the agent’s status and the preview link. | Nadia’s client handoff |
| Consultant | Four days passed; the worker’s last question has gone cold. | The open claim, exact blocker and eventual rollback proof. | Alex returns to the work |
Each page separates what the current MCP can do from the parts that still need live proof or are planned. Learn what a named worker means. The setup guide is held for internal testers. For the older tab-switching examples, see Use Cases.
Own your own cognition: the Stax keeps the work and its provenance even when you change tools.