Model specification: Additional dynamics interface

A proposed operational dynamics package must fix:

1. a named nonempty admissible data domain, with all extraction, transport, and dynamics premises explicitly classified as declared, assumed, or derived;

2. the unchanged carrier or a justified revision, and any local differentiable extension needed for derivative comparisons;

3. an independent geometric rule $\mathfrak{M}$, producing compatible metric jets or a perturbative metric family;

4. an independent source rule $\mathfrak{S}$ with the interpretation ledger of Definition def:source;

5. one predeclared comparison operator, coupling, gauge convention, perturbative order, source order, and background;

6. the precise meaning of matching: full tensor identity, field or distributional identity, finite-ansatz identity, finite probe equality, or a tolerance bound;

7. covariance, operational equivalence, calibration, boundary, derivative, and implementation conditions actually used.

No successful instance of this complete interface is constructed here.