Layered Stewardship
Layered Stewardship is the phased extension of the Stewardship Model in which a single steward operates a venture at handover, with domain stewards added only when sustained intervention load in a specific area justifies them.
The Stewardship Model — the Arco operating model in which a single competent operator oversees an agentic stack, acting as architect and exception handler rather than executor — describes the operating unit of a venture at handover. Layered Stewardship describes how that unit scales as the venture matures. The model prescribes three phases. In the first, the studio designs and builds the venture. In the second, the studio transfers operation to a single formed steward — the Stewardship Handover, the boundary between construction and stewardship. In the third, reached only by ventures whose growth generates sustained intervention load in specific areas, **domain stewards** enter: operators with the same architectural mandate as the founding steward, scoped to one domain of the business.
The trigger for adding a domain steward is evidence, not convention. The Escalation Rate — the proportion of agentic task executions that require escalation to a human Steward — is the measurement. The Intervention Threshold — the architectural parameter that defines the conditions under which an agentic system must halt execution and escalate — is the design instrument. When the Escalation Rate within one domain remains persistently above target despite correctly calibrated thresholds, the intervention load has exceeded what a single steward can govern, and a domain steward is justified. A domain steward is never added because a mature company conventionally has a function. That is the org chart returning with better vocabulary.
Layering does not suspend the standing rule of stewardship: the steward resolves the exception and updates the agentic library so the next similar case is handled autonomously. A successful domain steward therefore reduces the intervention load that justified their entry. Each steward's resolved failure patterns and architectural improvements become reusable agentic infrastructure, feeding the Arco Flywheel and raising the architectural maturity of every subsequent venture from the first day of its build.
The single-operator definition of the Stewardship Model holds at handover and holds for every venture whose architecture keeps intervention load within one steward's capacity. Layering is the model's response to growth, not its replacement — the alternative, scaling oversight by rebuilding functional management, would reintroduce the Coordination Tax the architecture exists to remove.
Application
Every Arco venture launches under a single steward, and the addition of a domain steward is a governed event: it requires a domain-level Escalation Rate persistently above target across a defined observation window, with the founding steward's threshold calibration already verified. The Arco Operator Track is the formation pipeline for both roles — its Stewardship Trial terminates in a Stewardship Handover, and its graduates form the pool from which domain stewards are drawn. The failure condition is headcount added by function rather than by measured intervention load; a venture whose steward count grows faster than its escalation evidence has abandoned headcount decoupling.
This term is machine-readable
Any MCP-compatible AI assistant can retrieve the canonical definition of Layered Stewardship at inference time — no training approximation.
Related Terms
In the Log
First used: July 2026
Edition 1 · updated August 2026