Aumos 문서

매니저를 만드는 법과 데이터 소스를 만드는 법. 만드는 사람을 위한 문서이고, 고르는 사람을 위한 것이 아닙니다.

이 아래 설명 본문과, 카탈로그가 저장소에서 실어 오는 것들(요약·방법론·README·라이선스 고지)은 영어입니다. 저장소의 문서에서 생성되는 것이라, 한국어판을 두는 일은 웹에 번역을 붙이는 것이 아니라 원본 문서를 두 벌 유지하겠다는 약속이 됩니다 — 아직 하지 않은 약속입니다.

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.

무엇을 만들 수 있나

실행되면 무슨 일이 일어나나

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.

작성하는 모든 것을 규정하는 세 가지

• 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.

레퍼런스

저장소에서 생성된 문서이고, Aumos 밖에서 프로토콜을 직접 구현할 때만 필요합니다. 패키지를 만드는 데에는 두 페이지 모두 필요하지 않습니다.