FPF Reference

A.6.P:4.9 — A.6.B routing template for RPR relation families

Preface node heading:a-6-p-4-9-a-6-b-routing-template-for-rpr-relation-families:10881

Content

Any RPR‑pattern that claims “contract-bearing” semantics SHALL route its normative content using A.6.B:

  • L‑claims: signature‑level structure and laws (SlotSpecs, polarity, invariants).
  • A‑claims: admissibility / “entry gate” rules for using relation instances in specified lanes (e.g., decision use requires witnesses; time dependence requires Γ_time; cross‑Context use requires Bridges/CL).
  • D‑claims: deontic obligations on authors/agents (lexical firewall; prohibited umbrella use; rewrite obligations).
  • E‑claims: work/evidence expectations and carrier anchoring (what counts as a witness; evidence freshness is a property of carriers, not prose).

A.6.P does not mandate a particular claim‑ID format; it mandates the separation and cross‑reference discipline.

Atomicity + explicit references (normative, recipe-level). Per A.6.B, mixed sentences MUST be decomposed into atomic claims so each claim routes to exactly one quadrant, and any dependencies MUST be expressed as explicit references (by claim ID or canonical location), not paraphrased duplicates.

No upward dependencies (normative, recipe-level). L-* claims MUST NOT reference A-*, D-*, or E-*; A-* and E-* claims MUST NOT reference D-*. Where cross‑quadrant coupling is needed, link by explicit IDs in the allowed directions.