| Card-to-kind jump | A useful card is promoted into a U.* kind because it has repeated fields. | Recover its claims, subject, form, and carrier; use C.2.1 or E.24.PUB as triggered. |
| Structural U-kind jump | A heading, title, filename, or ToC row keeps U.* because the spelling is convenient. | Recover the subject and use E.24.UK for the admission question; naming follows the result. |
| Column-to-participant jump | A field label is treated as a relation-participant meaning, or a filled field as an actual participant; either is called a SlotSpec because of column position. | Recover the direct predicate, its relation-participant meanings, and its actual participants first. Keep the field as a representation element or participant designation; under A.6.5, declare a SlotSpec only inside a needed RelationSignature for that already recovered relation. |
| One-word candidate | A broad word is renamed and treated as settled. | Recover the subject and predicate; use F.19 when only wording remains and E.10 for unresolved meanings. |
| Local-kind inflation | A useful project criterion is promoted to durable public ontology. | Use C.3.2 and keep the local kind, declaration, judgment, and extension distinct. |
| Registry trap | The author keeps a list of possible ontics without deciding the blocked case. | State the work, apply one truthful subject pattern or name one precise unresolved stop, and stop. |
| Scoring before identity | A score form is filled before the subject and direct relation gap are known. | Recover the subject, identity rule, dependent uses, and missing coordination; use A.19.ECS only for an actual comparison. |
| Repetition-as-admission | Several forms or patterns share a label, so an ontic is inferred. | Require the E.24 entry facts: one subject identity and minimal relation set reused by named dependent patterns. |
| Negative-catalogue repair | The text lists only what the candidate is not. | State the positive subject, claim, direct pattern, and next action. |