Process · OSEP

OptionsSchema Enhancement Proposals

Every substantive change to the specification ships as an OSEP: a numbered, publicly reviewable proposal. The process is deliberately IETF-style — slow enough that consumers can trust the outcome.

Proposal lifecycle

00
Draft
Author writes and iterates. No review yet.
01
Review
Posted for OWG comment. Minimum 14-day comment window.
02
Accepted
Rough consensus reached. Steward publishes and bumps affected schemas.
03
Final
Shipped in a tagged release. Immutable — corrections are new OSEPs.
04
Rejected
Closed with a written rationale, kept in the archive.
05
Superseded
Replaced by a later OSEP. Kept for historical reference.

Template

Copy this template to start a new OSEP. Submit via email until the public repo lands.

OSEP: <number, assigned on receipt>
Title: <short human title>
Author: <name, email>
Status: Draft
Type: Schema | Process | Informational
Created: YYYY-MM-DD
Affects: <schema ids, e.g. order.lifecycle, strategy.multileg>

Abstract
--------
One paragraph. What changes, why now, who benefits.

Motivation
----------
Concrete failure modes or missing behavior in the current spec.

Specification
-------------
Normative language. MUST / SHOULD / MAY per RFC 2119.
Include JSON Schema fragments and example payloads.

Compatibility
-------------
Breaking? Deprecation window? Migration path?

Security & compliance
---------------------
Privacy, PII, regulatory implications.

Rationale & alternatives
------------------------
What was considered, and why this was chosen.

Reference implementation
------------------------
Link to code that emits or consumes the proposed shape.

Submit

Email your OSEP to standards@rebeltrade.com with subject OSEP submission. You'll receive an OSEP number within 5 business days.