E.10:0.2c.17 - Coordination and FPF-governed lists
Apply F.19 first: ask whether the receiving use needs a series at all. If one governing claim, relation, or representative case would do, write it and remove the catalogue. A broader umbrella head is not a repair.
When a series is needed and its FPF meaning remains unresolved, distinguish the current use:
- a closed set, with its classified kind, membership rule, and closure;
- illustrative examples, with the proposition or kind first and a non-exhaustive cue when completeness is plausibly ambiguous;
- explicit alternatives or a sequence;
- several obtaining direct relations, each with its actual participants;
- a reusable relation declaration, with its
RelationSignatureand A.6.5SlotSpecvalues; or - a C.29 representation, with its elements, represented objects, and correspondences.
If it declares reusable relation shapes, name each RelationSignature and A.6.5 SlotSpec value and do not infer that any relation obtains. If it is a C.29 tuple representation, name the representation elements, represented objects, and explicit correspondences; if the same material is also a reusable relation declaration, name its RelationSignature and A.6.5 SlotSpec values separately.
If none fits, leave the ontology or architecture question blocking instead of making the list itself a new kind. Even when one case fits, keep only members whose distinction changes the receiving use.