Every Step in a Task Has Its Own Owner, AI or Human

Brex ran dozens of gRPC migrations across a 400-plus-service monorepo with 50 agents running in parallel, then stated the governance requirement in one sentence: agent work "needs to be attributed back to an actual human and not just a bot." Assigning the task an owner is not enough. Every step inside the task, the AI step that writes the code and the human step that approves the deploy, needs its own explicit owner, recorded at the moment it happens. Where agent identity gives the AI a distinct principal and binding to the human ties that principal to the person who asked, per-step ownership is what makes the resulting record complete.

The laptop model assigns owners by accident

On a laptop, ownership is solved. One engineer, one checkout, one token. Every step has the same owner because there is only one candidate. That answer is correct, free, and completely implicit.

It stops working the moment the work is distributed. In Brex's platform, tasks arrive from "Slack, Linear, GitHub, or a cron job," an orchestrator routes them to an agent pool, and each task gets its own Remote Developer Environment (Brex's per-task isolated workspace). Brex calls running 50 agents in parallel "a systems design problem." It is also an ownership problem. When fifty tasks run in parallel and no human is at any keyboard, "whoever kicked it off" is no longer an answer you can read off the room. It has to be a property the system records, per step, or it does not exist.

A step is first-class when it is typed, owned, and recorded

The mechanism is plain. A workflow is an ordered list of steps. Each step carries two facts: what kind of actor performs it (AI or human) and which specific entity owns it. Neither step type is a footnote to the other.

• An AI step runs under a distinct agent identity, bound to the human who initiated the task. The step's output, a commit, a plan, a review comment, carries that identity. The owner of an AI step is never "the bot"; it is the bound human, acting through a labeled synthetic actor.
• A human step is a gate. The workflow parks until a named person acts, and the action is recorded as that person's. Review as a gate covers the gate mechanics; the point here is that the human's approval is a step in the same workflow, with the same record format, not an out-of-band Slack thumbs-up.

Both kinds of step produce the same artifact: a record naming who did what, in order. That symmetry is what "first-class" means. A human approval that lives only in someone's memory is exactly as unauditable as an AI commit under a borrowed human token.

Recorded ownership is what survives the audit

Intercom runs the largest published version of this. Over 19% of their PRs are auto-approved with no human in the loop, and the system passed muster with their auditors. Their description of how: every AI-approved PR is "labelled, logged, and queryable. The review comments, the approval decision, the test results, the merge event: all recorded." Their sharpest formulation is the ownership claim in miniature: "The 'who' may change, but the 'what' doesn't."

And the terminal step stays human. Intercom is explicit that "the engineer who ships a change is expected to watch it go live, monitor its behaviour in production, and be ready to roll back." The AI owns the review step; a person owns the shipping step. Per-step ownership is what lets you hand individual steps to AI without the accountability for the whole task going anywhere, which is the subject of accountability stays human. It is also what enforces that the author of a change is never its sole approver: you cannot check author against approver unless both steps name their owner (author, never approver).

The published practice covers the end of the pipeline, not the middle

Two gaps. Brex names attribution as a principle but publishes nothing about its implementation: no identity model, no record format. And both reports document ownership at the terminal steps, the PR and the merge, while the corpus is largely silent on owners for intermediate steps such as planning and scoping.