Operations
How a synthetic officeof agents is governed
Short answer
A synthetic office is governed like a company. The general director is a person and has the final word. A coordinating agent splits the work among agents with director-level mandates, every task has exactly one owner, and Compliance watches all of them without depending on any of them. Payments, signatures, and legal decisions are always approved by a person.
What a synthetic office is
A synthetic office is a team of AI agents organized like a company: with a hierarchy, mandates by area, and someone who coordinates. It is not a program that does everything. Each agent has an area, knows what is theirs, and knows who to report to. Anthropic describes this way of working as the orchestrator-workers pattern: a central model splits tasks among others and gathers the results1.
| Piece | Who it is | What it does | Who it answers to |
|---|---|---|---|
| General director | A person | Has the final word and approves what commits the company | The partners or the board |
| CEO agent | The coordinating agent | Receives every request, classifies it, splits it, gathers the results, and reports | The general director |
| Area agents | COO, CRO, CMO, CFO, CTO, and CLO, one per vertical | Do the repetitive work of their area and prepare decisions | The CEO agent and the person who leads that area |
| Compliance | A cross-cutting agent | Checks that what was executed is what was authorized, and can veto | Directly to the CEO agent, without going through any area |
| Shared memory | The company's knowledge base | Stores the rules, cases, and criteria that get refined over time, outside each agent's conversation2 | Managed by your team together with Omni Agent |
Every area agent works with a director's mandate: what falls to it in leadership, customers, resources, and the other dimensions of the model. The company gains the structure of a full leadership team, and the people who lead today keep deciding.
The governance rules
There are six, and they are not negotiated project by project. Each one answers a concrete risk.
- The final word belongs to a person. The general director and whoever leads each area decide. Agents execute, prepare, and propose.
- Every task has exactly one owner. Every request falls into a cell of the mandate matrix, and that cell has one responsible agent, as in a RACI matrix, where every task has exactly one person accountable for the result3. If there is no cell, the request goes to a person.
- Compliance does not depend on anyone it reviews. An auditor who reports to the area it audits stops being an auditor. The Institute of Internal Auditors' three lines model puts it this way: independence from management is what gives audit its objectivity and authority4. That is why Compliance watches every vertical and reports directly to the coordinator.
- Read by default, write with permission. Every agent starts with read-only access to each system. It writes only where your company authorizes it in writing, system by system, and asks for authorization before each write. That is the principle of least privilege: everyone gets only the permissions their function needs5.
- Whatever moves money or commits the company is approved by a person. OWASP recommends human approval before any high-impact action6. In our model that includes payments, signatures, contracts, and legal or tax decisions of substance.
- Everything is logged. Every action records when, where, who, and what7. Since every agent has its own account, "who" is always identifiable.
The decision-rights matrix
This table is the core of governance. It says what the agent does and what the person does for each kind of action.
| Type of action | What the agent does | What the person does | Example |
|---|---|---|---|
| Consult | Reads when needed, with read access | Reviews the log whenever they want | Bank movements through an authorized aggregator |
| Prepare and propose | Puts together the document, figure, or proposal | Reviews and decides | The week's payment proposal |
| Write to a system | Only with written authorization for that system, and asks for permission before each write | Authorizes or rejects | Logging a policy in the ERP |
| Handle a customer | Answers questions and follows up with approved rules | Takes the case if there is anger, an exception, or a negotiation | The status of a warranty claim over WhatsApp |
| Move money | Never; proposes the payment with its supporting documents | Authorizes the payment | Payment to a contractor |
| Decide something legal, tax, or strategic | Organizes the information and flags risks | Decides with their accountant or their lawyer | Responding to a request from an authority |
The practical effect is that your team stops chasing information and starts receiving it already put together. Whoever approves a payment does it with the invoice validated, the purchase order cross-checked, and the supplier's history in view.
How a request travels
A request always follows the same path, and every step leaves a record.
- It comes in. By WhatsApp, email, a form, or a system, at any hour.
- It gets classified. The CEO agent places it in a dimension and sends it to the agent who owns that cell.
- It gets executed. The agent works with its permissions and prepares what needs a decision.
- It gets reviewed. Compliance checks that what was done follows the rules before anything goes out.
- It gets approved. If it touches money, a signature, or a legal criterion, a person decides.
- It gets closed. The case is logged, and shared memory keeps what was learned.
Anthropic warns that an agent's errors can compound and recommends pauses for human review and stopping conditions1. Steps 4 and 5 are those pauses.
Infrastructure and data for each client
Every client has a dedicated virtual machine, Claude account and agents, and shares infrastructure with no one. That infrastructure belongs to Omni Agent, which contracts and manages it as part of the service; the information stays the client's.
Agents connect through authorized channels that already exist: banks through authorized aggregators in read mode, SAT through bulk invoice download, the ERP through its own connection or a connector installed on your network, and customers through WhatsApp Business and email. Where a portal has no connection, the agent operates it the way your staff would, with the permissions you give it. Your data stays yours. The confidentiality agreement is signed before seeing the first document, and personal data handling follows the federal law on the protection of personal data held by private parties, whose current version was published in March 20258.
How we install governance in your company
Omni Agent is an AI consultancy based in Mérida, Yucatán, that installs agents on top of models that already exist, mainly Anthropic's. Governance is not added at the end: it is designed from day one.
- Discovery. We map who approves what today, the business rules, the policies nobody wrote down, the tools, and how many times a month each thing happens. You come out with your company's decision-rights matrix.
- Contract. If you decide to move forward, it is signed once Discovery ends, for twelve months.
- Implementation. We set up each agent's account, permissions by system, approval points, and Compliance controls, and we test with real cases before opening the flow.
- Maintenance. We review the log, adjust rules and permissions, and give your team one hour of support each week. The monthly fee also covers the Claude account, the virtual machine and the harness license.
With governance installed, your directors delegate more because they see everything. The numbers are current, information arrives already put together, and decisions get made in minutes instead of waiting for the month's close.
What governance does not allow
- An agent paying, signing, or accepting a contract. It proposes and prepares; a person decides.
- An agent expanding its own permissions. Every new permission is authorized by your company in writing.
- A task going without an owner. Whatever does not fit the matrix goes to a person.
- Anything happening without a record. What is not in the log did not go through an agent.
- Promising zero errors. Agents make mistakes, like any team. That is why Compliance review, human approval, and the log exist.
Let's review which decisions you would delegate and which ones stay with you.
Sources
- Building effective agents (Anthropic)Orchestrator-workers pattern, errors that compound, pauses for human review, and stopping conditions.
- Effective context engineering for AI agents (Anthropic, September 2025)Agents that write notes to a memory outside their context window to keep what they learned between tasks.
- RACI chart template (Atlassian)In a RACI matrix, every task must have exactly one person accountable for the final result.
- The IIA's Three Lines Model (The Institute of Internal Auditors, July 2020)Internal audit's independence from management is critical to its objectivity, authority, and credibility.
- Least privilege (NIST, CSRC glossary)Definition of least privilege.
- LLM06:2025 Excessive Agency (OWASP)Limit tools and permissions, require human approval for high-impact actions, and log activity.
- Logging Cheat Sheet (OWASP)Every logged event should state when, where, who, and what.
- Federal Law on the Protection of Personal Data Held by Private Parties (Chamber of Deputies)Current text, published in the Official Gazette of the Federation on March 20, 2025.
Keep reading
The 9 dimensions where AI agents operate
What the nine dimensions of the Omni Agent model are, what each director-level agent owns in each one, and how that matrix decides who handles every request.
How to implement AI agents in your company, step by step
A practical guide to getting your first AI agent into operation in six steps. Pick the process, write the rules, set safe access and measure a pilot.