Izawi Corporation · Annual Report · Year One年次報告書
A multi-asset trading system — equities, options, perpetuals — engineered end to end by an orchestrated AI workforce, on hardware in one room.
The Premise前提
The leverage isn't the model — it's the organization. Any single AI agent writes code. What ships a system is structure: executives that hold direction, directors that break down work, and builders whose output is never trusted until an independent machine reviews it.
Some of the corporation's products are its own machinery: Atlas Dispatch, the workbench that moves every task from written specification to reviewed merge, and Hermes, the agent harness its Site Directors run in. Others are ordinary shipped work — newsletters, the written personas of its own staff, field bots that reach the floor from anywhere. Atlas, the trading system in Act III, is the largest product, not the only one. The full shelf sits below.
What follows is the building, floor by floor: the hardware it stands on, the corporation that runs inside it, and the flagship system that corporation produced.
Act I · The Lab第一幕
Everything runs on hardware I own. Five machines carry the workforce and the trading system; the infrastructure behind them appears here by function only. That is deliberate.
Act II · The AI Corporation第二幕
It runs like a company because it is one. Direction flows down. Work flows up. Nothing merges without a second machine's signature. The three Site Directors — Robin, Raven, and Wren — are named for the machines they live on. Tap any role to read its posting.
承認MERGED
TAP A ROLE TO READ ITS POSTING
This structure — not any single model — is what shipped the system.
Interlude · Anatomy of a Task工程
The machinery is a product too: Atlas Dispatch, the workbench the corporation runs on. It turns a mission into a written task with acceptance conditions, dispatches it to a builder–reviewer pair, and records the evidence and the verdict in HQ. The three Site Directors run inside Hermes, the corporation's agent harness; builders and reviewers work as bare CLI agents — the same seats, whatever model happens to occupy them.
The roles are shaped this way on purpose. A builder produces one bounded change and must show its evidence. A paired reviewer's job is to find what the builder missed, because agreement is not a control. Compliance blocks whatever fails its checks, because confidence is not evidence. Forty registered agent identities fill three roles across three worker sites — kept separate so that authorship, review, and authority never sit in the same seat.
Above the pairs, the executive layer runs as persistent tmux sessions, joined to each other by a bidirectional message channel. The Chief Operating Officer tasks work out. The Chief Technology Officer reviews specifications and architecture. The Chief Financial Officer signs off before anything touching capital ships. Each persona begins as a written bootstrap charter — the org chart is documents before it is sessions.
The mix of minds is deliberate: three current frontier models on one floor, each where it is strongest. Claude Opus 4.8 holds the operating and financial seats. Codex 5.6 Sol holds the technology seat, the directors' desks, and the builders' keyboards. Kimi K3 sits across the review table. The family that writes a change is never the family that approves it. Models are listed as of this printing — the seats outlast their occupants.
Act III · Atlas第三幕
Four planes, described at altitude. What each part does is public. How it does it is the company's business. Tap any subsystem for its one-line brief.
Capabilities能力
By the Numbers実績
COMPLETIONS IN EVERY CLOCK HOUR OF THE LEDGER'S DAY · 24/24 · AS OF JULY 16, 2026
The Builder創業者
Elsewhere — generated by AI, curated by me. And AI.