ICA · Institutional Control Architecture
An essay from ALEETH  ·  October 2026
ALEETH · Essay

The Authority Ledger

ICA is the record the AI-operated company needs: who acted, on whose authority, within what limits, decided before it acted, and checkable by anyone.


Delaware is drafting a new kind of company, one an AI agent operates day to day. On October 26, 2026, the chairman of the House Oversight Committee asked the state for its records on the idea. Underneath his letter sits the question every company handing work to AI agents now has to answer: who gave the AI its authority, and who answers for what it does? ICA answers it for every action, in production today.

The Proposal

A company with an agent at the desk

The proposal describes an Artificial Intelligence Company: an entity an AI agent operates day to day, able to own assets and file lawsuits. One member, a person or a company, keeps it adequately capitalized and holds a liability shield. The shield falls away if the company is undercapitalized, or if it is used to break the law or commit fraud. Banking is excluded. A supervised sandbox would hold the first of these companies for thirty months, and lawmakers are expected to take the idea up in January.

For the record of what the agent actually does, the proposal asks for one thing: The AI agent must keep a log of its activities.

The Question

Congress asks who answers

Chairman James Comer's letter to Governor Matt Meyer requests the state's records on the initiative. He warns that the structure could be used to protect powerful AI companies and their investors from responsibility for reckless harmful actions, and he asks who shaped the drafting and why it was not done in the open.

AI agents already do corporate work, in every industry and under every kind of company. What Congress is reaching for is the record that stands behind that work when someone asks who allowed it.

A log tells you what the agent says it did. A ledger tells you who allowed it, within what limits, and lets anyone check.
The distinction
The Gap

A log is not a ledger

An agent's own log is written by the agent and held by the company that benefits from it. It can record that an action happened. It cannot show who gave the authority, what the limits were, whether a person could have stopped it, or that the entry was never changed. Those are the facts a court, a regulator, an insurer or a board will ask for, and a self-kept log was never built to carry them.

An authority ledger is a different object. Each entry is decided before the action takes place, bound to the person who authorized it, sealed outside the agent's reach, and verifiable by someone who trusts neither the agent nor the company.

The Answer

Five entries for every action

ICA writes that ledger for every governed action.

01Who actedThe agent, named by its own credential.
02On whose authorityA named person, with the approval bound to that person's signed-in identity.
03Within what limitsScope and spend set before the agent acts. A named person can stop it.
04Decided before it actedAllowed, held for a person, or refused, at the moment of the action.
05Checkable by anyoneA signed receipt in a public log, timestamped under RFC 3161, verifiable offline.
What ICA seals for each governed action

None of this is a report written after the fact. The decision is made at the moment of the action, the action carries its decision, and the record lands where it cannot be quietly edited. Anyone can verify a receipt against ICA's published key with no ALEETH server in the loop.

We Go First

Our own agents, chartered

A company that sells an authority ledger should keep one. Every one of ALEETH's 153 active AI agents carries a sealed charter: what the agent is for, what it must never do, the person accountable for it, what it may execute, the most it may risk on a single action, when a person must approve, and what trips its kill switch.

The last two charters were sealed on October 26. ICA does not let an agent's key grant that authority: a charter that lets an agent act needs a signed-in person behind its first seal. The authority came from the accountable owner's own session, and the receipt names the person who granted it.

The Record

Read it live

ICA publishes its own enforcement coverage, gaps included, and its transparency log anchors each signed root with an RFC 3161 trusted timestamp. At Harborline, ALEETH's test hotel, real AI agents faced a thousand attempts to con them into changing the books, and every decision was made by production ICA.

1,305
of 1,305 action paths that change anything, governed
1,000
attempts to con the test hotel's AI
311
times the AI gave in
0
changes to the books

The AI gave in. The books held, because changing them was never the AI's decision to make.

What It Means

The question has already arrived

Whether or not Delaware passes the proposal, the question has already arrived for every corporation whose agents act in its name. The board directs the business, officers act by delegation, and the duty of oversight reaches the systems that act for the company. An agent that can sign, pay, file or promise on the company's behalf is part of that chain.

That chain belongs on the record: who may authorize the agent, who may bind the company through it, who may stop it, and who may reverse what it did, from the board's instrument to the agent's charter to each sealed act.

AI can do the work. ICA proves who granted the authority, what was allowed, and who remains accountable.
The answer

Sources: Delaware Artificial Intelligence Company proposal, WHYY News, S. Mueller, updated September 30, 2026. U.S. House Committee on Oversight and Government Reform release, October 26, 2026. ICA public enforcement coverage and transparency log, read October 26, 2026. Harborline attack test hn-20261005T0613Z-e13f, 1,552 signed receipts verified offline. ALEETH agent charters read from production ICA, October 26, 2026.