Background¶
Warning
Pre-implementation. This section describes proposed contracts. Behavior is subject to change before code lands.
Who should read this. Reviewers and contributors who want the why behind the design. If you need the exact contract, not the rationale, go straight to Reference.
Before you start. Skim the four design pillars on the home page and the Concepts section first. This section rationalizes decisions those pages already assume.
What this section is not. It is not a contract. Names, versions, and field lists are normative only on the Reference and API pages; a claim here that disagrees with a reference page loses.
Orientation¶
EMMA (Electromagnetic Multi-task Model Assessment) rests on four pillars: generalization is the score (not in-distribution accuracy); the canonical input is raw, phase-coherent, multi-antenna I/Q (in-phase and quadrature); the benchmark is reproducible by construction; and governance is neutral by design. Each pillar is a deliberate choice with rejected alternatives, and each is defensible against the existing landscape.
Design decisions states the load-bearing choices and what they rule out. Landscape maps the incumbents and the specific gap EMMA targets. Literature is the master citation list every load-bearing claim draws from. Roadmap sequences the releases and the maturation per feature. Open questions names the unresolved decisions and what would resolve each. Governance covers the ring-fence mechanism and the path to an independent operator. Validation points at the six-lens framework that audits the whole design.