Judgment Layer / Execution Layer

The architectural binary that defines the Arco build model: the Execution Layer is the set of tasks in a business's operations that follow deterministic logic and can be owned by agents; the Judgment Layer is the set of decisions that require genuine human assessment and are owned by the Steward.

In every business, two distinct categories of work exist simultaneously. The Execution Layer is the work that follows a fixed, encodable sequence — the tasks that execute deterministically once the inputs are known. These are the majority of operational steps in any labour-intensive service business: data entry, handoffs, confirmations, status updates, routing, reconciliation, document processing. They require accuracy and consistency but not judgment. The Judgment Layer is the work that requires genuine human assessment — the exceptions that do not fit a defined protocol, the decisions that depend on context that cannot be fully specified in advance, the actions that carry accountability that must be held by a person.

In legacy firms, these two layers are fused. A human performs both the execution and the judgment because the system was not designed to separate them. The consequence is that human time is consumed by Execution Layer work — work the system could own — while the Judgment Layer work that genuinely requires human input is buried in a workflow that makes it impossible to isolate. The human is doing two jobs for the cost of one, and the business is paying human rates for machine-executable work.

First used: March 2026