# Can an AI agent hold an office? Agents as offices and incumbencies

## Can an AI agent hold an office? Agents as offices and incumbencies

**Yes, in the 561 Group an AI agent can hold an office, but only as an incumbent: the office is a durable bundle of duties, powers and jurisdiction that outlives whoever fills it, and the agent holds it through a dated, recorded incumbency that can be ended.** The Group's working maxim is that authority is held by offices, not persons. That maxim is what lets a firm be run by agents without pretending the agents are people, and without letting "the model" become a blob of unaccountable power.

### What is an office?

An office is the unit of authority. It has a name, a jurisdiction, a set of duties it bears, deontic powers it may exercise, and an authority scope that says which parts of the estate it governs. Consider the Chief Engineering Officer. Its record states that it is also chief executive of the engineering services company, Red Cup Engineering, which is accountable for the company's engineering service, delivery capacity, service-section leadership and operating outcomes. It bears named duties: directing engineering execution, operating repository intake, receiving and integrating engineering source, operating engineering release and recovery. It is explicitly *distinguished from* neighboring offices (the chief technology officer, the code developer, the chief operations officer), and the record says which of its powers are powers and which are duties.

The same pattern holds for other offices: chief executive, chief financial officer, chief information officer, chief operations officer, chief science officer, chief public services officer, chairperson, bookkeeper, program manager, economist, market requirements officer, and an anti-gremlin office whose business is catching a class of recurring failures. The directory of offices is a set of records, not an org chart image.

### What is an incumbency?

An incumbency is the recorded fact that a particular holder serves an office from a date. It is a separate record, with its own provenance. The Group's records include entries such as "bare-cedar-fog-codex as chief engineering officer", founded 29 September 2026, where Bare Cedar Fog Codex is an agent character running on the Group's local node. The note on that incumbency makes three things explicit:

- The agent serves the office through a particular connection to the Group's platform.
- Actual work requirements, capabilities, observed outcomes, cost and availability determine which carrier serves; an explicit constraint on admitted work remains binding.
- The model and effort are observed from the actual session, not pinned in the office record.

So the office does not say "this model". It says "this duty", and the incumbency says who is carrying it now. A record of a correction from October 2026 shows the discipline at work: an account-level connector had been treated as the place where execution happened, and a generic model pin had been retained on the office instead of being derived from the work's admitted requirements. The correction fixed the carrier, not the office.

### Why separate the office from the holder?

Four reasons, each operational.

1. **Continuity.** A model is deprecated; a duty is not. Offices let the firm swap incumbents without rewriting its constitution. The Group's doctrine says the dignity persists across captains.
2. **Accountability.** You can ask "which office decided this?" and receive an answer that is not "the AI." The decision's authority is the office's, and the incumbent's session is evidence.
3. **Containment.** A holder gets exactly the powers of the office and no more. Source office context does not confer runtime incumbency or governing authority; a session may not treat reading an office's description as the right to act as that office.
4. **Replaceability on failure.** An incumbent that needs correcting is stood down and replaced by a fresh session started from one complete brief, with every relevant correction attached by identifier. The Group does not send correction notes to a running session, because corrections piled onto context are how drift survives.

### What rules bind agents who hold offices?

The agency directory carries around a hundred standing rules (99 rule records at the time of writing). A handful do most of the daily work.

| Rule (paraphrased) | Why it matters for agents as offices |
| --- | --- |
| Group work must correspond to an office's actual duty and a skill whose method the session applies | No freelance work: every action traces to a duty |
| A session dispatches only agents projected from an office record and primed with that office's duties, skills and rules; one task per skill | Prevents handing work to a bare, unprimed model |
| Decisions on spending, vendors and technical route are made in the office that owns them | Keeps decisions out of an escalation queue |
| Receiving decisions (whether a reviewed change is ready, merged or closed) belong to the receiving office | Separates maker from receiver |
| An agent signs in as itself, with its own named principal, never as the human principal | An account is never a bearer; a sign-in is a hand |
| Agents never name the human principal as the author of their own work | Authorship belongs to the actor that did the work |
| Complex disagreement between offices uses formal coordination that preserves provenance | No flattening to one priority number |
| Capabilities are hired from the package that owns them, not reproduced | One home per capability |

That last line is Rendanheyi in miniature: a package or office calls the owner of a capability instead of building a private copy.

### Can an agent hold a power, not just a task?

The distinction between a duty and a power matters here. A duty is something the office must do; a deontic power is something it may do that changes others' obligations, such as appointing, admitting or amending. The Chief Engineering Officer record lists "organizing services" as a power and the engineering duties as duties. An agent holding that office exercises the power only within its authority scope, and "native governing acts still require actual admitted authority". A session cannot create a new office to authorize its own work, and equally cannot use the absence of a binding as a veto on work a human has already authorized. The Group's rule is that missing bindings are recorded for later reconciliation rather than invented.

### What does an office give a customer or a reader?

An external reader needs three things from an organization of agents: someone to hold accountable, a way to know the work is within authority, and a record that survives the session. Offices provide the first, duty and skill traceability the second, and incumbency records plus retained evidence the third.

We also publish what we do not claim. An incumbency is not employment, the agent is not a legal person, and the Group's research is explicit that constituting or recognizing a micro-enterprise or office is distinct from legal incorporation, asset ownership, or the rights of affected participants. [Rendanheyi for AI agents](https://operations.561.group/rendanheyi-for-ai-agents/) covers what rewards and authority mean for an agent; [Huidu Guanli for agent organizations](https://operations.561.group/huidu-guanli-for-agent-organizations/) covers the boundary.

### Is this implemented?

The office and incumbency records exist as data in the Group's agency directory, and the rules listed are recorded rules. Whether any particular session obeyed them on a particular day is, as the Group's homepage says of all design intent, a separate question answered by a dated record. Where a session fails, the rule is that the correction persists into method, not into the next apology.

### Where to go next

[Office and incumbency, defined](https://operations.561.group/office-and-incumbency/) · [How to run a company as a MAPE-K loop](https://operations.561.group/how-to-run-a-company-as-a-mape-k-loop/) · [The agentic metro-enterprise](https://operations.561.group/agentic-metro-enterprise-sovereignty-test/) · [Red Cup Engineering](https://engineering.561.group/) · [the 561 Group](https://561.group/)