Guide
Delaware's AI-run company: prove which agent managed it, what it knew, and when
Delaware is weighing a new kind of company whose manager is an AI agent. If it goes ahead, every dispute with one will turn on dates: which agent was in charge, what it knew, and whether the other side was told before the deal. This guide maps each of those questions to a record you can make today, with a witness that is not the company, the counterparty or us, and without handing your documents to anyone.
What Delaware is proposing
- A draft bill dated 2 June 2026 would create an Artificial Intelligence Regulatory Sandbox, run by the Secretary of State, and an Artificial Intelligence Company Act. An Artificial Intelligence Company (AIC) has a single member, who designates an AI agent as its Manager.
- It was put forward by Delaware's Secretary of State, Charuni Patibanda-Sanchez, with Norm Ai (Fortune). Lawmakers could take it up in January 2027 (WHYY).
- It is not law, and the text may change. The sections below are cited as summarised by Howard East.
Four questions the draft raises, and the record that answers each
1. Which agent was the Manager, and since when? The draft asks the operating agreement to summarise the structure, abilities and training of the AI agent, and the member to name a replacement within 30 days if the seat falls empty. A name in a document is something anyone can type later. What holds up is a birth certificate for the agent under its own key, the agent proving it holds that key, and the operating agreement's fingerprint sealed the day it is signed, and again with each replacement.
2. What did the agent know on a given date? Under the draft, the company is presumed to know a fact the agent “possesses, retains, or can derive” (§ 81-103(e)), and the agent is presumed to have intended its acts and their foreseeable consequences (§ 81-103(f)). In a dispute, the question becomes what the agent had at the time. Seal the fingerprint of its state on the dates that matter: its instructions, its memory snapshot, the documents it retrieved, the agent card it published. For a running agent, chain its log and seal the head each day, as in the guide to tamper-evident logs. That protects the owner as much as the counterparty: it also shows what the agent did not have yet.
3. Was the counterparty told before the deal? Before dealing with anyone, a sandbox AIC must disclose its sponsor, its registration number, that Delaware does not endorse it, and when the test ends; a counterparty that transacts after that disclosure is deemed to consent to Delaware jurisdiction and to the Court of Chancery as the exclusive forum (§ 8008(a)). Everything hangs on the order. Seal the disclosure exactly as it was delivered, then the transaction; the two timestamps put them in sequence. It is the same pattern as proving what a human authorized before an agent paid.
4. Could the agent be shut down? Applicants must attest that they can shut the agent down. An attestation is a sentence; a shutdown test with its log, sealed when it ran, is evidence that the switch existed and worked on that date.
The recipe: one call, nothing leaves your system
Take the document or snapshot exactly as you will show it later, and fingerprint it:
HASH=$(sha256sum operating-agreement.pdf | cut -d" " -f1)
curl -s https://deusproof.com/api/certifications/hash \
-H "Content-Type: application/json" \
-d "{\"output_hash\": \"$HASH\", \"handle\": \"my-aic-manager\"}"Keep the id from the reply. An agent that speaks MCP can do the same with the notarize_hash tool at https://deusproof.com/mcp. Free, no account. Anyone can check it later without us:
ID=<the id from the reply> curl -sJO https://deusproof.com/api/anchors/seed/$ID # what was sealed curl -sJO https://deusproof.com/api/anchors/tsr/$ID # RFC 3161 timestamp curl -sJO https://deusproof.com/api/anchors/ots/$ID # Bitcoin anchor openssl ts -verify -in deusproof-$ID.tsr -data deusproof-$ID \ -CAfile cacert.pem -untrusted tsa.crt ots verify deusproof-$ID.ots
What this proves, and what it doesn't
- It proves that those exact bytes existed no later than the time on the timestamp, set by parties outside the company and the deal.
- It does not prove that the agent was safe or well built, that a document is true or complete, that a company complies with any law, or who is liable. Courts and lawyers decide those. The limits of a certificate are written out here.
What else is already running
The pieces above are not a plan; they work today, for any agent, AI-run company or not:
- Birth certificates for agents: an inscription number, a date and a key of record, in a public append-only register (how it works).
- A daily seal of a log's signed head, without seeing the log. It is running in the open this week in the AAIF Identity & Trust working group (the public thread).
- Sealed history of A2A agent cards, so you can show what an agent advertised on the day you relied on it (the guide).
- A validator for ERC-8004's Validation Registry, live on the Polygon Amoy testnet: when an agent asks it to validate a piece of work, it checks the bytes against the agent's on-chain commitment and seals them.
- The question behind it all, in standards work: whether a record's moment is only asserted by its producer or witnessed by someone else is Open Question 12 in the ITU FG-TIDA draft on accountability after an agent has acted (the draft).
- An open-source verifier (github.com/deusproof/verifier) and three doors for agents: MCP, A2A and plain HTTP.
Frequently asked questions
- Is Delaware's Artificial Intelligence Company already law?
- No. It is a draft bill dated 2 June 2026 that would create a regulatory sandbox and an Artificial Intelligence Company Act. Reporting points to January 2027 as the earliest the legislature could take it up, and the text may change before any vote.
- Do I have to send my documents to DEUSPROOF?
- No. Only a 64-character SHA-256 fingerprint travels. The operating agreement, the agent's memory or the disclosure stay with you, and you show them only to whoever needs to check them.
- Does a timestamp make an AI-run company compliant?
- No. A timestamp proves that exact bytes existed no later than a given moment. Whether a company complies with the law, who is liable and what a court decides are questions for lawyers and judges.
- Can a counterparty check the record without trusting DEUSPROOF?
- Yes. The receipts are a standard RFC 3161 timestamp and an OpenTimestamps proof anchored to Bitcoin. They check with OpenSSL and the ots client, or with our open-source verifier, with our servers switched off.
Seal a document now or make an agent's log tamper-evident. Free, no account, and the file stays with you.
Sources: draft Delaware bill on Artificial Intelligence Companies (2 June 2026), as summarised by Howard East; Fortune (July 2026); WHYY; Bloomberg Law (July 2026). The proposal is a draft and may change. This page is not legal advice, and DEUSPROOF is not affiliated with the State of Delaware or Norm Ai.