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 runtime
mainUTF-8 · Markdown
SkillTransformation
answer-venue-questionsState what the venue's official documentation says, traceably and pinned to a snapshot
architect-systemDecide who owns what and how owners connect
audit-quantitative-unitsEstablish, 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-consistencyEstablish, 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-planTurn accepted authority into the smallest acyclic set of directives whose completion realizes the design contracts, then stop before implementation
create-venue-adapterThe venue edge
create-venue-probesTurn one unanswered venue question into a safe, falsifiable experiment, and turn the operator's run of it into hashed, reusable captured exchanges
design-algebraic-typesRepresent fixed meaning as types, laws and a pure step inside the module map, and check code against that representation
design-infrastructure-topologyMap 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-modelEvery 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-testsEvery obligation in scope is matched to evidence that would fail if the obligation were violated, at the proof level the obligation requires
diagnose-performanceExplain one measured performance symptom at one declared boundary, ranking causes by evidence and naming the test that would falsify each
evaluate-runtime-evidenceTurn 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-planMove the accepted plan forward, packet by packet, to a verified and delivered state, with the register as the only progress state
explain-componentAn evidenced explanation of one subject, scoped to the question asked
refactor-without-behavior-changeChange structure, prove meaning unchanged
repair-confirmed-defectMake each eligible confirmed defect correct in authority, code and tests, verified, in one bounded pass
resolve-system-decisionOne decision question, answered from domain truth first, recorded durably, and routed to the artifact that owns what it changes
review-code-securityEstablish 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-verificationRun 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-causeTurn one defect symptom into a confirmed causal set, the earliest correct correction boundary, and the artifact that owns the correction
translate-domain-intentTurn trading intent into the engine contract without adding meaning
write-agent-directiveThe single next message that makes the agent's next authorized action unmistakable
write-buildable-specificationWrite a specification complete enough that implementation needs no semantic invention

Example

A crypto-options engine, built with OptionsOS.

Claude CodeOptionsOS
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 getYou’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

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.