FPF Reference

A.6.P:11 — SoTA‑Echoing (informative; post‑2015 alignment)

Preface node heading:a-6-p-11-sota-echoing-informative-post-2015-alignment:11112

Content

Evidence binding note. If your Context maintains a SoTA Synthesis Pack for relation/contract authoring or “qualified relations”, cite it here and keep this section consistent. Otherwise, treat the table below as a seed list (informative only).

A.6.P echoes contemporary practice across independent traditions, while remaining notation‑neutral and Context-local:

SoTA practice (post‑2015)Primary source (post‑2015)EchoWhat A.6.P addsAdoption stance
Constraint/shape validation over graph assertionsW3C SHACL Recommendation (2017)Separates “assertions” from “constraints”Couples structural contracts with lexical guardrails to prevent prose regressionAdopt/Adapt — adopt “explicit contracts”, adapt by binding to Tech↔Plain and rewrite discipline
Qualified statements / reification patternsRDF‑star / SPARQL‑star (2017+) practice familyReification/qualification when hidden arity appearsRequires explicit RelationKind + change‑class lexicon (not just representational qualification)Adapt — representation is not enough without kind selection + change semantics
Architecture views & correspondencesISO/IEC/IEEE 42010:2022Viewpoints and correspondences as first-class concernsForces viewpoint discipline inside relation qualification + prohibits silent polarity flipsAdopt/Adapt — adopt viewpoint accountability, adapt by embedding it into relation records
Bidirectional transformations / opticsPickering et al., Profunctor Optics (ICFP 2017) and successors“Pairs of projections + laws” as stable lensesUses optics as conceptual stabilisers for multi‑view relations while keeping Core notation‑neutralAdapt — use as a stabilising lens, not as mandated notation
Compositional modelling (applied category theory)Fong & Spivak, Seven Sketches in Compositionality (2019)Stable abstract lenses reusable across domainsEmbeds lens choice into an authoring discipline with explicit slots + guardrailsAdapt — keep the categorical lens didactic; operationalise via SlotSpecs + change lexicon

These echoes justify why A.6.P is structured as: stable lens → explicit slots → explicit change classes → lexical guardrails, rather than “just define the verb”.