C.2.LS - Language-State Facet Profile: Publish Readings and Use Conditions Together
Type: Definitional (D) Status: Stable Normativity: Normative unless marked informative
Plain-name. Language-state facet profile.
Technical alias. LanguageStateFacetProfile names the optional record form below. A filled profile is an assessment account governed by C.2.1.
Use this pattern when. Use C.2.LS when the next use of a published U.Episteme needs selected language-state readings to be interpreted, compared or reused together. Select the required formality, articulation, closure and representation readings, together with any source or use conditions needed to interpret or apply them.
Sufficient result and non-use. The profile can point to existing readings and include only the facets needed together. If ordinary wording, one direct facet reading or an applicable existing profile already serves the receiving use, use it without constructing another bundle.
What goes wrong if missed. Teams replace the facet profile with a maturity adjective such as ready, raw, or stable, then use that label to choose routes, decide whether to reopen, interpret Bridges, or make publication decisions. The label hides the facet values.
What this buys. A decomposable profile bundle: each facet keeps the definition and tests supplied by its own pattern, while the profile gives authors, assurance readers, and integrators one place to publish selected readings and the conditions on their joint use.
C.2.LS:1 - Problem frame
When several language-state readings are needed together, collect their references, assessment scopes, grounds and use conditions in one recoverable account. This makes their separate contributions to the receiving judgement inspectable. If that judgement needs a language-state chart position, its declared U.CharacteristicSpace supplies the basis.
C.2.LS:2 - Problem
When authors need several facet readings together, a vague maturity label can conceal their different contributions, or F can become their surrogate. That blocks admissible threshold publication, undercuts A.16 move guards, and makes school-to-school bridge work harder than it needs to be.
C.2.LS:3 - Forces
| Force | Tension |
|---|---|
| Thin profile bundle vs practical coordination | Keep the bundle small, but still give one stable place where the language-state facets are named together. |
| Reuse vs duplication | Reuse A.18/A.19 characteristic machinery and A.16 moves; use E.18 only for an independently selected TransformationFlowStructure. |
| Local thresholds vs cross-context comparability | Receiving uses can require different local thresholds; facet meanings must remain recoverable for comparison, bridge work and viewpoint bundles. |
C.2.LS:4 - Solution
A language-state facet profile records selected readings and use conditions about one identified episteme edition. Use C.2.2a:0 and :4.2–4.5 to select the needed facets, obtain readings and grounds, and identify any conditions used by the receiving action. The profile brings those results together and can refer to existing readings or to the source and use account supplied by C.2.6. Each Characteristic reading retains its meaning, Scale, value, assessment scope and grounds. A source or use claim retains its predicate, participants and grounds. Use a declared language-state chart over U.CharacteristicSpace when the receiving use needs a position or an operation in that chart. The optional fields below can refer to the readings and accounts that supply these contributions:
formalityRef-> the expression-property assessment governed byC.2.3, including its selected basis and any justified local ordered summaryarticulationExplicitnessRef-> the articulation reading governed byC.2.4languageStateClosureDegreeRef-> the closure reading governed byC.2.5languageStateAnchoringModeRef-> the source, evidence, access or action-condition claims selected underC.2.6; cite their account or an explicitly defined local summary with its criterionlanguageStateRepresentationFactorBundleRef-> the selected representation-factor readings governed byC.2.7thresholdRefs?-> context-local threshold declarations over the named facetsrouteNotes?-> 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 formality assessment or representation-factor bundle can contain several Characteristics. If placed in a CharacteristicSpace, each of those Characteristics receives its own declared Scale and slot; the reference to the assessment is not itself a Coordinate. The C.2.6 account is likewise separate from those slots; a local summary needs its own declared Characteristic and Scale before it can supply a Coordinate. 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
The optional LanguageStateFacetProfile form expresses an ordinary C.2.1 assessment account. The episteme edition being assessed is its EntityOfConcern. Its claims give the selected readings and their grounds within the assessment scope, using a declared chart when the receiving use needs one, together with any required source or use conditions and any thresholds used in the assessment. C.2.1 governs the account’s identity; E.24.PUB governs its expression and publication. No additional profile individual or dependent U-kind is needed for this use.
Distinguish the selection of facets from the filled assessment. A selection identifies the Characteristics and Scales needed by the receiving use and any separate C.2.6 questions. If a chart is needed, bind those Characteristics and Scales in its A.19 basis. The same selection can be used for several assessments, just as the same record form can express them.
A filled assessment states readings about its identified episteme edition and scope; changing a reading or a stated relation changes that claim content even if every definition reference stays the same.
An A.19 CharacteristicSpacePredicate has its own by-value identity under A.19:5.1.8. Reusing readings with a different predicate requires a new evaluation of that predicate, while the readings can remain unchanged.
For reuse, recover the assessed edition, facet meanings, any chart basis needed by the use, scope, readings and relied-on grounds from the profile or its applicable cited source. Recover a threshold or a separate source or action condition and its receiving use when the conclusion relies on it. Saying which of the selection, readings, threshold or whole assessment is being reused prevents an unchanged label from concealing changed content. Rearranging the same claims in a dashboard or table leaves their meanings available under the same account-identity rule.
Choose direct readings or a shared profile.
Use direct facet readings when they already provide the inputs for the receiving judgement. A shared profile is useful when several readings and their conditions must be interpreted, compared or reused together: recover their joint scope and how each contributes to that judgement.
When readings concern different expressions or components, keep that distinction visible. Identify which readings or relation claims each receiving condition uses, including any local threshold, and report that condition as met, not met or unresolved as its grounds warrant. This saves reassembling dispersed references. The profile adds no stronger warrant to the readings. Keep it partial when the task needs only part of the facet family, and reuse an existing applicable assessment rather than writing another.
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 universal formality progression or an undeclared local summary;
- redefine the scale semantics of
AE,CDor the representation factors inC.2.7, or replace the direct predicates recovered through C.2.6; - define reopen/backoff moves;
- define endpoint classification or bridge kinds.
C.2.LS:4.2 - Threshold publication discipline
When the receiving use relies on a threshold, make its condition and input readings recoverable from the profile or an applicable cited source. Do not describe hidden sub-levels of F when the issue is articulation, closure, a source or use condition, or the representation-factor bundle. Test a required relation under its direct predicate. An A.19 CharacteristicSpacePredicate retains its declared space, Characteristic and Scale bindings, domain and test under A.19:5.1.8; only declared Characteristic readings supply its slot values.
C.2.LS:4.2.a - Local profile-reading witness
For this pattern, a published facet profile is reviewable when:
- the assessed episteme edition, any chart used, scope, selected refs, readings and any relied-on source or use claims are explicit or recoverable from a cited applicable upstream publication;
- any threshold-bearing use identifies the threshold and the readings it consumes;
- route notes or local overlays remain informative and visibly docked to the explicit facet bundle;
- and any claimed move, Bridge, gate state or downstream result retains its own governing definition and test.
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
For a diagnostic note, ask what the wording lets a reader identify and which explanations the observations still permit. A note can name two sensors, their readings and the time window precisely while leaving both a calibration fault and a sampling delay open. Cite the trace from which the readings were derived. If the decision also depends on how the sensor encodes them, inspect that encoding. A table listing the two readings can supply the user with symbolic labels while leaving the internal code unknown.
C.2.LS:4.4 - Corridor map note
For a map of the related language-state patterns, see C.2.2a:15.
C.2.LS:5 - Archetypal Grounding
A team may say a draft is “still forming” for different reasons. The profile lets the team identify whether the issue is low articulation, low candidate-space closure, an unavailable observation or use condition, or an unresolved representation-factor bundle.
Operator alert. An operator alert note can have stable alert terms and structure and low closure, while participating in an operator acknowledgement-and-check procedure.
Inquiry note. A station note records the service identifier, date and actual arrival time for each of three trains at the same station. The reader can identify all three events. To compare their delays, obtain each scheduled arrival from the applicable timetable and compare it with the matching actual arrival on the same time basis.
C.2.LS:6 - Bias-Annotation
Making selected facet readings explicit costs more than using one stage adjective. It makes their contribution to the receiving judgement inspectable, including any threshold that judgement uses; retain the ordinary wording or existing reading when that already serves the use.
C.2.LS:7 - Conformance Checklist
CC-C.2.LS-1A language-state facet profile SHALL reference the patterns that define its facets rather than invent local unnamed factors.CC-C.2.LS-2C.2.LSMUST NOT redefine the C.2.3 assessment or conceal several expression properties in one undeclared rank.CC-C.2.LS-3A threshold relied on for routing, reopening, or lexical repair SHALL be stated or cited with the readings it consumes. Required relation conditions retain their direct predicates.CC-C.2.LS-4Trajectory accounts that rely on facet profiles SHOULD reuse A.16 move kinds. Apply E.18 only to an independently selected TransformationFlowStructure; use E.18.2 when its mathematical description is needed.CC-C.2.LS-5Composite labels such asearly,settled, orreadySHALL NOT stand in for the explicit facet bundle when those states matter operationally.CC-C.2.LS-6Composite readings, overlays, and route notes SHALL remain decomposable into named facets and MUST NOT behave as hidden master factors.CC-C.2.LS-7Profile references or notes MUST NOT replace the governing move, Bridge, gate or downstream rule. Cite the applicable rule when a proposed consequence depends on it.
C.2.LS:8 - Common Anti-Patterns and How to Avoid Them
- Shadow progression. Treating
early/lateas a master scale. Split the judgement into the named facets. - Formality capture. Letting
Fstand in for closure or articulation. Publish those facets explicitly. - Bundle inflation. Turning the profile into a second
A.19. Keep it thin and referential. - Opaque readiness. Using words such as
readyormaturewithout naming which facet justifies the claim. - Route-note capture. Letting an informative route note act as a move rule, gate state, or endpoint rule. Keep route notes informative. Use
A.16for admissible moves, the applicable pattern for a downstream definition or test, the applicable gate or Work pattern for those claims, and anauthoritySourceRefonly when an external authority supplies the rule.
C.2.LS:9 - Consequences
The benefit is clearer source and rule references: early cue work, bridge annotations, and reopen moves can all refer to one explicit facet profile. The trade-off is making the selected readings and their use conditions recoverable, including any threshold used.
C.2.LS:10 - Rationale
The profile brings together the references needed to interpret facet readings together and test any local threshold used by the receiving judgement. Each referenced pattern supplies the corresponding definition and test; the profile preserves their different contributions to the receiving judgement.
C.2.LS:11 - SoTA-Echoing
Source boundary. The facet meanings and profile rules come from A.18/A.19 and the neighboring FPF patterns. The external comparisons below contribute scoped conditions and publication distinctions.
| Claim need | Bounded comparison | Exact source | Use in C.2.LS | Disposition |
|---|---|---|---|---|
| Conditions are selected for the receiving use. | AI RMF profiles are tailored to application requirements, risk tolerance and resources; the framework prescribes neither a universal tolerance nor a profile template. | NIST AI RMF 1.0 (2023), §1.2.2 and §6 | Select needed language-state readings and make any relied-on threshold explicit. | Adapt. |
| A publication can keep several named description elements visible without making their container identical to those elements. | Architecture-description vocabulary distinguishes named elements and their correspondence in a published description. | ISO/IEC/IEEE 42010:2022, §§3.4 and 3.11 | Use this only as a narrow publication comparator; it does not establish the language-state facet ontology. | Narrow comparator only. |
Local stance. The useful result is a decomposable profile of the readings and conditions needed for the receiving use.
C.2.LS:12 - Relations
- Builds on:
A.18,A.19,C.2.1,C.2.2a,C.2.3,E.24.PUB. - Coordinates with:
C.2.4,C.2.5,C.2.6,C.2.7,A.16.0,A.16,A.16.1,A.16.2,B.4.1,B.5.2.0,E.18,F.9for any Bridge and bounded-use claim, andF.9.1only for an optional stance note about that claim. - Constrains: language-state threshold publication and profile composition.
C.2.LS:13 - Worked Examples and Composition Notes
C.2.LS:13.1 - Operator-facing early alert
In this constructed case, the console publishes Pump-alert-21 for an operator comparing diagnostic alternatives before selecting a check:
At sample t21, Pump P7 indicates 70 kPa, below its alarm threshold of 90 kPa:
p_indicated(P7,t21) < 90 kPa. Which of sensor bias, low supply, or an open bypass explains this indication? Keep these three alternatives live until an observation distinguishes them.
For this comparison, the three candidates have these stated implications:
| Candidate | Distinguishing implication in this case |
|---|---|
| Sensor bias | An accepted independent reference gauge would read at least 90 kPa despite the indicated 70 kPa. |
| Low supply | The reference gauge would read below 90 kPa and the upstream pressure below 80 kPa. |
| Open bypass | The reference gauge would read below 90 kPa and the bypass would be open. |
Initially no reference-gauge reading, upstream-pressure reading, or bypass-state observation is available. The alert makes the contrasts explicit without excluding a candidate or selecting a diagnostic route. Its receiving use is comparison within this stated candidate field. The console connects the alert to the operator’s acknowledgement and selection of the next diagnostic check.
The alert’s code component uses eight indicator units in this order: NORMAL, LOW_PRESSURE, HIGH_PRESSURE, LOW_FLOW, HIGH_TEMPERATURE, VIBRATION, SENSOR_FAULT, LINK_LOSS. Exactly one unit is active at a time. The fixed decoder assigns the active unit its corresponding report label; LOW_PRESSURE denotes the alarm predicate above. Thus [0,1,0,0,0,0,0,0] denotes this low-pressure alert. For this code comparison, the local criterion calls an active-unit fraction at most 1/4 sparse and a greater fraction dense.
The profile states:
- its formality assessment covers the displayed alert condition and question: the pressure variables and units are defined, the threshold predicate is explicit, and the question and diagnostic contrasts are expressed in prose;
AE = AE4for the initial diagnostic question, because its subject, indicated condition, alternatives, contrasting implications, and bounded receiving use give a complete branch-appropriate expression (C.2.4:4.2);CD = CD1, because the contrasts weakly stabilize the stated candidate field while all three alternatives remain live and no route is selected (C.2.5:4.2);- the C.2.6 account states that the console connects the alert to the operator’s acknowledgement and diagnostic-check selection; this action condition is separate from the chart readings;
RepresentationFactorBundle = {local, sparse, symbolic}for the indicator-code component: one unit identifies the report, the active fraction1/8satisfies the stated local criterion, and the named units have an explicit decoding rule (C.2.7:4.1). These readings concern the code; assess the surrounding prose separately if its representation factors matter.
Changed condition. Suppose an accepted reference-gauge reading for the same sample t21 becomes available: 72 kPa. Under the stated case implications it excludes sensor bias, while low supply and an open bypass remain live. The meaningful reduction from three candidates to two supports CD2; it selects neither remaining route. The updated diagnostic question still has its complete expression, and the pressure vocabulary, alarm predicate, indicator code, and operator-loop connection are unchanged. Apply the receiving pattern’s own conditions when choosing the next question, check, or endpoint use.
The alert has a complete question and still-open diagnostic alternatives. Its code factors and operator-loop connection answer different questions; no one facet replaces the others.
C.2.LS:13.2 - Research cue before lexical repair
An observer reports a vibration just after startup. The note identifies the machine, the observer and the occasion. It leaves open what changed and which part vibrated. The next investigator can locate the observation and seek a comparison or a trace. If a later summary proposes a cause, identify which evidence supports that claim. A.16.1 can preserve the initial cue. Use A.6.P for an unclear relation or B.5.2 when the material supplies the conditions for an abductive prompt.
C.2.LS:13.3 - Architecture-description case
A note evaluates whether a named edition of an architecture description assigns a responder to each failure mode. For one mode the description names two possible responders and gives no rule for choosing between them. The note can express this finding precisely. The assignment remains open in the description. To determine who responded in service, inspect the record of that incident.
C.2.LS:13.4 - Same F, different profile
Two notes may supply the same required expression properties and still differ sharply in articulation, closure, source and use conditions, and representation factors. One may be used in an operator’s check procedure with diagnostic alternatives still open; another may assess a document’s assertions with comparatively closed alternatives. The profile bundle keeps that difference visible instead of letting F behave like a master factor.
C.2.LS:13.5 - Reuse the selection while readings or thresholds change
In :13.1, the facet definitions and record form remain available after the reference-gauge reading arrives. The closure assessment changes from CD1 to CD2; retain the assessed alert edition and the new grounds in the updated assessment. This is reuse of the facet selection with changed claim content, not reuse of the earlier closure reading.
Now consider two stipulated receiving rules for that same assessment. A diagnostic-comparison meeting requires an explicit question and contrasting alternatives; it can use the available AE4 reading. An action-selection rule additionally requires a selected diagnostic route. CD2 still leaves two alternatives live, so that rule’s condition is not met.
The same readings support these different conclusions because the receiving conditions differ. If both assessments publish their threshold conditions, their full contents differ; the common readings may be cited once. Neither rule changes what AE4 or CD2 means, and each applies only to the stated receiving use.
C.2.LS:14 - Authoring and Review Guidance
C.2.LS:14.1 - For authors
When publishing a language-state facet profile:
- start from the local authoring problem rather than from a memorized progression;
- name the facet refs;
- add threshold refs only when a threshold changes routing, repair, or another operative decision;
- when a label such as “mature”, “raw”, or “ready” carries an operational claim, make the relevant facet readings and conditions visible.
C.2.LS:14.2 - For assurance readers
Use :18.1 to check the profile’s meanings, relied-on conditions and claimed consequences.
C.2.LS:14.3 - For integrators
Integrators should preserve the profile references. A local alias is acceptable when the underlying facet references remain recoverable and unambiguous.
C.2.LS:15 - Extension and Migration Notes
C.2.LS:15.1 - Local extension rule
Contexts may extend the profile with local threshold refs, route notes, or additional descriptive aids, but they shall not add a new master facet that collapses the named facet set into one summary factor.
C.2.LS:15.2 - Migration from surrogate prose
When a stage label carries a claim used in routing, comparison or another decision, recover the readings and conditions it abbreviates. Examples include:
- “the episteme is still early”,
- “the issue is not mature enough”,
- “the note is ready”,
- “the cue is still raw”.
For that use, state the relevant readings or relation claims and their grounds, whether any relied-on threshold is met, and the governing rule for the resulting move. An ordinary description with no such operational claim needs no profile expansion.
C.2.LS:15.3 - Boundary reminder
Use the profile to refer to facet readings and applicable thresholds. Definitions and tests for moves, Bridges, Scales and bundles remain with their governing patterns.
C.2.LS:15.4 - Use a facet selection in an assessment
A record containing only references to facet definitions supplies a selection of Characteristics and any separate source or use questions to be answered. To use it for a position assessment, add or cite the required readings and relation claims, identify the episteme edition being assessed and state the assessment scope. Retain the definition references so the meaning of each reading remains recoverable.
C.2.LS:16 - Profile Publication Package Discipline
C.2.LS:16.1 - Minimal publishable profile package
A publishable LanguageStateFacetProfile carries what its receiving use needs:
- the selected refs from :4, with the relevant readings or relation claims, stated here or cited;
- any threshold refs that substantively affect routing, repair, bridge interpretation, or review load;
- the relation to
Fwhen readers might otherwise treatFas a surrogate; - any missing or unknown reading or unresolved source or use condition that could change the receiving judgement.
One-line publication is admissible only if the applicable facet definitions and tests, and the grounds of any relation claims, remain recoverable.
C.2.LS:16.2 - Partial-profile rule
A partial profile identifies its selected facets and any missing reading that could change the receiving judgement. Publishing AE and CD can suffice when a source or interaction condition is irrelevant to that use. When such a condition matters, state the relation and its grounds or the decision-relevant unknown under C.2.6:4.3. For an independently defined local Characteristic, use C.2.2a:4.2 for its reading and uncertainty.
One facet can be sufficient for the named use. Refer to other readings only when that use needs them; no note about irrelevant omissions is required.
C.2.LS:16.3 - Overlay discipline
Local overlays such as “explicit-but-open”, “derived from trace T”, or “requires operator acknowledgement” are admissible only when their meanings are recoverable from the readings or relation claims stated or cited in the profile. Overlays remain secondary to the declared profile and must not replace the facet bundle.
C.2.LS:17 - Cross-Facet Reading Rule
C.2.LS:17.1 - No master-facet reading
Do not infer the whole language-state profile from one facet. High AE does not entail high CD; an operator acknowledgement condition does not fix AE or CD; symbolic representation does not establish the expression properties needed by the receiving use; low CD does not imply low operational consequence.
C.2.LS:17.2 - Threshold interaction rule
For a threshold expressed over one facet, identify any other facet readings or relation conditions that also constrain the receiving use. A local rule may require sufficient AE for an explicit open explanatory question for B.5.2.0 and cap CD so rival explanations remain live. Another may require AE3+ and an open-interpretation CD condition for an exploratory A.6.P use of a relation that needs clarification. Apply these thresholds to the named semantic branch under the receiving pattern’s entry conditions. Any binding consequence retains its own governing rule and authority.
C.2.LS:17.3 - Transition reading rule
Read changes in the profile’s readings and source or use conditions separately. A note may become more explicit without becoming more closed. Replacing direct access to an observation with access to its written report can leave closure unchanged while changing which check the recipient can perform. A representation may become more symbolic without adding the expression properties needed by its receiving use. Use the applicable move rule to determine which current readings and source, use or route conditions must hold. State any changes to them that the transition makes.
C.2.LS:18 - Review Matrix and Migration Tests
C.2.LS:18.1 - Review matrix
An assurance reader should ask:
- does each published facet keep the definition and test supplied by its own pattern rather than by surrogate prose;
- does any overlay introduce a hidden scalar or gate decision;
- are threshold claims tied to the facet that bears them;
- do cited moves in
A.16,A.16.1,A.16.2,B.4.1, orB.5.2.0match the facet bundle; - if reuse depends on distinct local meanings, were their exact senses recovered and the F.9 predicate tested, preserving a false or unresolved result; if a Bridge obtains, does its separate bounded-use claim support the proposed reuse under F.9:4.2, with any optional loss account or F.9.1 stance note kept separate from the facets;
- if viewpoint conformance is claimed, was it tested under
E.17.0?
C.2.LS:18.2 - Migration test for source prose
When a receiving use depends on a source phrase such as “still immature” or “already stable enough”, recover the claimed reading or relation, its grounds, any threshold or route consequence, and the cited rule that warrants that consequence. Add an external authoritySourceRef only when an external authority supplies the rule.
C.2.LS:18.3 - Comparative profile use
Compare profiles on the named facets. A missing reading leaves that facet’s comparison unresolved. A reporting aggregate needs a declared local model and operations admissible for the Scales under A.18/A.19; publishing an aggregation rule alone does not establish that basis. The receiving rule determines whether the aggregate supplies a sufficient input. Keep component readings or an accessible return to them whenever that rule, interpretation or reliance needs their distinctions or grounds.