E.17:5.1d - Compact boundary aid for the present claim or effect

When a publication-facing unit, publication face, rendering, narrower-use rendering, explanation, comparison note, dashboard tile, credential view, status view, carrier, or generated unit creates more than one possible interpretation, separate the claim being made or effect being used now and cite the source relation that makes that claim recoverable. This compact boundary aid applies only to the present claim or effect; it does not classify the whole unit. The same unit can expose several typed records; handle one claim or effect at a time instead of assigning one source relation to the whole unit.

Mixed-case precedence. When several publication-use patterns appear possible, repair the smallest unstable interpretation that changes the current bounded use before applying a neighboring pattern whose claim or effect is present:

If one local head is the only unstable part, apply E.17.AUD.LHR or C.2.P and stop when the repaired sentence names the local kind, relation, and bounded use.
If the bounded PublicationUnit or the interpretation of its primary subject is unstable, apply E.17.AUD or E.17.AUD.OOTD before using E.17.ID.CR or E.17.EFP. Use EntityOfConcern(E) for that subject only when the unit carries one identified claim-bearing episteme E and both name the same exact entity.
If the unit is stable and the present problem is comparison overread, apply E.17.ID.CR; use F.9, C.11, A.20, or A.21 only when equivalence, recommendation, selection, decision, gate, or release claim is actually being made.
If the unit is stable and the present problem is explanation overread, apply E.17.EFP; use A.10, B.3, A.20, A.21, or A.15.4 only when evidence, engineering-justification, gate, release, work, or reliance claim is actually being made.
If the present problem is a durable reusable name, UTS row, Core-facing term, or cross-context naming relation, apply F.18; otherwise keep the lighter local repair pattern.

Present claim or effect question	Apply or recover
Is the face being used to guide work or reliance by appearance while the acting user still lacks the concrete project-side relation?	Use `A.15.4` to repair appearance-based reliance, then recover the actual `A.15`, `A.15.1`, `A.10`, `B.3`, `A.20`, `A.21`, `A.2.8`, `A.2.9`, `A.6.B`, or other project-side reference needed by that use. If that exact relation is already the live question, use it directly.
Is the publication-facing unit being used as evidence, provenance, attestation, currentness, freshness, or a claim-bound evidence relation?	Use `A.10` for the evidence/provenance path. When currentness or freshness is itself claimed, cite the G.11 result and let A.10 represent only the bounded source-to-use path.
Is the publication-facing unit being used as engineering justification, assurance, confidence, readiness, or limitations relation?	`B.3` assurance or engineering-justification claim with evidence, limits, and decay explicit.
Is the publication-facing unit being used as gate passage, constraint validity, adjudication, or release decision source?	Recover the exact `A.20` constraint result or `A.21` gate result and the applicable rule, subject, source results, scope, window, and action consequence. Add a log, replay witness, freshness result, or evidence path only when the governing rule or receiving use requires it; a release claim also retains its own decision or authority basis.
Is it the same EntityOfConcern with textual restatement only?	`A.6.3.CR Conservative Retextualization`.
Is it the same EntityOfConcern with representation scheme or reasoning medium changed?	`A.6.3.RT Representation-Scheme Transition`.
Is it deliberately reduced-use and useful only under narrower bounded use, `non-admissible downstream use`, and source-bearing reopen?	`A.6.3.CSC Controlled Semantic Coarsening`.
Is the primary issue explanation-facing rendering class on an existing MVPK face?	`E.17.EFP ExplanationFaithfulnessProfile`.
Is the primary issue one bounded comparative review unit over sources?	`E.17.ID.CR ComparativeReviewUnit`.
Did the EntityOfConcern, target, ontology frame, or claim or relation record named by value change?	`A.6.4`, `OntologicalReframing`, or the retargeting or reframing pattern named by value.
Is the publication-facing unit being used as bridge, substitution, equivalence, “same”, “equivalent”, “align”, or “map” wording, or cross-context comparison relation?	Use Part F and `A.6.9` to repair the wording. Use F.9 for the obtaining Bridge, bounded-use claim, optional `CL`, evidence and loss boundaries, and optional Card. Use F.9.1 only for a separate stance note about that claim. Comparison alone is not a Bridge, and a publication face is neither the Bridge nor the note.
Is the live question carrier, export, OCR, screen, front-end behavior, or work on carriers?	Use `A.7` to repair a conflated relation position; recover the exact carrier or front-end relation under its direct pattern, and use `A.15.1` for a dated Work claim.

Evidence-path boundary. An A.10 evidence/provenance path, including one that cites attestation, freshness, or a G.11 currentness result, carries only the claim named by value it instantiates. It does not approve or authorize work, pass a gate, perform work, supply release permission, or raise assurance or engineering-justification use unless the typed project-side FPF kind and reference named by value that carries that downstream claim is also instantiated, such as A.15.4, A.15, A.20, A.21, or B.3.

Gate-display boundary. A dashboard tile, status view, or release screen exposes a gate decision only when the exact GateDecisionResult is recoverable with its decision subject, bounded action, profile application, check-application references, decision, action consequence, scope, window, and recheck condition under A.21. Add evidence, currentness, replay, or audit references only when the applicable rule or receiving use requires them. Without the required result and basis, the display remains orientation or source-finding only; color, label, layout, or proximity establishes neither gate passage, release permission, nor performed Work.