Build trading engines with AI
Describe an engine in plain language. Your AI designs, builds, tests and corrects it on OptionsOS’s crypto-options libraries.
How OptionsOS is built
AGENTS.md — options-os
options-os › AGENTS.md
25## Task entry and engineering construction2627Treat the latest user instruction as the scope and authority for the current task.2829Before mutation:30311. classify the request as analysis, specification, implementation, verification, delivery, or32 external operation;332. identify the highest-authority specification governing the requested behavior;343. identify the affected packages, declarations, behaviors, consumers, and engineering layers;354. distinguish directly authorized work from adjacent findings;365. continue from an accepted plan or execution record when one governs the task;376. preserve unresolved semantic decisions rather than inferring them.3839Before creating, moving, or changing code, classify each affected declaration and behavior as a40primitive, enum, object, algebra, morphism, pipeline, program, interpreter, effect, or runtime1# Options OS Crypto-Options Domain Profile23## 1. Purpose and semantic boundary45### 1.1 Identity and purpose67| Field | Declaration |8| --- | --- |9| Profile ID | `crypto-options` |10| Profile kind | Domain model and semantic contract |11| Definition version | `1.0.0` |12| Primary domain | Crypto options |13| Supporting domains | Crypto assets, spot, futures and perpetuals used for strategy, hedging, valuation, carry, collateral or settlement |14| Instantiation | An engine selects its supported contexts and binds the required authorities under §7 |1516This profile establishes the concepts, meanings, relationships and lawful transformations within which an Options OS agent reasons. It supplies a shared domain for specifying, constructing, analysing and verifying crypto-options systems. It is a semantic model, not a wire format, repository layout, execution schedule or prescribed strategy.1718The domain is closed enough when admitted objects have defined meanings, operations have typed boundaries, compositions have stated conditions and extensions preserve or explicitly revise existing laws. Closure does not require every venue, strategy or analytic technique to be known in advance.1920An agent may derive new structures, compose compatible operations, select models, investigate hypotheses and construct engine policies. New work must make its concepts and assumptions explicit within this domain. A new interpretation is introduced through §7.4 rather than hidden in a field, formula or adapter.1---2name: translate-domain-intent3description: Translate a filled Trading System Intent (`intent.md`), or trading intent mapped onto it, into one concrete engine's contract — the four peer documents SPEC.md, DECISION_MODEL.md, OPERATIONS.md, SCENARIOS.md and the contract map under `specifications/engines/<engine-id>/` — written together in one step. Every rule carries its intent origin; every condition is classified veto or preference; every decision family carries an acting-decision record with grounded rejections, a declared no-action result and a measured liveness band; open meaning becomes UNRESOLVED, never an assumption. Use at the start of a trading-system build, when an engine's trading intent changes, or when a traced defect's cause is engine meaning or evidence. Does not select libraries, partition modules, design types, or choose implementation.4---56# Translate domain intent78## Responsibility and modes910One responsibility: turn trading intent into the engine contract without adding meaning.1112| Mode | Typed input | Output artifact |13|---|---|---|14| `NEW_ENGINE` | filled intent (`intentPath`) or intent mapped onto the intent; engine identifier | `specifications/engines/<engine-id>/{SPEC,DECISION_MODEL,OPERATIONS,SCENARIOS}.md`, `support/CONTRACT_MAP.json`, `support/CONTRACT_MAP.leaf.json`, `support/INTENT_TRANSLATION.md` |15| `UPDATE_ENGINE` | changed intent, or a confirmed engine-specification cause; existing engine directory | the same set, updated as one change, plus a rule delta |1617The four documents are one contract. They are written, amended and accepted together; a change to one peer is re-checked against the other three in the same invocation.1# Options OS Trading Engine Specification23## 1. Contract purpose and authority45This specification defines the strategy semantics of one concrete Options OS trading engine and governs the composition of the complete four-document engine contract.67It defines what the engine means, what it believes, which actions it can consider, how it values their consequences, which risks it may accept, and which operational obligations an accepted decision creates.89The complete contract consists of:1011* `SPEC.md`: strategy authority;12* `DECISION_MODEL.md`: universal decision-semantics authority;13* `OPERATIONS.md`: operational and integration authority;14* `SCENARIOS.md`: required composition and evidence corpus.1516`_framework/grammar/definitions.md` is the semantic authority for the grammar, classification, disposition, and vocabulary these documents instantiate.1718No document may duplicate a production owned by another document. A document may reference another document's production but must not redefine it. Concrete engine specifications complete the variation points in this document and in `DECISION_MODEL.md`.1920No implementation, runtime observation, scenario, or adapter may redefine this contract retroactively.mainUTF-8 · Markdown
| Skill | Transformation |
|---|---|
answer-venue-questions | State what the venue's official documentation says, traceably and pinned to a snapshot |
architect-system | Decide who owns what and how owners connect |
audit-quantitative-units | Establish, with evidence, whether every material quantity in a bounded scope carries a complete, authoritative unit and is converted only on owned, explicit edges |
audit-trading-state-consistency | Establish, with evidence, whether trading state stays causally, temporally and financially coherent across every path that changes it, including paths that are not fills |
create-implementation-plan | Turn accepted authority into the smallest acyclic set of directives whose completion realizes the design contracts, then stop before implementation |
create-venue-adapter | The venue edge |
create-venue-probes | Turn one unanswered venue question into a safe, falsifiable experiment, and turn the operator's run of it into hashed, reusable captured exchanges |
design-algebraic-types | Represent fixed meaning as types, laws and a pure step inside the module map, and check code against that representation |
design-infrastructure-topology | Map every logical participant, owner and edge already declared by the assembly onto physical resources, so that the declared semantics — single writers, edge guarantees, the step contract — survive placement, failure and recovery |
design-relational-data-model | Every durable fact is stored once, by the writer the architecture names, and decodes to exactly the value that was encoded or fails with a declared error |
design-tests | Every obligation in scope is matched to evidence that would fail if the obligation were violated, at the proof level the obligation requires |
diagnose-performance | Explain one measured performance symptom at one declared boundary, ranking causes by evidence and naming the test that would falsify each |
evaluate-runtime-evidence | Turn a fixed evidence cut into a judged account of decision episodes — what happened, whether it was right, and whether the engine acts as often as its mandate says it should |
execute-implementation-plan | Move the accepted plan forward, packet by packet, to a verified and delivered state, with the register as the only progress state |
explain-component | An evidenced explanation of one subject, scoped to the question asked |
refactor-without-behavior-change | Change structure, prove meaning unchanged |
repair-confirmed-defect | Make each eligible confirmed defect correct in authority, code and tests, verified, in one bounded pass |
resolve-system-decision | One decision question, answered from domain truth first, recorded durably, and routed to the artifact that owns what it changes |
review-code-security | Establish which security weaknesses in a bounded scope are confirmed, with reachable paths and evidence, which remain candidates, and which artifact owns each correction |
run-test-verification | Run the gates an authority requires on one pinned candidate and record exactly what ran, what it reached, and what it observed — with the identities each record needs to be judged later by someone else |
trace-defect-cause | Turn one defect symptom into a confirmed causal set, the earliest correct correction boundary, and the artifact that owns the correction |
translate-domain-intent | Turn trading intent into the engine contract without adding meaning |
write-agent-directive | The single next message that makes the agent's next authorized action unmistakable |
write-buildable-specification | Write a specification complete enough that implementation needs no semantic invention |
Example
A crypto-options engine, built with OptionsOS.
Build an engine that captures volatility premium on crypto options: fully automated, defined-risk, delta-managed and short volatility, trading on Deribit, OKX, Coincall and Derive. My risk limits are in mandates/.Engine
volatility-premium-capture-engine/
- Engine contract3OPERATIONS · SCENARIOS · SPEC
- Libraries23adapter-core · canonical · config · fact-freshness · hedging · instrument
- Venue adapters4coincall · deribit · derive · okx
- Tests834test files across the engine, libraries and adapters
- Completed work9656 plans · 18 decisions · 13 specs · 6 evidence · 3 defects
| What you get | You’ll need |
|---|---|
| Templates for the engine intent and contract, each document’s job defined. | Enough software engineering to review your agent’s changes, run tests and check the engine behaves as specified. |
| Libraries for exposure conventions, costs and friction, and risk limits. | A GitHub account |
| Venue integration, with Deribit as the reference adapter. | Claude Code or Codex, with a reasoning model |
| Claude Code and Codex procedures from specification to maintenance. | Linux or WSL2, Python 3.12, Git and Make |
| Workflows, routing, agent hooks and checks that connect the work. | |
| Contracts, plans, progress records and evidence to continue from. |
Your engines, venue credentials and agent stay in your own environment. Deployment, capital and live approval are yours.
Get it
Opening Stripe…
We couldn’t open Stripe. Try again, or contact Support.
This product isn’t available to buy. See Available or contact Support.
The offer has changed. Review the current price and terms before continuing.
We can’t confirm your payment yet. Check your receipt or contact Support before paying again.
Payment cancelled. You’re back at OptionsOS.
Payment didn’t go through. Check your details and try again.
- Licence
- $149 USD once for one person, for your own trading account or company. Each further person needs a licence.
- Access
- After payment, a private GitHub invitation to the username you enter in Stripe.
- Payment
- Pay through Stripe. Enter your email and GitHub username there.
- Updates
- Updates while maintained; received versions stay usable. A successor under a new name is a separate purchase.
- Refunds
- Digital purchases are non-refundable.
- Help
- Email bella@leanos.tech for help getting it working. Reply to your purchase email for access recovery.