B.4.1:4 - Solution

Use this seam to make the candidate continuations and any selected route explicit after cue stabilization. The pre-abductive route-bearing seam sits inside the language-state cluster, between observation/cue preservation and endpoint subject-pattern entries:

Observe -> Notice -> Stabilize -> Route

Publish the route package as a RoutedCueSet, normally downstream of PreArticulationCuePack.

A robust route package should identify:

• the originating cue pack, if any, or the equivalent early form preserving the stabilized cue,
• the candidate route set,
• the route decision state,
• the selected route, if any,
• the grounds for each live route,
• the conditions that would change route ranking,
• and any typed downstream publication already published.

This keeps later handoff reviewable while leaving downstream claims and results under their applicable subject patterns.

For specialization-sensitive routes, the package should also make explicit the declared task family or utility target, the current budget window, the missing discriminator still needed, and the downstream subject pattern that would become applicable if that discriminator and that pattern’s other entry conditions are satisfied.

B.4.1:4.1 - RoutedCueSet shape

A conforming routed cue set may publish:

• sourceCuePackRef
• candidateRouteSet
• routeDecision?
• 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.

B.4.1:4.2 - Starter route family and conditional extension species

The candidate route set may contain, among others:

• starter canonical routes:
  • EvaluativeRoute
  • ActionInvitationRoute
  • ProblemAbductionRoute
  • MethodWorkRoute
  • RequirementCommitmentRoute
• conditional extension routes for bounded specialization or corridor discovery:
  • TaskFamilySpecializationRoute
  • AdaptationProbeRoute
  • NonHumanUtilityRoute
  • SubstrateDiversificationRoute

B.4.1:4.2.1 - Specialization-sensitive extension route family

These four routes are not part of the starter canonical core. Use them only when the cue already carries explicit bounded-specialization pressure, corridor-entry pressure, or substrate-fit doubt that subject patterns must be able to recover by value.

Use TaskFamilySpecializationRoute when the cue points toward acquiring one narrower higher-fit specialist lane for one declared task family under budget, where that lane may later resolve into one specialist method, portfolio, or competence bundle. Use AdaptationProbeRoute when the honest next question is whether threshold-reaching specialization is actually attainable under the current budget. Use NonHumanUtilityRoute when the cue suggests a promising utility target outside the current human-default solution corridor but still tied to one declared task family or utility target. Use SubstrateDiversificationRoute when the cue says the current method substrate may be too narrow and a broader or different substrate should be tested before commitment.

Contexts may refine the route family locally, but they shall keep the distinction between early route publication and endpoint governance.

B.4.1:4.3 - Projection discipline

Here projection names route-bounded partialization. The resulting content must be published in a typed publication form, rendered, when needed, on an existing MVPK face. The applicable subject pattern governs the downstream claim.

A routed cue set may support these continuations:

• publish U.AbductivePrompt under B.5.2.0,
• apply A.6.P, A.6.A, or C.16.Q under its own entry conditions and produce the sentence, record, or other result that the selected pattern calls for,
• or publish another explicitly typed upstream projection.

For a proposed downstream projection, if no typed publication form can yet be named honestly, keep the content in RoutedCueSet; an MVPK face alone supplies no such form.