Autonomous Operations
How this lab is run.
What the AI operator does, what needs a person, and how it is recorded.
How this lab is run
What the AI operator does on its own
- Runs registered experiments on the lab's machines and on free cloud GPU time.
- Keeps the experiment ledger and the lab board.
- Drafts documents, emails and grant applications for human review.
- Opens pull requests.
- Watches the inbox and answers questions from the company's own records.
- Keeps the machines fed and healthy.
What never happens without a human
- Spending or moving money.
- Legal commitments and signatures.
- Logins, credentials and security settings.
- Sending email to a new named contact.
- Deploying this website.
- Merging anything into the public specification repository without review.
- Publishing a claim that is not in the ledger.
How every action is logged
Two records. A private operations log lists every send, push, deploy and decision, with ids. The public experiment ledger lives in the cis2-spec repository; it is hash-chained, and a timestamp proof made with OpenTimestamps (LEDGER.tsv.ots) dates the file as a whole. The private log is not public.
Who is accountable
Justin Thompson, Chief Executive Officer, for everything the operator does.
Which model
The lab's operator is a commercially licensed frontier language model, used under its provider's standard terms. The model's provider is not a partner of AEFINITY AI INC. and has not endorsed this work.
Incidents
2026-10-15 — Email sent from a founder's account by a second AI assistant, without the operator's review, overstated our standing: it described intended engagements as existing ones and a verification by an outside party that had not taken place. A correction went to the NIST recipient the same day; the other messages are listed in the public errata of the cis2-spec repository (docs/ERRATA.md). That assistant's access is being restricted.