Multiplayer Collaborative Canvas  ·  View 03 of 23  ·  People and journeys

Actors and Their Journeys

Three kinds of people and two kinds of machine, each wanting something the architecture has to pay for.

Editable source SVG draw.io All views
People in the file Product designer 4 M / month Goal — Work in the same file as my colleague without either of us losing a change or waiting for a save. Core journeys Design together, live Keep working offline Roll back to yesterday Stakeholder 11 M / month Goal — Open the link someone pasted in chat, see what changed, and leave a comment where it belongs. Core journeys Review by shared link Follow someone's cursor Workspace admin 120 k workspaces Goal — Remove a leaver's access and know it took effect while they still had the file open. Core journeys Revoke access now Recover a deleted file Machines in the file Plugin host quota-bound Goal — Apply a bulk change to 400 layers without being mistaken for a denial-of-service attack. Core journeys Bulk-edit under quota Platform SRE on call Goal — Know within a minute that one client's document has drifted from the server's version. Core journeys Catch divergence early Re-host a lost session Actors and the Journeys That Carry the Value Person or role Journey / task External / third party Security / platform Three journeys are mapped in the next views: design together, review by link, and the return from offline. v 1.0 · owner Platform Architecture · date 2026-10

What each one actually gets to do

  • The designer gets to stop thinking about saving — which is the whole product, and is why durability happens before the acknowledgement rather than on a timer.
  • The stakeholder gets to open a link on a phone and comment in the right place, without an account and without ever reaching the sequencer.
  • The admin gets a revocation that takes effect while the file is open, which is a live-session guarantee rather than an access-control list update.

Why the machines are in the cast

  • The plugin host edits like a person but at machine rate; without its own quota it is indistinguishable from abuse, and with one it becomes a supported use (view 09).
  • The platform SRE is an actor because divergence is invisible to users until it is expensive: someone has to be told within a minute (view 18).

Risks

  • Journeys were written from the requirement, not from research. Every volume on this page is a stated assumption.
  • The 'roll back to yesterday' journey is Phase 2 in the MVP ladder, so the set draws the history machinery without claiming the product surface exists.