Aumos documentation

How to write a manager, and how to write a data source. For people making one, not for people choosing one.

Aumos runs AI fund-manager harnesses against a real portfolio through a standard decision protocol. It does not host a model and holds no model API key: it starts the CLI coding manager you already subscribe to — claude, codex — as a child process, hands it your package as a plugin and an MCP server to answer through, and files what comes back. A manager proposes; only the Kernel changes state; every judgement is appended to a hash-chained journal that is verified by recomputation rather than trusted.

What you can build

What happens when your manager runs

1. An investor installs your package into one portfolio, choosing the vendor and model it runs under and how often it should be woken.
2. A run starts — on a cadence, on an event, or because somebody pressed the button. The CLI is launched as a different OS account, in a per-run writable copy of your package, with that copy as its plugin directory.
3. The session reaches Aumos through one MCP server. It reads its invocation, calls whatever its capabilities entitle it to, and submits exactly one judgement with decision_submit. That call is what ends the run.
4. The Kernel rules on the judgement against the investor's mandate, seals it into the journal, and — if it implies an order — puts it in front of a person. Nothing reaches a venue without that.

Three rules that shape everything you write

• You cannot trade. There is no broker:write capability to ask for — the enum has no such member, so the request cannot be spelled. Orders reach a venue through one path, and a person approves each one.
• You are pinned to an instant, not fenced behind one. Every invocation carries an asOf, there is no default for it, and a gateway call without one is refused — so what you asked, and as of when, is always answerable. What is not promised is that the answer was bounded by it: a data source relays a vendor's response unread, and a session reaches the open web on its own.
• Doing nothing is an answer. WAIT and WATCH are first-class judgements, argued and scored exactly as a BUY is. A manager that returns a bare WAIT with no reasons fails conformance.

Reference

Generated from the repository, and needed only when you are implementing the protocol outside Aumos. Writing a package needs neither page.