E.17:5.1c - Shared use-boundary terms

Use these terms when a publication face, rendering, narrower-use rendering, explanation, comparison note, source-finding cue, or authority-looking display can be interpreted beyond its named source relation. Define them once here and link back to this section from local patterns instead of minting local synonyms.

Term	Meaning for FPF use
`orientation use`	The publication-facing unit helps a reader find, inspect, triage, compare, teach, discuss, or prepare planning while the unit itself does not carry a downstream work, reliance, claim, or effect.
`reliance use`	The publication-facing unit is used as the source relation for an engineering claim or effect that changes a next work occurrence or reliance use, such as method choice, work plan, performed-work claim, release, gate, approval, an unresolved role or status phrase routed through `E.10.ROLE`, a recovered classification, assignment, assignment-state or direct-status claim, evidence, assurance, or external-impact action.
`work, reliance, claim, or effect`	A claim or instituted effect about method selection, selected method, `U.WorkPlan`, performed `U.Work`, work result, gate or release, an unresolved role or status phrase routed through `E.10.ROLE`, a recovered local system-role-kind classification, assignment occurrence, assignment state or direct status predicate, evidence, assurance, boundary or policy effect, or another typed project-side FPF kind and reference named by value.
`operative claim`	A claim whose acceptance would change the next bounded work occurrence or reliance use, the typed project-side FPF kind and reference named by value to recover, or the cross-context use of the publication-facing unit. Explanatory prose, examples, and source-finding cues are not operative claims unless they are used that way.
`non-admissible downstream use`	A wider use that the current source relation does not carry. Narrow the use, return to the source-bearing side, recover the missing relation, or apply the concrete work, evidence, decision, bridge, gate, release, or assurance rule that carries the wider claim.
`reopen trigger`	A dispute, use escalation, missing, stale, or contradictory source relation, source update, context or window change, or wider claim that requires source refresh, re-expansion, or application of the concrete rule or test carrying that claim.
`authority-looking case`	A recognition phrase for a publication-facing unit that can be overread as permission, approval, evidence, gate passage, assurance, responsibility, authority, release, or an unresolved role or status claim. It is not a U-kind or authority record. Route the unresolved source phrase through `E.10.ROLE`; then recover the current result: a local system-role kind and classification, an assignment, assignment state, another participant or status predicate, responsibility or authority, actual Work whose exact performer is recovered through A.13 and which A.15.1 admits independently, optional precise F.6 attribution when expressly consumed, ordinary non-use, or the exact missing governor.