Normative design documents still required

This requirements baseline intentionally does not answer every implementation question. The following design documents must be written and approved before implementation of their dependent subsystems:

1. Reference Benchmark and Qualification Plan — resolves the distributable reference scenario, analytical and numerical qualification including dynamic-analysis reference cases, official regression fixtures, evidence-source policy, reproduction and performance workloads, and optional independent-data comparisons without requiring new physical data collection.
2. Canonical Model Specification — entity identity, numeric categories and persistence encodings, units, frame graph, schemas, engineering-property type/version and value forms, runtime-action reference payloads, namespaces, extensions, and migrations.
3. Simulation Time and Coupling Specification — integer-tick and rational-time-base details, event phases, multi-rate scheduling, checkpoints, runtime-action admission, ordering, atomic commit and safe mutation boundaries, and determinism classes.
4. Mechanics Backend Contract — capability taxonomy, model compilation, state exchange, generalized-coordinate conventions, dynamic-analysis queries and derivatives, diagnostics, and conformance.
5. Environment and Material Semantics — fields, surfaces, wetness, weather effects, property-family semantics, state-dependent relation evaluation, interpolation, extrapolation, history, capability binding, provenance, and validity.
6. Device, Power, and Sensor Semantics — ports, energy accounting, timing, signal chains, faults, and model equations.
7. Controller and ML API Specification — lifecycle, reset and supervised-restart semantics, observation/action schemas, state and control derivatives, linearization artifacts, batching, randomization, motion-planning boundaries, and sandboxing.
8. Experiment and Result Schema — runs, runtime-action plans and receipts, sweeps, user-authored regression cases, baselines and results, calibration and identifiability records, metrics, manifests, traces, snapshots, comparisons, and retention.
9. Extension and Integration Protocol — Wasm/process lifecycle, permissions, shared data, ROS 2, FMI, and HIL boundaries.
10. Security and Dependency Policy — unsafe code, parsers, native exceptions, SBOM, signing, and incident response.
11. Editor Information Architecture — authoring flows, inspection, diagnostics, plots, and accessibility.
12. Release and Compatibility Policy — supported platforms, versioning, migrations, deprecation, and release gates.

Change rationale (section 32, item 1): ADR-0001 replaces the unapproved physical-mission-first draft with a simulation-first benchmark plan. The renamed design makes distributable fixtures, analytical and numerical qualification, property/effect disclosure, convergence, reproduction, and explicit evidence status the implementation-facing baseline while retaining optional independent and physical evidence as stronger, clearly classified claim tiers.

Change rationale (section 32, items 1–4, 7, and 8): The v0.4 runtime-action, simulation-regression, motion-planning, and dynamic-analysis requirements extend existing cross-cutting contracts. Their fixtures, persisted identities, event phases, mechanics semantics, controller lifecycle, and evidence must be resolved in the already required designs; adding requirements does not approve those designs or authorize incompatible implementation shortcuts.

Change rationale (section 32, items 2–3, v0.7): ADR-0006 settles the shared representation direction, but the Canonical Model design still owns exact schema encodings and conversion envelopes while the Simulation Time design owns tick scale, horizon, rational scheduling, overflow, and sequence allocation. The accepted ADR does not substitute for either design's approval.