System Design¶
- Automation Architecture (Hermes Loop) — The Hermes pipeline — a staged loop from news intake to playbook feedback — with an explicit split between LLM and deterministic stages.
status: draft - Data Infrastructure — Vendor data and pricing stack for the system — ThetaData options bars, Tiingo EOD underlyings, py_vollib pricing — and the design constraints they impose.
status: draft - EV Contract (Operational) — The mandatory checklist every expected-value claim must satisfy before a playbook is tradable — attested computation, real-world probabilities, explicit costs, baseline comparison, regime context.
status: draft - Hermes Pilot Reconciliation — the Running System on ai-rig — Maps the live Hermes options-round pilot (tastytrade-mcp marks, ev_ladder, sizing, approval server, Telegram delivery) onto the TOMIC 2.0 framework — what is adopted, what the framework contributes, and the consolidation decisions.
status: draft - Hermes Round Prompts — options-round-analyst and report-builder — The two Hermes cron jobs that run the daily TOMIC 2.0 round on hermesagent — what each prompt enforces, the code contracts it relies on, how the analyst's memory works, the version history, and the procedure for changing a prompt. The canonical prompt text lives in the repository's ops/cron/; this page explains it and does not duplicate it.
status: draft - Position Ledger — the canonical book (closes framework hole #1) — Append-only JSONL position ledger that succeeds the retired round-state.json — v0 schema, backfill-provisioned, fill receipts mandatory once the execution adapter exists.
status: stable - Stage-8 Execution Adapter Charter — The separately governed control plane for the order path — what the execution adapter may do, in what modes, under which approvals; the artifact whose ratification is the precondition for any live money.
status: draft - Telegram Approval Flow — the bidirectional human-in-the-loop channel — Design for moving the stage-7 human gate from localhost-web to Telegram, using Hermes' native clarify-in-Telegram rendering; two implementations (M1 paper-era, M2 execution-era), threat model, and fail-closed rules.
status: stable - Trading Plan (System Skeleton) — A TOMIC-style business plan skeleton, updated with regime-aware risk parameters and links into the playbook library.
status: draft
Back to the bundle index.