A.7:11 - SoTA‑Echoing

• Digital twins (ISO 23247-1/-2, 2021). The public previews of Part 1, §§3.2.2–3.2.5 distinguish observable manufacturing elements from synchronized digital representations; Part 2, §§3.5/5.2.3–5.2.4 distinguishes implementing and management systems and permits a digital-twin entity to denote a system or systems. Adapt: distinguish the representation from its implementing System, and identify the FPF kind from the actual referent.
• Observability (OpenTelemetry). Semantic Conventions 1.44.0 defines attribute meanings; the Specification Overview 1.60.0 and exporter description distinguish export components and their data mappings. Adapt: keep semantic definitions and transport or representation mappings distinct. Publication-face and publication-form orthogonality is the FPF use of that distinction.
• Active inference. In Active Inference: A Process Theory (2017), §§2–2.2, Friston, FitzGerald, Rigoli, Schwartenbeck and Pezzulo distinguish a generative model, policies, the generative process, and the action/observation cycle. Adopt this historical model/action distinction for A.7’s referent recovery; identify the model and acting System under their own FPF rules.
• Constructor theory. Deutsch’s Constructor Theory, arXiv:1210.7439v2 (17 January 2013), §§1.1/2.14/2.15 distinguishes tasks and constructors and also treats information and knowledge as abstract constructors. Marletto’s Constructor theory of life (2015), §3.1 retains embodied knowledge’s constructor role; her Constructor Theory of Thermodynamics (2016) concerns thermodynamic work and work media. Adapt the historical task/realization distinction. A.7 uses that distinction without assigning these source meanings of knowledge or thermodynamic work to U.Episteme or U.Work.
• Quality-diversity (MAP-Elites). In Illuminating search spaces by mapping elites (2015), §3/Fig. 2, Mouret and Clune describe storing candidate solutions by feature-space cell and retaining the best found for an occupied cell. The returned feature-performance map differs from the run producing it; default parent selection chooses one elite. Adopt and adapt this historical archive/execution distinction and collection-valued output example; govern any FPF typed-space or order claim by its own rule.
• Formal verification and quantities. LiquidHaskell: Experience with Refinement Types in the Real World (2014), by Vazou, Seidel and Jhala, presents logical refinement predicates and contracts. Koenig and Leino’s Programming Language Features for Refinement, KRML 248 (2015), together with the Dafny Reference Manual’s refinement section, describes restricted program refinement. uom 0.38.0 supplies dimension-safe quantities with declared units and conversions. Adapt these distinct practices to motivate the specification-use boundary: the claiming specification, formality, refinement, measurement-criterion, and publication patterns govern the applicable check, law, and pins.