Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-21 09:09:35 UTC · snapshot created 2026-11-21 09:15:17 UTC · last check 2026-11-21 10:00:10 UTC

C.2.2a - Language-State Chart over U.CharacteristicSpace

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain-name. Language-state chart.

Builds on. A.19, E.10, F.18.

Used by. C.2.LS, C.2.3, 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, F.9.1, A.6.P, C.16.Q, A.6.A.

Use this pattern when. Routing, comparison or publication needs a language-state position, a comparison on declared Characteristics and Scales, or an evaluation of a slot predicate. Recover the separate readings and conditions hidden by labels such as early, ready or settled.

First question. Which expression, articulation, closure or representation readings can change the next action, and which source or use conditions must be stated beside them?

What goes wrong if missed. Teams flatten the relevant Characteristics, source and use conditions, grounds for assessment and publication lane into one maturity adjective. A polished document can then look ready although the claim is still open, or a useful early cue can be rejected because it is not yet polished.

What this buys. A recoverable position claim that shows the distinctions needed by the next action while keeping the episteme publication separate from its grounds, publication form and carrier.

C.2.2a:0 - First useful chart

When a chart position is needed, make the following content recoverable; a row is one possible form:

  • the episteme publication being positioned;
  • only the facet values or supported sets of possible values relevant to the next action; use intervals where the Scale admits them and mark a decision-relevant unknown as unknown;
  • the grounds for those readings, with any source, evidence, access or action conditions on which the next use depends;
  • any local threshold used by the named next action and whether the readings meet it, fail it, or leave the result undecided;
  • publication form, face, or carrier only when that distinction changes interpretation, preservation, or the next action.

Filled example. Pump-alert-17 is the alerting episteme publication being positioned. Its affected asset and discrepant reading are visible, but the claim structure is not yet complete; rival diagnostic routes remain open; the alert enters the operator’s acknowledgement-and-check procedure; and its representation mixes text with telemetry. Formality is omitted because the present routing decision does not depend on it. The grounds are trace T-17 and operator note N-4. The local rule permits routing to the diagnostic-question seam once the affected asset and discrepant reading are explicit. Form, face, and carrier are omitted because none changes that decision.

Sufficient result and non-use. Use an ordinary account, a direct facet reading or an existing chart directly when it supplies the distinctions, grounds and conditions required by the receiving use. Where that use needs a chart position, comparison or predicate evaluation not yet supplied, declare or reuse the needed chart basis and state the missing readings or result.

Practical result. The position account helps the practitioner decide whether to continue, stop, or route the publication to the pattern that governs the next question; it does not itself authorize that action.

C.2.2a:1 - Problem frame

In engineering, inquiry, operator, and management practice, teams often need to say where a U.Episteme publication stands before it has reached an endpoint subject pattern. That publication may appear through several cue-bearing, route-bearing, or endpoint-bound publication forms. The chart claim remains about the U.Episteme publication rather than about a local alias or a carrier lane.

Reusable arrangements or notations for cue packs, routed cue sets, abductive prompts, typed route-bounded projection publications, partial normal forms, and endpoint records are publication forms. A completed cue or record can express the episteme being assessed; its arrangement does not determine its chart position. An MVPK face is a selected publication form under E.17; it remains separate from the episteme, publication occurrence and carrier under E.24.PUB.

By contrast, a service disturbance, a model-vs-observation discrepancy, a bodily tension, a telemetry trace, a model output, or a carrier document may trigger, witness, or carry that episteme, but none of those is itself a coordinate in the space.

Practitioners still have to determine the relevant readings, any threshold used, the publication form needed and the claims those readings support. Labels such as raw, early, settled, or ready can hide these separate values and decision conditions.

C.2.2a:2 - Problem

When relevant facets and use conditions remain implicit:

  1. teams collapse several facets into one maturity story;
  2. F is silently misused as a surrogate for articulation, closure, source and use conditions, and representation factors;
  3. thresholds are published as vague readiness statements instead of explicit facet conditions;
  4. source phenomena, epistemes, publication forms, publication faces, and carriers are conflated;
  5. bridge and endpoint work inherit under-described upstream states.

C.2.2a:3 - Forces

ForceTension
Multi-facet fidelity vs readable publicationThe chart must preserve several independent facets without becoming unreadable.
Stable basis vs local thresholdsBasis slots should stay stable across contexts, while thresholds remain context-local.
Position semantics vs publication semanticsA position claim is not identical to the source phenomenon, publication form, or carrier through which it is currently expressed.
Comparability vs non-collapseTeams need to compare positions, but not by flattening them into one pseudo-scale.
Bridge reuse vs local authorityCross-context work benefits from a stable upstream chart, yet each context keeps local threshold authority.

C.2.2a:4 - Solution

A language-state chart is a declared U.CharacteristicSpace whose basis slots use selected language-state Characteristics and Scales under A.19. A profile containing several Characteristics expands into their separate slots; it is not one atomic Coordinate.

C.2.2a:4.0a - Chart, position claims and publication

The space declaration identifies the chart and makes its basis, optional overlays and typing hooks recoverable under A.19. A position claim states facet readings about the selected published U.Episteme edition; the E.24.PUB publication occurrence remains separate. A score table or local route map can express the declaration and position claims. Its reusable form and carrier remain distinct from those contents.

Changing a slot’s Characteristic, Scale or position requires a changed space declaration under A.19. Revising a reading changes the position claim and can use the same space. Changing a threshold changes the predicate under A.19:5.1.8. Changing only the form or carrier of these unchanged contents changes neither the space, reading nor predicate.

C.2.2a:4.1 - Core use

Use the declared chart to answer five questions:

  • which basis slots define where the episteme stands;
  • what a position claim in that chart means;
  • which thresholds are locally declared over those slots;
  • what comparisons are admissible without cross-facet collapse;
  • and how the same position claim stays distinct from the publication form expressing it.

C.2.2a:4.2 - Position reading under A.19

A language-state position is a partial, slot-explicit coordinate claim in the declared language-state U.CharacteristicSpace.

ValueSet(Scale) in A.19 is the full Scale domain. Publish each selected slot’s reading as one value or as a supported set of remaining possible values within that domain. This set describes incomplete information about the slot’s value. Use an interval only where the Scale admits it; state a decision-relevant unknown separately when the available information does not determine the needed reading. For closure, {CD1, CD2} can report two remaining possible values while the assessment is incomplete. Separate source and use claims follow C.2.6:4.3: two unresolved possible sources differ from an established contribution by both.

position here abbreviates these slot-explicit A.19 coordinate claims.

C.2.2a:4.3 - Facet basis

The language-state chart is coordinated by explicit facet subject patterns rather than by an informal master progression. Select the Characteristics and Scales needed for the next action from:

  • C.2.3 for the selected expression properties in a formality assessment, or an explicitly justified local summary;
  • C.2.4 for articulation explicitness;
  • C.2.5 for language-state closure degree;
  • C.2.7 for the language-state representation-factor bundle.

The selected basis slots together define the chart under A.19. Each Characteristic has its own Scale and slot. In particular, neither a formality profile nor a representation-factor bundle is silently treated as one Coordinate. C.2.2a does not govern the internal meanings or Scale semantics of those Characteristics.

C.2.6 supplies the source, evidence, access and action-condition account needed beside the coordinates. That account contributes no slot by itself. A local summary contributes a slot only when its one aspect and Scale are defined under C.2.6:15.1 and A.18/A.19; changing that basis requires an explicit chart change.

C.2.2a:4.4 - Position, grounds and publication

Keep the positioned episteme publication separate from the grounds for its assessment and from its publication form and carrier:

  • positioned episteme publication - the U.Episteme publication whose current position is being claimed;
  • grounds / witnesses - disturbances, discrepancies, traces, model outputs, bodily tensions, exemplars, or contrasts that justify the current reading;
  • publication forms - arrangements or notations used for publications such as cue packs, prompts, typed projections, partial normal forms and endpoint records; an MVPK face is a selected publication form, identified when that distinction matters;
  • carriers - physical or digital media, such as a paper sheet, file or console display, that bear the selected form.

C.2.2a governs the coordinate reading of the position claim. Keep that claim distinct from its grounds, publication form and carrier. C.2.6 also distinguishes a reading’s derivation from evidence for its target claim and from the conditions under which someone uses it.

C.2.2a:4.5 - Position publication rule

A published position identifies the episteme publication, states the facet readings relevant to the present use, and gives their grounds. A decision-relevant unknown is stated as unknown; unrelated facets need not be filled merely to complete a form.

For a movement, routing, comparison or endpoint use, name the receiving action and any language-state threshold it uses. If that action also requires a source, evidence or interaction condition, state or cite its predicate beside the facet readings; the condition does not become a Coordinate by being included in the same account. Add publication form, MVPK face, carrier, or SCR/RSCR lane only when that distinction affects interpretation, preservation, distribution, or the next action.

The position is reviewable when the named or inherited episteme publication, relevant readings, grounds, and any relied-on threshold are recoverable, and when any form, face, or carrier mentioned remains distinct from the positioned episteme publication. A polished note or better carrier does not by itself prove a new chart position.

C.2.2a:4.6 - Non-substitution of F

The formality assessment supplies the selected expression Characteristics, each with its own basis slot. A justified local summary may occupy one slot; a multi-property profile does not. These readings describe only the expression properties selected under C.2.3.

A conforming account shall not infer:

  • closure from formality alone;
  • source or use relations from publication-face format alone;
  • representation factors from articulation alone;
  • or routing admissibility from a lone F statement.

Where operationally meaningful thresholds exist, they must be published on the relevant slots rather than being disguised as informal F sublevels.

C.2.2a:4.7 - Position versus publication form

Identify the expression or component whose properties supplied each reading, and the expression in which the assessor reports it. Reformatting the assessment table can preserve every reading about the earlier alert. Rewriting the alert can change its articulation even if the assessor uses the same table. Check the affected facet on the changed expression. The table can follow a reusable publication form, including an MVPK face, and its carrier can be identified under E.24.PUB. A subsequent publication has to satisfy the conditions of its receiving pattern.

C.2.2a:4.8 - Threshold publication discipline

If a threshold is used to justify a move or endpoint entry, that threshold shall be stated on explicit basis slots in the chart. Statements such as this is now ready, this has matured, or this is still too early are non-conformant when they substitute for undeclared slot conditions.

C.2.2a:4.9 - Comparison and bridge note

Positions may be compared directly only under one shared chart meaning and the applicable local comparison rule. When comparison or reuse depends on distinct local meanings, recover the two exact F.17 local senses and test the F.9 predicate. Cite a Bridge only when that predicate obtains. State the proposed bounded use and any reliance separately; a loss note is optional and belongs to that use, not to the fact that the contexts differ.

If no Bridge obtains, preserve both local positions. Name the comparison or translation relation needed by the receiving use, or return the applicable missing-governor result instead of inventing correspondence.

C.2.2a:4.10 - Use the recovered position

Use the position facts for the named receiving question. If the next action uses a local threshold, compare the relevant readings with it and state whether they meet it, fail it or leave the result undecided. Use the supported result to decide whether to keep the publication where it is, route it through a seam or prompt pattern, or open a facet or endpoint question. An unknown reading prevents only the action or conclusion that requires it. The receiving pattern governs the route, comparison or publication decision.

C.2.2a:5 - Archetypal Grounding

Tell. One note can be used in an operator’s acknowledgement procedure yet still have low closure. Another can report an architecture document’s assertions in symbolic form while its route choice remains open. Both notes have positions in one language-state chart, but not on one maturity progression.

Show (System). A service disturbance is a system-side phenomenon. The positioned U.Episteme publication is the alerting episteme published from that disturbance. In Pump-alert-21 (:13.2), its position combines declared observation terms and unit-bearing values, CD1, and local/sparse/symbolic readings for the defined indicator code. The account separately states the operator acknowledgement and diagnostic-check condition.

Show (Episteme). The research note in :13.1 names a discrepancy and two possible causes. Its reader can compare the causes but cannot yet attribute the discrepancy to either one. To assess the internal encoding of the readings, the reader would need evidence about the meters. The typography of the note supplies no such evidence.

C.2.2a:6 - Bias-Annotation

The pattern favors separate facet readings over one stage adjective when a decision depends on them. Ordinary descriptions remain sufficient under the non-use boundary in :0.

C.2.2a:7 - Conformance Checklist

  • CC-C.2.2a-1 The language-state chart SHALL be a declared U.CharacteristicSpace under A.19, not a disguised F progression.
  • CC-C.2.2a-2 Published positions SHALL cite explicit facet subject patterns when those positions matter for movement, routing, or endpoint entry.
  • CC-C.2.2a-3 Position claims SHALL use slot-explicit values, supported sets of remaining possible values, or intervals admitted by the slot’s Scale; uncertainty SHALL NOT be hidden inside stage words such as ready, early, or mature.
  • CC-C.2.2a-4 A position claim in the chart MUST NOT be conflated with the current ground, witness, publication form (including an MVPK face), or carrier.
  • CC-C.2.2a-5 Comparison or reuse that depends on distinct local meanings SHALL recover the two exact F.17 local senses and test the F.9 predicate. Cite a Bridge only when it obtains; keep the bounded-use claim, reliance, and any optional loss note separate. If it does not obtain, keep the local positions distinct and name the missing comparison or translation governor.
  • CC-C.2.2a-6 Corridor and navigation notes MUST NOT be read as relocation of facet, seam, bridge, or downstream subject-pattern semantics into the chart subject-pattern set.
  • CC-C.2.2a-7 If a position claim is used for routing, endpoint entry, or gate-adjacent reasoning, its relied-on threshold SHALL remain explicit or recoverable from the cited applicable upstream publication. The positioned episteme publication SHALL remain identifiable. Include form, MVPK face or carrier distinctions when they affect interpretation or the next action, as in :4.5.

C.2.2a:8 - Common Anti-Patterns and How to Avoid Them

  • Maturity monism. Replace the needed distinctions with one stage word. Publish the relevant slot values and state any required source or use condition separately.
  • Formality capture. Use F to stand in for articulation, closure, or source and use conditions. Repair by naming the facet subject pattern.
  • Carrier collapse. Treat a document, cue pack, or routed note as if it were the position itself. Repair by distinguishing the position claim, publication form (including an MVPK face) and carrier.
  • Threshold folklore. Hide a relied-on facet threshold behind a readiness label. Repair by making its slot conditions explicit or citing the applicable declaration.
  • Bridge by vibe. Similar stage language is treated as equivalence. Recover the two exact F.17 local senses and test F.9; cite a Bridge only when its predicate obtains. Otherwise keep both positions local and route the comparison or translation question.
  • Corridor inflation. Treat the navigation cluster or corridor map as if it were the subject-pattern set for all downstream semantics. Repair by naming the pattern that governs the current chart, seam, or downstream claim; identify any seam publication form separately.

C.2.2a:9 - Consequences

Practitioners can state the language-state readings of a U.Episteme and their grounds without hiding them inside one maturity adjective. Where the receiving use needs a chart position, the publication must make its relevant slots, grounds and any relied-on threshold recoverable.

C.2.2a:10 - Rationale

Language-state work needs one explicit statement of what this chart is before individual facet, move, and endpoint patterns start using it. Its declared basis and each facet’s rule let readers interpret a position and test any threshold used by the next action.

C.2.2a:11 - SoTA-Echoing

The external comparisons below concern publication distinctions and scoped profiles. The chart basis remains grounded in A.19 and its facet patterns.

Claim needPractice contributionPrimary sourceAlignment with C.2.2aAdoption status
Distinguish the represented subject from its description and chosen description conventions.The 2022 standard distinguishes architecture from an architecture description and specifies requirements for architecture-description frameworks, languages, viewpoints and model kinds.ISO/IEC/IEEE 42010:2022, official abstractThe analogous FPF question is which episteme a position claim concerns and how it is expressed. C.2.1, A.19 and E.24.PUB supply those distinctions here.Adapt, bounded comparison.
Select profile content for the named use.AI RMF 1.0 §6 describes use-case profiles based on requirements, risk tolerance and resources, and comparison of Current and Target Profiles. It leaves profile templates open.NIST AI RMF 1.0 (2023), §6This supplies a comparison for tailoring selected readings to the receiving use. FPF chart slots and any threshold predicate follow A.19 and the applicable facet rule.Adapt, bounded comparison.

FPF architecture-description use. Keep the position claim and the expression, selected form and carrier through which it is published distinguishable when their identity changes interpretation or use, under C.2.1, A.19 and E.24.PUB.

Characteristic-space and profile discipline. The multi-facet chart is grounded in FPF A.19 and the Characteristics defined in C.2.3–C.2.5 and C.2.7. The cited NIST profile method supplies the narrower comparison of tailoring an account to a specific use.

Local stance. When the receiving use needs a chart position, use A.19 with the selected facets, any threshold used, and the publication distinctions that affect that use. The ISO and NIST contributions above are bounded comparisons; A.19 and the facet patterns govern this chart.

C.2.2a:12 - Relations

C.2.2a:13 - Worked Examples

C.2.2a:13.1 - Inquiry cue before endpoint capture

An inquiry note says that two meters gave different readings under the same recorded operating conditions. It identifies the meters and their units. It names calibration drift and a sampling-time difference as possible causes, with no observation yet to distinguish them. A reader can recover a diagnostic question and two live explanations. The display uses names and numbers. If the comparison concerns the code inside either meter, its distribution across internal units is still unknown. Use the established readings for the diagnostic inquiry. Entry to a pattern that needs a specific relation or causal conclusion depends on that pattern’s own conditions.

C.2.2a:13.2 - Routed operator alert note

Use Pump-alert-21 from C.2.LS:13.1 to compare the three stated diagnostic alternatives before selecting a check. The alert names Pump P7, its indicated pressure of 70 kPa, the alarm condition p_indicated(P7,t21) < 90 kPa, and the contrasting implications of sensor bias, low supply, and an open bypass. Its chart readings and separate use condition are:

  • F: the pressure variables and units are defined, the alarm predicate is explicit, and the question and diagnostic contrasts are expressed in prose;
  • AE = AE4: the diagnostic question has the participants, conditions, and bounds needed for this comparison;
  • CD = CD1: the three alternatives have explicit contrasts, but none has yet been excluded and no diagnostic route has been selected;
  • use condition under C.2.6: the console connects the alert to the operator’s acknowledgement and diagnostic-check selection; this is stated beside the coordinates;
  • RepresentationFactorBundle = {local, sparse, symbolic} for the alert’s indicator-code component only: one of eight named units is active, the fixed decoder gives its report label, and the active fraction 1/8 meets the example’s local sparse criterion. C.2.LS:13.1 supplies the unit order, decoder, and criterion.

If an accepted reference-gauge reading of 72 kPa for the same sample t21 excludes sensor bias under the stated case rule while the other two alternatives remain, update CD to CD2. The question remains fully stated and the code, expression properties, and operator-loop connection are unchanged.

Keep the live responses explicit in the route-bearing seam publication. Before publishing an endpoint-subject-qualified work record or reliance record, test the applicable downstream pattern’s conditions; these chart readings do not decide that result.

C.2.2a:13.3 - Viewpoint-bound adequacy note

A review note asks whether the architecture description specifies who acknowledges a storage fault. The cited edition names two possible responders and leaves their assignment open. A reviewer can identify the unresolved choice and the evidence still needed. Before assigning a closure level, check whether either responder has been ruled out or chosen and what would allow that choice to be reopened. Compare the note with an observation report on the same chart only for facets assessed on the same basis. Keep the source of each assessment available.

C.2.2a:13.4 - Polished prose is not closure

A prose rewrite may look cleaner, more compact, or more manager-readable than the source cue and still remain low in closure or articulation explicitness. If the underlying slot values, uncertainty, and route plurality remain unchanged, then publication polish changes the rendering or carrier lane, not the chart position by itself.

C.2.2a:14 - Position Publication Package Discipline

An account of a chart position identifies the episteme publication, the decision-relevant facet readings or intervals, their grounds, and any local threshold used by the named next action. Add form, face, carrier, freshness, or inherited pins only when the receiving use relies on them.

Minimum self-check:

  1. Does the account name the positioned episteme publication rather than a ground, form, face, or carrier?
  2. Does it state every facet that can change the named next action and mark a relevant unknown as unknown?
  3. Are the grounds and any relied-on local threshold recoverable?
  4. Does the account supply the position facts needed by the receiving question and, if a local threshold is used, say whether the readings meet it, fail it or leave the result undecided, while the receiving pattern governs the action?
  5. If the use depends on distinct local meanings, was F.9 tested on the two exact local senses rather than inferred from similar wording?

C.2.2a:15 - Extended corridor map

After the first position account is understood, the wider Language-State & Semantic Routing Corridor can be read as a distributed overlay over C.2.2a, C.2.LS, C.2.4–C.2.7, A.16, A.16.0–A.16.2, B.4.1, and B.5.2.0.

A.16.1 / PreArticulationCuePack is the earliest durable seam publication form in that corridor. B.4.1 is the explicit route-bearing seam after cue preservation, and B.5.2.0 is typed prompt entry. C.16.Q, A.6.A, A.6.P, B.5.2, A.15, and C.25 are downstream subject patterns, not members of the language-state chart. The map explains navigation only; it relocates none of their semantics into C.2.2a.

C.2.2a:End

Referenced in the corpus

35 literal mentions in other sections. Read their context to establish the relation.