B.4.1:4.1 - RoutedCueSet shape
A conforming routed cue set may publish:
sourceCuePackRefcandidateRouteSetrouteDecision?selectedRoute?routeRationale?routeSelectionStatus?multiRoutePolicy?publicationFaceRefs?articulationThresholdStatus?closureStatus?scope?GammaTime?
RoutedCueSet is not itself the late endpoint. articulationThresholdStatus and closureStatus report guard state only; their governance remains with C.2.4 and C.2.5, and route discrimination may additionally cite C.2.6 or C.2.7 when anchoring or representation-factor differences are load-bearing.
candidateRouteSet is the load-bearing core here. routeDecision, selectedRoute, routeRationale, and routeSelectionStatus belong here when route selection is explicit. They do not belong in PreArticulationCuePack. The status says only whether plurality remains open or a route has been selected; endpoint admission, publication availability, current use or retirement, and any actual authority relation remain separate claims under A.16 and their direct patterns. Use sourceCuePackRef when the originating early form is a cue pack; otherwise identify the equivalent early form and the stabilized cue it preserves.
publicationFaceRefs names MVPK faces only when face typing matters for publication or review. Faces are renderings of the routed cue set or of later typed projection publications; they are not the route-bearing form itself.
A multi-route RoutedCueSet is still one governed member. A lineage fork requires distinct successor epistemes or project records under their applicable identity and lineage rules. Use C.2.1 for episteme identity; publication availability remains separate under E.24.PUB.