C.2.LS:13 - Worked Examples and Composition Notes
C.2.LS:13.1 - Operator-facing early alert
A console alert note may be published with a language-state facet profile such as:
F = F2/F3because the note is structurally controlled but still lightweight;AE = AE2because candidate anchors are visible but not yet fully relation-shaped;CD = CD1because several routes remain live;LanguageStateAnchoringMode = AM.OperatorLoopbecause the note is directly anchored to operator intervention/work;RepresentationFactorBundle = {local, sparse, mixed-symbolic}because alert text and compact codes coexist.
This example shows why no one facet can replace the others. The note is not simply early; it is early in a specific, decomposable way.
C.2.LS:13.2 - Research cue before lexical repair
A felt or trace-anchored mismatch cue in an inquiry note may be:
- low
AE, - very low
CD, AM.EmbodiedFelt,- and representation-wise mixed because the cue is partly verbal, partly kinesthetic, partly exemplar-based.
That profile explains why the cue should remain in A.16.1 rather than being forced into A.6.P or B.5.2 immediately.
C.2.LS:13.3 - Architecture-description case
A viewpoint-bound note about the adequacy of an architecture description may be moderately high in F, moderately high in AE, still mid-level in CD, document-mediated in AM, and symbolic in its representation-factor bundle. The profile keeps description-side adequacy distinct from system-side engineering quality.
C.2.LS:13.4 - Same F, different profile
Two notes may share the same rough F band and still differ sharply in articulation, closure, anchoring, and representation factors. One may be operator-loop anchored and low-closure; another may be document-mediated and comparatively closed. The profile bundle keeps that difference visible instead of letting F behave like a master factor.