Maturity matrix¶

Warning

Pre-implementation. This page describes proposed contracts. Class signatures, parameter types, schema fields, and behavior are subject to change before code lands. Once implementation exists, content here will be regenerated from docstrings or sourced from running tests.

The authoritative per-feature status table. Each task, dataset, schema family, API module, CLI command, and governance instrument carries a version badge (when it ships) and a maturity label (its contract state), using the vocabulary in STYLE.md. The matrix aggregates the per-feature facts recorded in Task reference, Datasets, the Schema reference, the API reference, CLI reference, and the roadmap; when a row disagrees with its source page, the source page wins until this matrix is updated.

Until src/emma/ lands, every API and schema row is proposed-contract, and every task and dataset row is proposed-contract at the maturity its source page records. Items whose contract is not yet pinned are planned.

Vocabulary¶

Maturity labels are the closed set defined in STYLE.md and in the Maturity enum:

Label	Meaning
`planned`	Named roadmap item; no contract yet.
`proposed-contract`	Intended API, schema, or recipe shape; may still change before code lands.
`implemented`	Code exists; examples are runnable.
`verified`	Implementation has contract tests or golden validation.
`deprecated`	Scheduled for removal; use the replacement instead.

Version badges render as in STYLE.md: v0.1 is the emerald live accent for the launch version; plain v0.2 marks a future version.

Tasks¶

All 15 TaskID members, at the maturity recorded in Task reference. The per-task metric, OOD (out-of-distribution) axis, readout head, and domain wiring live there.

Feature	Version	Maturity
`E-LOC-AOA`	v0.1	`proposed-contract`
`E-LOC-LOS`	v0.1	`proposed-contract`
`E-ID-DRONE`	v0.1	`proposed-contract`
`E-ID-FP`	v0.1	`proposed-contract`
`E-ID-AMC` (AMC is automatic modulation classification; continuity column)	v0.1	`proposed-contract`
`E-LOC-POS`	v1	`proposed-contract`
`E-ID-RWAVE`	v0.2	`proposed-contract`
`E-ID-UAVDOP`	v0.2	`proposed-contract`
`E-CH-BEAM`	v0.2	`proposed-contract`
`E-CH-CSI`	v1	`proposed-contract`
`E-SC-SEP`	v1	`proposed-contract`
`E-SC-ANOM`	v1	`proposed-contract`
`E-SC-SENSE`	v1	`proposed-contract`
`E-S2T-CAP`	v2	`proposed-contract`
`E-S2T-QA`	v2	`proposed-contract`

Datasets¶

All 15 dataset ids, at the maturity recorded in Datasets. Recipes that depend on an rfgen feature not yet shipped carry an open dependency flag on their per-dataset page; that flag does not change the maturity here, but it does block scoring until the dependency lands.

Feature	Version	Maturity
`EMMA-LOC-v0.1`	v0.1	`proposed-contract`
`EMMA-DRONE-v0.1`	v0.1	`proposed-contract`
`EMMA-FP-v0.1`	v0.1	`proposed-contract`
`EMMA-AMC-v0.1`	v0.1	`proposed-contract`
`EMMA-REAL-OOD-v0.1` (fidelity only)	v0.1	`proposed-contract`
`EMMA-RWAVE-v0.2`	v0.2	`proposed-contract`
`EMMA-UAVDOP-v0.2`	v0.2	`proposed-contract`
`EMMA-BEAM-v0.2`	v0.2	`proposed-contract`
`EMMA-POS-v1`	v1	`proposed-contract`
`EMMA-CSI-v1`	v1	`proposed-contract`
`EMMA-SC-SEP-v1`	v1	`proposed-contract`
`EMMA-SC-ANOM-v1`	v1	`proposed-contract`
`EMMA-SC-SENSE-v1`	v1	`proposed-contract`
`EMMA-S2T-CAP-v2`	v2	`proposed-contract`
`EMMA-S2T-QA-v2`	v2	`proposed-contract`

Schema families¶

The serialized contracts documented under Schema reference. The two governance records (PreRegistration and ReScoringLog) are listed under Governance below to avoid duplicating the instruments they back.

Feature	Version	Maturity
TaskSpec	v0.1	`proposed-contract`
DatasetRecipe	v0.1	`proposed-contract`
SceneManifest	v0.1	`proposed-contract`
DataReleaseManifest	v0.1	`proposed-contract`
PredictionBundle	v0.1	`proposed-contract`
Submission	v0.1	`proposed-contract`
LeaderboardRow	v0.1	`proposed-contract`
RunManifest	v0.1	`proposed-contract`

API modules¶

The Python modules documented under API reference. Each module ships at v0.1 even when it contains later-version classes (for example the emma.tasks module includes the v2 caption and QA heads).

Feature	Version	Maturity
Primitives (`emma.enums`, `emma.errors`)	v0.1	`proposed-contract`
Schemas (`emma.schemas`)	v0.1	`proposed-contract`
Datasets (`emma.datasets`)	v0.1	`proposed-contract`
Metrics (`emma.metrics`)	v0.1	`proposed-contract`
Tasks (`emma.tasks`)	v0.1	`proposed-contract`
Harness (`emma.harness`)	v0.1	`proposed-contract`
Leaderboard (`emma.leaderboard`)	v0.1	`proposed-contract`
CLI (`emma.cli`)	v0.1	`proposed-contract`
Governance (`emma.governance`)	v0.1	`proposed-contract`

CLI commands¶

The emma command surface, at the maturity recorded in CLI reference.

Feature	Version	Maturity
`emma list-tasks`	v0.1	`proposed-contract`
`emma download`	v0.1	`proposed-contract`
`emma eval`	v0.1	`proposed-contract`
`emma submit`	v0.1	`proposed-contract`
`emma score`	v0.1	`proposed-contract`
`emma release`	v0.1	`proposed-contract`

Governance instruments¶

The ring-fence machinery documented in Governance and scheduled in the roadmap. The v0.1 instruments are proposed-contract; the v1 and later instruments are planned because their contracts are not yet pinned.

Feature	Version	Maturity
Pre-registration (PreRegistration + store)	v0.1	`proposed-contract`
Third-party re-scoring (ReScoringLog + writer)	v0.1	`proposed-contract`
Operational ring-fence (external co-steward)	v0.1	`proposed-contract`
COI (conflict of interest) charter	v0.1	`proposed-contract`
Sandboxed code submission	v1	`planned`
Independent steering committee	v1	`planned`
Independent non-profit operator	v1+	`planned`

Note

The transition from proposed-contract to implemented happens per feature when src/emma/ lands that feature; the transition from implemented to verified happens when the contract tests in Validation pass. No row is implemented or verified today.