A.6.5:7 - Conformance Checklist
- The direct relation kind and the definition of its predicate, applicability, participant meanings, and occurrence-identity rule are named before SlotSpecs are declared.
- Every participant meaning needed by reusable typed use has one complete
<SlotKind, ValueKind, refMode>SlotSpec in theRelationSignature. - Each SlotKind is local to the one
RelationSignaturethat contains its SlotSpec. - World-side relation prose names participant meanings and actual participants. Declaration prose uses
SlotSpecfor the complete declaration and...Slotfor its declaration-local SlotKind. Receiving-episteme prose distinguishes a designation from its referent, using...Reffor the reference kind or value. For a field receiving relation semantics, apply the §4.2 declaration or representation-correspondence rule. Position and place remain ordinary representation words unless a declaration establishes a SlotSpec. - Each ValueKind is exact enough for the direct predicate and does not combine participant kinds for which the predicate has different semantics.
- An assertion or description episteme that designates a participant by reference names the RefKind and resolves it to the declared ValueKind.
- The actual relation participant, its reference, reference resolution, SlotSpec declaration, participant designation in the assertion, and relation occurrence remain distinct.
- A C.3 kind is introduced only for a current typed-quantification, membership, substitution, or subkind use.
- A verb-shaped predicate is not used as evidence of work, method, transformation, agency, or holonhood.
- Only an admitted
U.Systemis admitted forHolderSystemSlot. Each species underU.SystemRoleAssignmentdeclares itsAssignedSystemRoleKindSlotdomain and any additional participant meaning whose value changes the predicate or occurrence identity. U.WorkandU.Methodrely on their own constructive holon tests, whileU.Transformationrelies onA.3.4’s actual-bounded-change identity; A.6.5 admits none of them by grammar.- The direct-relation definition supplies the obtaining predicate and occurrence-identity rule; current-case facts or constituting history supply the factual basis; a claim-bearing episteme records polarity; and evidence or reliance remains a separate judgement.
- A declaration, assertion, description, representation, or publication episteme does not create the world-side relation by form.
- Ordinary use can stop before signatures, explicit occurrence identity, or C.3 kind derivation when the receiving use depends on none of them; typed reuse, occurrence identity, and local-kind quantification are independent thresholds, and none is a prerequisite for another.
- A relation fact, an episteme claim, and a locally derived kind are handled by the patterns that define those respective objects.
- A SlotSpec declares one direct-relation participant meaning inside one
RelationSignature. Method-description, operation, plan, work, evaluation, representation, card, schema, and record fields retain the kinds and declaration rules supplied by their defining patterns; a field that receives relation semantics uses the applicable §4.2 route. - An A.15.3 planned-filling row may cite a SlotSpec, but the planned designation remains plan content and establishes neither an actual participant nor relation obtaining.
- Interface, port, endpoint, API, and signature language remains available for recognition. The text states what connects, crosses, or is transferred between which entities and recovers the direct-relation definition before declaring SlotSpecs; an unresolved case requires A.6.RSIR or a missing-relation result.
- When result wording leaves continuation or inception unresolved, determine whether the same entity continued or a new entity began. Recover a separately asserted delivery, acceptance or evaluation relation from its predicate and participants; clear wording needs no additional history inquiry. A catalogue or generic result kind cannot supply a missing relation.