F.6:4.3 - Preserve the Exact Assignment Species

Before checking or relying on attribution, recover RA’s declared species and occurrence. This distinguishes the assignment even when the final practitioner sentence omits its full declaration. Every species declares:

• a HolderSystemSlot whose ValueKind is U.System;
• a declaration-local AssignedSystemRoleKindSlot whose ValueKind is the exact local system-role-kind domain admitted for that species;
• every additional participant meaning and its ValueKind;
• the rule, applicability, and maximal uninterrupted occurrence identity.

An assignment occurrence supplies one participant value for each slot. In particular, it supplies one local system-role-kind value from the AssignedSystemRoleKindSlot domain; the value does not replace or narrow that declared domain.

A simple assignment may have only holder and kind. A project appointment may also have ReviewCommissionSlot. F.6 accepts both through the family ValueKind and holder projection while retaining the declared species and all participants that distinguish the assignment occurrence. Those participants and the assignment rule still do not establish that the Work was performed under the assignment; the case must establish that link separately. F.6 never creates a two-participant generic assignment beside the appointment.

Taxonomy, scheme, KindSignature, assertion, and assignmentInterval can interpret or describe RA without becoming participants by default. Verify temporal coverage from whether the assignment rule actually holds, not merely from a recorded interval.

Do not replace the species with one Context value. Recover what the source token denotes and use its direct pattern. It can denote a system or Work locus, claim scope, or selected BoundedModelUseStructure; those objects are neither interchangeable nor optional participants of generic assignment or attribution signatures.