E.18:12 - SoTA-Echoing (post-2015, multi-Tradition)
Each row states the source idea, the FPF invariant E.18 adopts, the practitioner implication, and the shortcut it rejects. Vendor, tool, and literature tokens are informative; the invariant and practitioner implication carry the pattern explanatory work.
| SoTA source idea | FPF invariant | Practitioner implication | Rejected shortcut |
|---|---|---|---|
Applied category theory and compositional open systems (Fong and Spivak, Seven Sketches in Compositionality, Cambridge University Press 2019; arXiv 1803.05316 source draft). | Use one TransformationFlowStructure whose loci are structure-positioned transformation and slot-filler values and whose links use the single relation kind U.Transfer; morphism language expresses mathematical composition only when the mathematical lens is current and supplies no transformation-composition claim. | Name the selected structure, locus kinds, one U.Transfer, and any current path or crossing before treating a work or method sequence as structure semantics. | Treating category-theory prestige, tool pipelines, lineage packages, or work and method narratives as selected-structure or transformation-composition semantics. |
Operads, wiring diagrams, and hypergraph categories (Spivak, The operad of wiring diagrams, arXiv 1305.0297; Baez and Fong, A Compositional Framework for Passive Linear Networks, arXiv 1504.05625). | Typed ports and junctions motivate explicit source and receiving positions and commuting-square checks; the mathematics does not supply locality, plane, edition, gate, policy, or semantic-Bridge truth. | At a structural crossing, name each changed binding’s from/to values and establishing basis, any applicable rule and current application, the separate gate decision, and CrossingRef; invoke F.9 only for separately tested local senses. | Treating a diagram, Bridge Card, UTS row, CL, gate result, permission, or policy label as sufficient crossing evidence. |
Open-graph and string-diagram rewriting (Bonchi, Gadducci, Kissinger, Sobocinski, Zanasi, Rewriting modulo symmetric monoidal structure, arXiv 1602.06771; Patterson, Spivak, Vagner, Wiring diagrams as normal forms for computing in symmetric monoidal categories, arXiv 2101.12046). | Rewrites and subflow refactors are admissible only with edition bumps, sentinel scopes, and PathSlice locality sufficient for replay. | Localize the rewrite to the affected subflow or slice, pin editions, and re-emit affected faces. | Treating a global rewrite as replay-safe because the diagram still looks equivalent. |
Research-package portability and RO-Crate-style research packaging (Soiland-Reyes et al., Packaging research artefacts with RO-Crate, arXiv 2108.06503; RO-Crate 1.2 as format lineage). | Portable package descriptions belong in MVPK faces and InteropCards; packages and lineage metadata do not define selected-structure semantics. | Publish package, provenance, and source refs as publication references while keeping structure meaning in the locus/gate definitions. | Treating a crate, package, file bundle, or lineage record as the semantic authority for the selected structure. |
Reproducibility and content addressability (Di Cosmo, Gruenpeter, Zacchiroli, Referencing Source Code Artifacts: a Separate Concern in Software Citation, arXiv 2001.08647). | Stable identifiers become edition pins and entries in E⃗; they make references checkable but do not decide locus, gate, or mechanism meaning. | Pin the exact editions of code, comparator, transport registry, descriptor map, or distance definition used by a face or path. | Treating an identifier, hash, or content-addressed source ref as semantic authority. |
TAMP, dynamic planning, and control practice (Zhao et al., A Survey of Optimization-based Task and Motion Planning, arXiv 2404.02817; Shen et al., Motion Planning in Dynamic Environments, arXiv 2606.02677, as current dynamic-motion survey context). | Iteration is represented only as a budgeted Selection-Planning loop with freshness checks; a pre-run gate consumes an intended work-entry claim, and actual launch values obtain only through direct relations or bindings of a later exact Work occurrence. | Declare the loop budget, freshness-request boundary, next PathSlice, exact work-entry claim, and later Work occurrence plus any separate finalization witness. | Turning E.18 into an ordered work-method narrative, an unbounded loop, a future-Work target, or pre-Work actual-value claim. |
Quality-Diversity and illumination search (Mouret and Clune, Illuminating search spaces by mapping elites, arXiv 1504.04909, lineage; Chalumeau et al., QDax, arXiv 2308.03665; Ding et al., QDHF, arXiv 2310.12103; Bradley et al., QDAIF, arXiv 2310.13032 for feedback-guided cases). | Set and archive returns stay visible; E.18 treats covert scalarization to one winner as non-conformant while leaving selector, archive, dominance, and comparator semantics to the named definitions and tests. | Return the set or archive, pin comparator and descriptor or distance editions, and cite the selector and comparator definitions or tests for current cases. | Collapsing a partially ordered or archive-like result into a single best score. |
Profunctor optics and modular projection practice (Pickering, Gibbons, Wu, Profunctor Optics: Modular Data Accessors, arXiv 1703.10857; Clarke et al., Profunctor Optics, a Categorical Update, arXiv 2001.07488, as later refinement). | A publication form may express a selected view episteme or mathematical description for one bounded use, and a carrier may bear that form; neither becomes the view, selected structure, or represented object. | Publish the exact selected episteme through E.24.PUB form-expression, carrier-bearing, and publication relations; use C.29 only for a separately obtaining representation relation, while using their own definitions and tests for transformations and checks. | Treating a form, carrier, screen, representation, or explanation as a view, transformation, evidence result, or gate decision. |
Cross-tradition note. Rows 1-3 (compositional graph practice), rows 4-5 (publication and reproducibility practice), row 6 (controls and robotics), row 7 (evolutionary search), and row 8 (programming-language semantics) jointly position E.18 across multiple traditions per E.8, but each row is retained only because it changes a practitioner implication or rejected overread.