A.16.1:4 - Solution
PreArticulationCuePack is a typed publishable episteme form that serves as the earliest durable seam publication form inside the language-state cluster. It is not a claim, not a characteristic, not a method, not work, and not a route record. When rendered, it appears on an ordinary MVPK face; cue-pack status is a property of the publication form, not a rival face kind.
A cue pack may exist before any route is selected and even before route-candidate hints can yet be named clearly. When route plurality or selection becomes explicit enough to publish, use B.4.1 to state it and publish the next form as a RoutedCueSet.
A.16.1:4.0a - Publication form and filled account
PreArticulationCuePack names the publication form defined here; it is not an admitted U-kind. A filled claim-bearing preservation account is an episteme only when its claim content, exact EntityOfConcern and effective ReferenceScheme satisfy C.2.1. The form, that episteme, its cue and witnesses, its carrier and any E.24.PUB publication occurrence remain distinct.
A.16.1:4.1 - Core shape
A conforming cue pack may publish:
cueNucleuspreservationRationale?laneCandidates?routeCandidateHints?valenceProfile?languageStateClosureDegreeRef?languageStateFacetProfileRef?detector?primaryAnchor?candidateAnchors?primaryWitnessRef?witnessRefs?exemplars?contrasts?traceRefs?embodimentRefs?modelStateRefs?scope?GammaTime?
cueNucleus names the minimal preserved core: what exactly is being kept visible rather than lost in carrier noise or premature endpoint wording.
primaryWitnessRef and primaryAnchor provide explicit triage when one witness or anchor is load-bearing for preservation. Secondary witnesses, anchors, traces, embodiment refs, and model-state refs may enrich the pack without displacing that primary nucleus.
laneCandidates and routeCandidateHints are early directional hints only. They are not a selected route, route rationale, or route-selection status. Those belong to RoutedCueSet under B.4.1.
The referenced facets keep their own definitions. primaryAnchor, candidateAnchors, contrasts, and exemplars commonly provide anchor material for AE under C.2.4; languageStateClosureDegreeRef docks to C.2.5; anchoring and representation-factor refs dock to C.2.6 and C.2.7; languageStateFacetProfileRef may bundle them through C.2.LS.
In this cluster, a cue is a salient epistemic nucleus extracted from witnesses, traces, felt tensions, model outputs, work-possibility hints, reliance-possibility hints, contrasts, or other grounds and made preservable as a pack. A raw signal-like trace counts as a cue only when that salience and preservability have been made explicit; otherwise it remains a trace, not yet a cue. Any evidence use is separately qualified under A.10 for a named target claim.
A.16.1:4.2 - Use boundary
A cue pack may preserve:
- a cue nucleus,
- preservation rationale,
- primary and candidate anchors,
- primary and secondary witnesses,
- contrasts and exemplars,
- early directional plurality or route-candidate hints.
A cue pack shall not silently serve as:
- a route decision record,
- a selected-route publication,
- a finished anomaly statement,
- a finished evaluative ascription,
- a finished
A.6.Ainvitation, - a method step,
- a work occurrence.
A.16.1:4.3 - Transition discipline
A cue pack may admissibly feed:
B.4.1once route plurality or route selection deserves explicit publication;B.5.2.0to constitute and check a cue-derived abductive prompt;A.6.Pwhen a relation-bearing phrase needs its direct relation, participants, direction, or detail restored for a named receiving use;A.16.2when prior stabilization must be reopened, backed off, respecified, or retired.