A.16:4.6 - Keep coordination claims separate
Do not compress several claims into AuthorityState. A reusable language-state coordination readout is only a compact view of independently established facts, not a new U-kind or world-side state. Include only the fields needed by the reader:
| Claim | What to show |
|---|---|
| Route plurality or selection | live routes; selected route if any; selection reason; route-bearing publication |
| Endpoint admission or use disposition | named endpoint test, its result, and the exact stronger use admitted, narrowed, or blocked |
| Publication availability | exact episteme, form, bounded use, and EpistemePublicationRelation occurrence when current |
| Current use or retirement | exact cue, episteme, publication, or branch and the currentness, withdrawal, supersession, or retirement claim that applies |
| Actual relation change | only an independently established authority, responsibility, permission, or commitment relation with participants, object or action, scope, interval, and act; otherwise omit the optional claim or report the unresolved change; state that a relation is unchanged only when an applicable negative criterion or complete closure basis supports that claim |
Open route plurality is not a lineage fork. A multi-route state keeps several directions live inside one route-bearing publication. A lineage fork has separately identified successor members, their preserved and lost content, and any exact lineage relations that obtain.
EndpointAdmissionProfile may still be reused as a declarative decision profile for next-use docking. It combines the relevant C.2.2a position, C.2.LS facet readings, route condition from B.4.1, prompt readiness from B.5.2.0, and visible witness or grounding conditions. Apply it to judge only whether docking to the later question is admissible: relation-like content toward A.6.P, an open question and rival set toward B.5.2.0, evaluative content toward C.16.Q, ambiguous affordance-like wording toward A.6.A and then the recovered subject, viability or other quality-family content toward C.25 when quality-family decomposition is the question, and executable docking toward A.15. Apply the selected pattern’s own tests. A.6.A may return a sufficient claim, question or exact missing basis; that recovery establishes no common invitation relation. Tone, style or apparent explicitness supplies no subject result by itself. The admission result creates no authority, responsibility, permission, commitment, publication, gate, or Work state.