A.6.RCD:4.7 - Separate recognition from assurance

Recognition branch for ordinary receiving use. Ask only:

1. What receiving claim or action is blocked?
2. Who or what are the exact participants, and under which meanings?
3. Does one current direct predicate already state the needed affirmative, negative, or exact rule-qualified modal claim?
4. If not, what smallest substrate-admitted compound claim answers it?
5. Which of the four dispositions lets the receiving use proceed now?

The ordinary branch can stop at a readable direct claim or one readable compound claim. It does not require a named substrate document, predicate-definition publication, new relation kind, signature, explicit occurrence, or designator when the receiving use consumes none of them.

Negative direct-claim case. A staffing check asks whether Robot_7 holds CellInspectorAssignment, a declared direct species of U.SystemRoleAssignment for InspectorSystemRole, in Cell_3 during Interval_T. The current A.2.1 participant meanings and the direct species predicate state the positive test over the actual holder system, cell, and interval; a taxonomy or scheme is not an assignment participant. If an applicable non-assignment criterion or complete assignment closure basis exists and the available facts satisfy it, one claim-bearing episteme states the negative result and disposition 1 closes the check; there is no obtaining assignment occurrence to individuate. If no current direct-species predicate, applicability condition, or needed occurrence rule exists, return missing-governor. If the governor exists and the available case basis is sufficient to apply the positive test but it fails, return factually unsupported; if a fact needed to decide the test is unavailable, return missing-information. Neither a failed positive test nor either blocker is a third assignment polarity.

Assurance branch for DPF and FPF authors. DPF and FPF authors use this branch whenever they author a compound claim, reusable predicate definition, or relation-kind admission candidate, including a durable local compound claim that stops at disposition 2. In addition, verify:

• exact base patterns, definitions, editions, and applicability;
• selected substrate and constructor semantics;
• positive case, discriminating failure case, and receiving-use replay;
• one truthful definition EntityOfConcern when reusable semantics are published;
• dependency and currentness conditions;
• direct occurrence-identity and recurrence rules for every admitted relation kind;
• representation correspondence without representation-to-world collapse;
• naming only after the exact definition episteme, kind, or occurrence is settled;
• evidence relations under A.10, assurance results under B.3, gate results under A.21, and decision results under C.11 or the pattern whose Solution answers the exact decision claim.

Passing the assurance branch does not make evidence constitutive of relation obtaining. It makes the derivation and admission decision replayable for the declared use.