| “The role contains the state graph.” | “The system-role-kind description carries claims about one exact local kind and may cite a separately governed SystemRoleAssignmentStateRelation; the graph is a representation only when that use is current.” |
| “The diagram is the architecture.” | “Recover the architecture-description episteme first; then classify the diagram as claim content, U.View, publication form borne by a carrier, or C.29 representation only under the rule for the named use.” |
| “MethodSpec draft.” | “MethodDescription draft; specification use is not admitted until checkable claims and the exact harness or validation relation are present. Name a viewpoint only when the relying describing use depends on it.” |
| “The PDF is the method.” | “The method-description episteme concerns the exact method; the PDF carrier bears a publication form that expresses a selected episteme edition.” |
| “Same label, same thing.” | “Identify each entity under its own identity rule. For epistemes compare ClaimGraph, EntityOfConcern and effective scheme. Use F.9 only when a receiving claim also needs a semantic relation between exact local senses with different interpretation bases; keep the bounded-use claim and reliance separate.” |
| “Evidence status is a role state.” | “The status claim concerns its exact epistemic or deontic subject; use SystemRoleAssignmentStateRelation only for one exact assignment and predicate, or the direct system-state relation for another runtime fact.” |
| “The source has the approval role.” | “State the exact source-use, evidence-use, assurance-use, gate-use, or publication-use relation. For a claimed Work use, name the exact premise, governed reference, decision-use relation, or A.6.1 operation-argument binding and its actual participants; otherwise return the exact missing-governor result. None is a work-facing role assignment by wording.” |
| “Fill the description context tuple.” | “Name the receiving use and the exact viewpoint it selects only when that selection changes what the receiver reads or checks; do not create a context tuple.” |
| “The dashboard approves deployment.” | “An exact publication occurrence may make the architecture-description edition available through a dashboard form borne by a carrier; an exact gate verdict or permission relation is separately required for approval.” |