Cloud Development Environment Platform  ·  View 03 of 21  ·  People and journeys

Actors and Their Core Journeys

Nine parties, two of them machines, each with a goal in their own voice and the journeys that carry it.

Editable source SVG draw.io All views
Developers Returning developer 250k daily Goal — Pick up yesterday's branch and keep typing — I should not have to notice that it stopped. Core journeys Resume a workspace p95 ≤ 2.5 s Share a preview URL New joiner day one Goal — Run the application before I have installed anything at all on this laptop. Core journeys First start from a prebuild p95 ≤ 25 s Reviewer per pull request Goal — Open the branch running, not a screenshot of it running. Core journeys Open a review workspace Machines Coding agent 65% of starts Goal — Give me forty disposable machines now, let me run unreviewed code in them, and take back a diff. Core journeys Burst 40 sandboxes 10× for 60 s Fork a developer's state Tenant automation scheduled Goal — Create and destroy workspaces from a script with no human in the loop. Core journeys Nightly integration sandbox The people who keep it up Platform SRE 1,800 hosts Goal — Patch every host this week without a single developer noticing that I did. Core journeys Drain and patch a host Absorb a host loss Security engineer per tenant Goal — Be able to say that a compromised dependency reaches nothing but its own kernel. Core journeys Set an egress posture Who pays for it Tenant admin seats · policy Goal — Set the idle timeout and the egress posture, and see what each costs me. Core journeys Set a spend ceiling Engineering finance monthly Goal — See cost per active workspace-hour, not a bill for a fleet. Core journeys Read the showback Actors and Their Core Journeys Person or role Journey / task External / third party Security / platform A coding agent is drawn as an actor, not as a feature: it starts two of every three workspaces and its goals contradict the developer's. v 1.0 · owner Platform Architecture · date 2026-10

What this settles

  • The coding agent is an actor, not a feature. Its goal — forty disposable machines now, unreviewed code inside them, a diff back — is what forces class-aware admission, stricter egress defaults and a session record that outlives the VM.
  • The platform SRE's goal (patch everything without a developer noticing) is only achievable because of ADR-01; on a host-owned design the same goal is a maintenance window.
  • Engineering finance appears in the cast because cost per active workspace-hour is a requirement, not a report.

Assumptions

  • A human session lasts about 95 minutes and an agent session about 7; the fleet is sized for the mix, not the average.
  • 1,800 tenants set their own idle timeout and egress posture within platform-defined bounds.

Risks

  • The reviewer's journey (open a branch running) is the one most likely to be served by a public preview URL, which is the platform's largest self-inflicted exposure.
  • Two of these actors can spend money without a human in the loop; the ceiling must be enforced at admission, not on an invoice.