A.6.RCD:4.1 - Execute the demand-first method

1. Name the blocked use. State the exact claim, check, decision, or continuation that cannot proceed, and what answer would close it.
2. Recover participants and direct relations. Use A.6.P to name the actual participant referents under their relation-participant meanings and retrieve the smallest plausible base from the exact pattern content or declaration that defines each base predicate and its obtaining law. Similar tokens, shared field names, or adjacent graph edges are not a base.
3. Choose the least constructor admitted by the current substrate. State the constructor semantics and the base claim content it consumes. Do not infer an operator from punctuation or notation.
4. Replay three things. Test one positive case, one discriminating failure case, and the named receiving use. Keep hidden intermediates, polarity, scope, time, and base-definition editions visible when they change the result.
5. Select the lightest disposition. Choose exactly one of the four dispositions in section 4.3 and stop at its stopping rule.
6. Open reusable semantics only when repeated use needs the same rule. First decide whether every reuse concerns one exact subject or the parameterized rule is reused across several subject instances. For one subject, identify a subject-bounded compound-law episteme whose exact EntityOfConcern is that subject and state the reuse limit. For a rule reused across subject instances, identify the exact reusable predicate definition as EntityOfConcern; that episteme may satisfy A.6.0 U.Signature membership before any relation kind is admitted, but it is not a RelationSignature.
7. Open kind admission only when occurrence semantics are consumed. A derived kind needs a direct subject settlement with obtaining, applicability, base dependencies, and a non-optional occurrence-identity rule. A primitive candidate additionally carries the failed derivation, the exact action-facing distinction lost, its own obtaining and recurrence laws, independent receiving uses, and a standalone subject-pattern obligation.

Use this compact working note only while the decision is live:

A.6.RCD working note:
  blockedReceivingUse:
  participantMeanings:
  candidateBaseRelationClaims:
  selectedSubstrateAndEdition:
  constructorSemantics:
  positiveCase:
  discriminatingFailureCase:
  receivingUseReplay:
  disposition:
  predicateDefinitionModeIfCurrent: subjectBounded | reusableAcrossSubjects
  predicateDefinitionEntityOfConcernIfCurrent:
  subjectBoundReuseBoundaryIfCurrent:
  directSubjectSettlementIfKindCurrent:
  stopOrReturn:

The note is a pattern-local prompt. A filled, claim-bearing use is an episteme under C.2.1; the printed shape is not a new record kind, RelationSignature, relation kind, or relation occurrence.