C.2.P.DR:0 - Use this when

Use this pattern when a declarative representation is about to guide action, reliance, gate, release, evidence, method, mechanism, work, or pattern-application claims by its shape alone.

First useful move. Recover the visible expression or artifact; exact current direct object or relation; any current representation or correspondence use; current source or publication relation; tempting stronger action claim; recovered subject pattern; retained use; blocked stronger action claim; and stop or reopen condition. Return the repaired wording and needed stop or subject-pattern return. Use a DeclarativeRepresentationRepair note only when the receiving use needs the repair to remain inspectable.

Quick example. A heat-flow graph in a reactor-cooling review can show preserved and lost flow relations. It does not authorize a valve change by graph shape. The repair keeps the graph path as graph structure, returns release or gate reliance to the gate, source, and evidence patterns, and blocks the hidden work-permission claim.

Use this pattern especially when:

• a graph path, PathSlice, flow valuation, transformation-flow structure line, or graph expression over such a structure is overread as a prescribed work route or workflow;
• an A.10 evidence path is overread as approval, permission, release, gate passage, or assurance;
• a query, access path, query plan, table, dashboard, schema, checklist predicate, or API description is overread as method, work plan, performed work, gate, permission, or proof;
• a publication face, source-chain relation, carrier file path, mathematical representation, method-description representation, or FPF pattern relation is overread as call, dispatch, invocation, send, receive, route, or pattern application;
• method-like wording hides whether the current claim concerns U.Method, U.MethodDescription, formal substrate, mathematical-lens use, U.Mechanism, U.WorkPlan, dated U.Work, evidence relation, source relation, or quote-only source wording.

What goes wrong if missed. The representation appears to do work it cannot do. A path “routes” a decision, a query “calls” a pattern, a dashboard “authorizes” release, a checklist predicate “runs” a process, an evidence path “permits” action, or a program-looking text becomes “the method” without recovering method semantics, method description, formal substrate, mechanism, work plan, work, evidence, or source-use relation.

What this buys. The working reader keeps a visible expression useful without making it magical or hiding its subject pattern. Graph paths and structures, evidence or provenance relations, queries and formal objects, publication faces, and pattern relations keep their own kinds. When a graph, file, tile, table, or face represents one of them, the exact representation or correspondence use is stated separately. For method-like wording, the reader identifies the direct object or relation, any represented object or claim, and the exact relation that gives the expression its current use before selecting method, method description, formal substrate, mechanism, plan, work, evidence, source, gate, or release guidance.

Not this pattern when.

• If the graph path, PathSlice, or flow valuation is already current as graph structure, use E.18 directly.
• If the evidence relation or provenance relation for a claim is already current, use A.10 directly.
• If the publication face or source-use relation is already current, use E.17, E.17.EFP, C.2.P, or the direct publication pattern.
• If the current claim concerns a semantic way of doing, use A.3.1; if it concerns the description of that way, use A.3.2.
• If the current claim concerns operation algebra, laws, admissibility predicates, transport, audit, or governing-definition assignment, use A.6.1 or E.20.
• If the current claim concerns planned work or dated work, use A.15.2 or A.15.1.
• If the word is only quoted source wording or ordinary navigation prose with no FPF-governed claim, keep it quote-only or ordinary.