Architecture: Record, Judgment, Orchestration
The company record makes orchestration company-specific. Figaro coordinates accountable capabilities, governs consequential actions, and brings outcomes back into the record.
Published August 9, 2026
Figaro is a system of record and judgment that enables the orchestration of a company. The dated state of the business, its authority boundaries, and the lessons of prior decisions give humans and machines a shared basis for the next action.
Figaro
The seats, company context, cockpit, and teams that carry out the work.
Powered by Figaro
One gate, bounded authority, execution receipts, and a decision-to-outcome record. Execution, judgment, and governance are graded separately.
The Figaro Protocol
Declare → resolve → receipt → observe → grade
One operating loop
Sense → decide → gate → actuate → measure. Connectors bring dated observations into the company record. A seat proposes an action from the available evidence. The canonical gate resolves authority. A scoped actuator carries out the approved action. The measurement plan establishes when and how to assess the result.
Execution evidence and business outcomes answer different questions. A provider response can establish that an action ran; it does not by itself establish that the decision improved the business.
Stable responsibilities, teams formed around the work
A seat has a role, evidence, and defined tools. Growth, inventory, and finance can contribute to the same objective, while the decision has an accountable owner. Models are replaceable engines behind those roles. The company keeps the record when the engine changes.
The record is append-only
Observations and decision events are added, not silently overwritten. Corrections are new entries. Decisions retain the evidence available at the time; later knowledge cannot rewrite the original bet.
Authority is explicit
There is one gate. Effective authority is limited by the client’s policy, a human-granted envelope, platform and provider constraints, and current preconditions. Policy and watchdog deciders work at that gate when granted permission. Agent credentials and organizational rank confer no implicit approval power.
Three grades keep the questions separate
Powered by Figaro’s contract grades execution correctness, judgment quality, and governance quality separately. An action may run correctly yet miss its business target. A profitable outcome may still violate authority. Neither is reduced to a single success light.
Coverage must be evidenced
The native operating system is in use in a working commerce business and uses human approval for consequential writes. The broader Powered by Figaro plane is being implemented. A managed engagement must verify its connectors, permitted actions, receipts, and measurement coverage individually. This architecture is not a claim that every workflow is already wired.