E.4.PFR:3.3 - Relation functions keep their own semantics
| Relation function | Admissible use | Exact defining or constraining locus |
|---|---|---|
| Pattern-use recommendation | Recommends or sequences a candidate pattern use for a concern; actual application remains separate. | E.11.PUR |
| Specialization | Narrows parent content through exact inherited content plus child delta and stated use boundary. | parent content and E.8 |
| Framework-architecture answer: initial pattern-relation choices | Asserts each direct relation among selected initial patterns whose truth changes the selected architecture answer or its stated consequences, using the predicate that defines that relation; the one E.9 answer records which choices were selected and why. Add a PFR row only when a named maintenance use needs a stable representation. | the pattern that defines or constrains each asserted relation; E.9 for the selected answer; E.4.PFAD for its framework-specific profile |
| Publication relation | Makes selected content available through a publication occurrence, form, unit, view, carrier, readme, preface, card, or table of contents. | E.11, E.17, E.24.PUB |
| Access relation | Describes bounded access to selected framework content or guidance through a skill pack, MCP-backed service, retrieval route, or assistant integration. | exact access claim plus E.11/E.17; C.35, A.15, A.10, B.3, E.9, or G.11 only when their distinct output is current |
| Framework edition dependency | States that one dependent edition’s content or result for a named use requires exact content from one relied-on edition: removing that content or changing it in a way relevant to the use would invalidate the dependent content/result or require that use to be reopened. It makes no compatibility claim. | E.4.PFR:3.4 for the defining predicate; E.5.3 only for allowed direction and Core acyclicity; G.11 only for currentness and refresh |
| Framework edition compatibility | States whether one exact pair supports a named overlapping use across a stated difference or interface, with its impact and reopen condition. If the basis is insufficient, make no positive compatibility claim. | C.2.1 assertion identity and E.4.PFR:3.4 |
| Preservation relation | States that one carrier, edition, profile, or projection preserves selected structure for a licensed use. | C.34, with C.33 for local carrier loss |
| Generated-result architecture-use admission | States whether an exact generated or discovered result may enter the intended architecture use, with its truthful kind, obtaining or proposed organization, next-use condition, and limit and return. | C.35 |
| Quality framing, evaluation, or improvement | Frames a question, evaluates FPF/DPF/pattern adequacy, or records repeated improvement. | E.22, E.2.DA, E.4.DPF.DA, E.21, E.23 as selected by the exact object |
| Selected-set result declaration | States the selector-facing result kind, exact scope, selection or inclusion conditions, members, ordering, named use when required, and basis pins. It establishes no availability occurrence. | Use G.5 for this declaration. If publication is separately current, use E.17 for a source-backed face and return to source and E.24.PUB for the publication occurrence and audience availability. |
| Source or decision reuse | Uses an exact source line, SoTA pack, DRR, selected answer, accepted decision, or evidence/source claim by value for a bounded use. | G.2 for source/SoTA; E.9 for the DRR and selected answer; the exact separate acceptance decision plus its authority relation or local rule for accepted-decision reuse; A.10 only for an evidence-use claim |
| Direct subject relation | States one exact relation or classification under its defining predicate and current case facts. | the exact subject pattern and C.2.1 assertion identity |
The direct assertions, not a PFAD or PFR row, state the architecture-bearing relation facts. The E.9 DRR records their selection and rationale; E.4.PFAD adds no relation or second decision result. An optional PFR row may point to an exact assertion for maintenance, but it neither creates that relation nor becomes a condition for accepting the answer.
There is no Subject-pattern relation. When earlier prose says that one pattern contains the defining content for or governs a value, claim, boundary, relation, record form, or use, recover the subject assertion and exact relation function. Preserve genuine non-pattern ownership, legal or institutional authority, source attribution, evidence, and other direct relations.