FPF Reference

    A.6.P:12 — Relations

    Preface node heading:a-6-p-12-relations:12925

    What this page is

    This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

    Methodology

    Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

    Content

    Specialised by

    • A.6.5 U.RelationSlotDiscipline — slot precision restoration for n‑ary relations.
    • A.6.6 U.BaseDeclarationDiscipline — base‑dependence precision restoration (SWBD + base‑change lexicon + anchor* red‑flags).
    • A.6.8 (RPR‑SERV) — service polysemy unpacking as a relation/facet precision restoration discipline (serviceSituation lens + canonical rewrites + service‑specific tests and change narration).
    • A.6.9 (RPR-XCTX) - U.CrossContextSamenessDisambiguation - Repairing cross-context "same", "equivalent", "align", or "map" via explicit Bridges
    • A.6.H (RPR‑WHOLE) — wholeness language unpacking (“whole/part/integrity/complete”) into boundary, typed parthood, explicit Γ selection, order/time classification, and A.15 completeness/coverage claims.

    Coordinates with

    • A.6.S U.SignatureEngineeringPair — RPR rewrite operations can be packaged as a ConstructorSignature for engineered relation specialisations; must preserve canonical verb mapping and effect‑free constructor semantics.
    • A.19 U.CharacteristicSpace + A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW — for declared characteristic spaces, guarded role references, and interpretive-view and atlas-view discipline when one relation repair needs those layers explicit.
    • G.2 — for palette, front, archive, or tradition-atlas specialization when the repaired passage is SoTA-harvest or synthesis prose.
    • F.18 — when the remaining issue is naming-side choice among candidate labels rather than relation typing or publication-lane repair.
    • C.2.2a, A.16, A.16.1, A.16.2, B.4.1, and B.5.2.0 + C.2.LS, C.2.4, C.2.5, C.2.6, and C.2.7 - relation publication enters only after admissible language-state chart positioning, articulation, and closure record exist; earlier cue-pack material stays on the language-state seam, prompt-shaped continuations stay with B.5.2.0, retreat/reopen moves remain governed by A.16.2, and A.16.0 is used only when lineage, branch, loss, or handoff history must itself be published.

    Candidate extraction signals (informative; not queued specialisations)

    These recurring relation-repair families are signals for applying the E.10.ARCH extraction criterion. They do not by themselves create a new A.6.x pattern.

    • Cross‑Context equivalence / “sameness” discipline (Bridge + loss-note relation patterns)
    • Correspondence/consistency + repair discipline (sync/alignment relation patterns)
    • Transfer/hand‑off discipline (multi‑party “give/assign/accountability” relation patterns)

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)