| Suffix minting | A word ending in Role, Status, Graph, Map, or Record becomes ontology. | Recover the governed value or relation, subject pattern, and proposed use first. |
| Evidence-role revival | EvidenceRole becomes a system-role-kind name family. | Recover the evidence-use relation; name it only through its subject pattern. |
| Status-system-role fusion | ReadyReviewerRole or ApprovedRole names a local system-role kind plus state. | Separate the system-role kind from the assignment-state or status-use relation. |
| Row overuse | A public naming row justifies equivalence, system-role assignment, or structural inference. | Lower use to the F.17 AdmissibleUse or repair the row and any needed Bridge. |
| Alias with payload | An alias changes kind, scope, occurrence identity, use, or authority. | Treat it as a different decision; use F.5, F.13, and F.18. |
| Source prestige minting | A standard or framework term becomes the selected FPF name by prestige. | Keep it as source wording, evidence for a local sense, or an alias until the subject and naming use are recovered and a designation is selected. |
| Review label as context | PatternReview_2026 is used as context, Work, system-role assignment, evidence, or authority. | Recover the dated Work, plan or edition, decision-use claim, or naming ReferenceScheme needed by the assertion. |
| Decision identifier or record as decision | An identifier or filled record is treated as the decision occurrence or as creating its result. | Recover the occurrence through the decision or choice pattern, predicate, actual participants, applicability, and identity rule that establish it. If the occurrence cannot be established, give the applicable outcome under §4.5. Constitute a separate C.2.1 result episteme only when needed. |
| Naming-object cascade | One expression automatically gets a cell, NameCard, row, identifier, and publication. | Use an already justified treatment. When the choice is unsettled, compare alternatives under F.14 and create a further naming object only if its use warrants it. |
| U-kind comfort minting | A new U-kind is proposed because existing names feel awkward, and F.8 is asked to name or admit it. | Return blockOrLowerUse; recover the object through E.24.CD when needed, let E.24.UK settle admission, and reopen naming only for the object named by that stable result. |
| Policy identifier as magic word | An identifier is used without a separately resolvable specification, or its mint history is called accountable, cited, replayable, normative, or reusable across the local boundary without an occurrence basis. | Supply the specification for every identifier. For the stronger history claim, supply its direct occurrence basis or give the applicable §4.5 outcome. Ordinary local use requires the specification and local scope. |