AI Code Completion Service  ·  View 03 of 21  ·  People and journeys

Actors and Their Journeys

Four groups, and the sentence each of them would use to say what they want.

Editable source SVG draw.io All views
The people who feel the latency Working developer 1.2 M daily Goal — Finish the line I was already typing, without stopping to read something wrong. Core journeys Accept a suggestion 2.4 B requests/day Ignore one and keep typing 55% cancelled Engineering lead per repo group Goal — Know whether this is helping my team or quietly putting plausible nonsense in our code. Core journeys Read acceptance by repo Exclude a generated path The people who own the estate Platform admin 40 tenants Goal — Switch it on for 4,000 engineers without our source code being retained anywhere. Core journeys Switch on a tenant zero retention Revoke a seat 60 s effective Security reviewer approves adoption Goal — See where code goes, what is retained, and what stops a key being suggested back. Core journeys Trace the data path Audit filter suppressions The people who change the model Model engineer weekly cadence Goal — Ship a better model and know within a day whether it actually helped anyone. Core journeys Promote a model 1% canary, 24 h Roll one back 10 min On-call SRE follows the sun Goal — Tell the difference between a fleet that is slow and one that is quietly useless. Core journeys Drain a GPU node Shed multi-line traffic Machines in the cast Workspace indexer per repo Goal — Keep a retrieval index that reflects the branch the developer is actually on. Core journeys Reindex a changed repo Promotion gate automated Goal — Refuse a model that loses retention, without waking anybody up. Core journeys Block or promote Actors and the Journeys They Own Person or role Journey / task Security / platform Decision point v 1.0 · owner Developer Experience Architecture · date 2026-10

Why this view first

  • The developer's goal — finish the line I was already typing — is the entire non-functional specification stated as a human sentence. Everything quantified later is a restatement of it.
  • The security reviewer is in the cast because they hold a veto. An architecture that cannot answer them does not get adopted, however fast it is.

Deliberate inclusions

  • The promotion gate is an actor, not a component: it refuses a model without waking anyone, which makes it a decision-maker in the system.
  • The engineering lead is here because acceptance rate is a management number as well as an engineering one, and the platform owes them a per-repo answer.

What is not here

  • No end customer of the software being written: this platform's value chain stops at the developer.
  • No prompt engineer or model trainer — training is outside the boundary (view 01).
◀  High-Level Architecture All views Journey — The Developer and the Grey Text  ▶
Solution Architecture v1.0 · Microsoft Azure · Developer Experience Architecture · 2026-10 · 21 views · 15 architecture decision records03-actors-and-journeys