C.2.LS:4 - Solution

U.LanguageStateFacetProfile is a typed profile bundle that names the facets by which position claims in the declared language-state chart over U.CharacteristicSpace are published and interpreted:

• formalityRef -> U.Formality from C.2.3
• articulationExplicitnessRef -> U.ArticulationExplicitness from C.2.4
• languageStateClosureDegreeRef -> U.LanguageStateClosureDegree from C.2.5
• languageStateAnchoringModeRef -> U.LanguageStateAnchoringMode from C.2.6
• languageStateRepresentationFactorBundleRef -> U.LanguageStateRepresentationFactorBundle from C.2.7
• thresholdRefs? -> context-local threshold declarations over the named facets
• routeNotes? -> informative notes that help interpret routing or reopening decisions

C.2.LS therefore defines only the profile bundle; it defines neither an individual characteristic nor a trajectory. A.18/A.19 supply characteristic semantics, A.16 defines admissible moves, and E.18 governs an independently selected TransformationFlowStructure.

C.2.LS:4.0a - Kind and profile-bundle boundary

U.LanguageStateFacetProfile is a dependent durable profile-bundle value under the declared U.LanguageStateSpace and U.CharacteristicSpace boundary, not a root U-kind. Its identity is the explicit bundle of language-state facet refs used for position reading and threshold publication. A local dashboard, table, route note, or maturity label is a publication or interpretation over the bundle, not the bundle itself.

C.2.LS:4.1 - Contribution boundary

C.2.LS defines only profile composition and requires the language-state facets to remain explicit and non-collapsed. It does not:

• redefine F;
• invent a second formality progression;
• redefine the scale semantics of AE, CD, LanguageStateAnchoringMode, or U.LanguageStateRepresentationFactorBundle;
• define reopen/backoff moves;
• define endpoint classification or bridge kinds.

C.2.LS:4.2 - Threshold publication discipline

Any threshold used to choose a next question, constrain an admissible move, or begin A.6.P recovery shall be published on explicit named facets in the profile. Do not describe hidden sub-levels of F when the real issue is articulation, closure, anchoring, or the representation-factor bundle.

C.2.LS:4.2.a - Local profile-reading witness

For this pattern, a published facet profile is reviewable when:

• the facet refs are explicit or explicitly inherited from an already pinned upstream publication;
• any threshold-bearing use names the facet whose threshold is being invoked;
• route notes or local overlays remain informative and visibly docked to the explicit facet bundle;
• and the profile does not smuggle move rules, bridge rules, gate state, or downstream definitions and tests into the bundle record.

A polished label, one strong facet, or one memorable route note does not by itself yield an admissible profile reading. The profile remains conformant only when the named facets stay explicit and decomposable.

C.2.LS:4.3 - Composite readings

A language-state judgement may be composite, but the composite shall be decomposable. For example, a cue may be:

• low AE,
• medium CD,
• AM.TraceAnchored,
• and representation-wise mixed rather than purely symbolic.

A conforming profile makes this decomposition visible rather than hiding it under one poetic label such as “early” or “raw”.

C.2.LS:4.4 - Corridor map note

C.2.LS participates in the current Language-State & Semantic Routing Corridor, but contributes only the thin facet-profile bundle. Readers who need one map of the full language-state pattern set should read the corridor note in C.2.2a.

That map does not change this boundary: C.2.LS still does not define cue preservation, route-bearing publication, prompt entry, or downstream endpoint use.