Specification

Draft v0.1

Scope

OptionsSchema defines a small set of interoperable object types that describe options market data, model output, and execution intent. It is a data contract, not a protocol: transport, authentication, and settlement are out of scope. A conforming producer emits objects that validate against the published JSON schemas; a conforming consumer accepts them without side agreements.

Core objects

InstrumentA listed underlying or option contract. Ticker + expiry + strike + side.
StrategyA named, multi-leg construction (vertical, condor, calendar, etc.).
AlertA detected market event — UOA print, gamma shift, level break.
OrderA broker-agnostic order intent. One or more legs, type, TIF.
RouteHow an Order is handed off to a specific broker or OMS.
VerdictA model output — Buy / Sell / Wait, probability, confidence.
AgentActionA logged, replayable action taken by an autonomous agent on behalf of a user.

Versioning

Every published schema carries a semantic version and a deterministic URL of the form /options-schema/registry/<category>/<id>@<version>. Breaking changes bump the major segment; additive fields bump minor; documentation and constraint tightening bump patch. Older versions remain resolvable.

JSON Schema conformance

All registry entries are JSON Schema 2020-12 documents. Producers SHOULD validate emitted payloads against the schema before delivery; consumers MUST reject payloads that fail validation. Unknown fields are permitted but MUST NOT change the meaning of known fields.

Change process

Proposals are opened as issues on the project repository, discussed in public, and merged after two independent implementations verify the change. The registry is the source of truth; this document describes the rules the registry follows.