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

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:20:20 UTC

G.12 — DHC Dashboards (Discipline-Health Time Series and Views)

Status: Stable

G.12:0 — Use This When

Use G.12 when a team needs several recorded C.21 coordinate results arranged across windows, a dashboard view over them, or refresh wiring for that view.

Start from the C.21 results. State the discipline, intended use, ClaimScope, coordinate-result refs, and windows before choosing a layout. A local view is sufficient when there is no audience publication or refresh use.

Do not use G.12 for one ordinary field-health claim, to manufacture measurements from rows, to turn a dashboard into evidence or authority, or to require publication and telemetry for every C.21 use.

G.12:1 — Intent

Produce a reproducible discipline-health series and view while keeping these objects separate:

  1. C.16 measurement results and their C.2.1 coordinate-result epistemes;
  2. one optional C.2.1 DHCSeries episteme that orders the coordinate-result refs by window;
  3. rows and slices that represent those results or series;
  4. any E.24.PUB publication occurrence, form, carrier, audience, and availability interval; and
  5. any measurement, series-assembly, rendering, upload, or refresh Work.

G.12:2 — Problem Frame

Dashboards drift or become misleading when they:

  • treat ClaimScope and a selected TargetSlice as one field;
  • copy a value without its C.21 replay basis;
  • average nominal or ordinal values or mix Units;
  • hide normalization, distance, comparison, or target-band rules;
  • require a Bridge for every source difference or omit F.9 when distinct local senses are related;
  • turn a row, screenshot, UTS name, form, or carrier into the measurement or series episteme;
  • turn selected sets or archives into one scalar winner; or
  • rebuild everything because changed definition and evidence pins cannot be localized.

G.12:3 — Forces

ForceTension
Readable view vs replayA useful dashboard should be easy to read, while every relied-on coordinate must return to its exact definition and result.
Stable history vs changed definitionsA new method or Scale edition may invalidate trend comparability without changing historical results.
Optional publication vs local useA local view may be enough; audience availability adds a separate publication relation.
Selective refresh vs process burdenRefresh needs pins that identify the changed basis and the affected results, but a one-off view needs no telemetry framework.
Set-valued results vs headline pressureA view can summarize without manufacturing a scalar winner.

G.12:4 — Solution

G.12:4.0 — G.Core linkage

This pattern consumes G.Core obligations only for the branches opened.

GCoreLinkageManifest (G.12)

  • CoreConformanceProfileIds := {GCoreConformanceProfileId.PartG.AuthoringBase, GCoreConformanceProfileId.PartG.TriStateGuard, GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted, GCoreConformanceProfileId.PartG.ShippingBoundary}.
  • RSCRTriggerSetIds := {GCoreTriggerSetId.BridgeCalibrationKit} only when crossing or refresh wiring is used.
  • RSCRTriggerKindIds := {RSCRTriggerKindId.LegalitySurfaceEdit} only when a persisted series or view depends on that surface. Optional panels add only their own declared trigger kinds.
  • DefaultsConsumed := ∅; portfolio defaults become current only through G.12:Ext.PortfolioTelemetry.
  • CorePinSetIds := {GCorePinSetId.PartG.AuthoringMinimal, GCorePinSetId.PartG.CrossingVisibilityPins} with nil-elision.

The minimal durable series basis is DHCSeriesRef.edition, DisciplineRef, IntendedUse, ClaimScopeRef, exact coordinate-result refs, and their windows. Each coordinate resolves the complete DHCReplayBasis from C.21. PathSliceId[], crossing pins, public-name rows, shipping pins, publication refs, and telemetry pins are conditional.

G.12:4.1 — Objects

Local nameExact objectBoundary
DHCCoordinateResultRefRef to one persisted C.21/C.16 coordinate-result episteme and its active C.21 replay basis.It is not a row, series, evidence path, or acceptance decision.
DHCSeriesOne C.2.1 episteme whose EntityOfConcern is the discipline and whose ClaimGraph orders coordinate-result refs by their stated windows under one intended use, ClaimScope, and comparison basis.It is not a public U-kind, publication occurrence, dashboard, carrier, or Work.
DHCRowOne representation element showing the reference to the coordinate result and selected readable fields.It does not compute, establish, or replace the result.
DashboardSliceA dashboard representation or grouping over references to the rows, results or series. Use C.29 when an unresolved mathematical representation or transfer question matters to the dashboard use.It adds no comparison, normalization, acceptance, or selection semantics.
DHCTelemetryPinA G.11-facing refresh payload with a canonical trigger, exact affected scope, and changed definition, window, evidence, or policy pins.It is not evidence, currentness, an edition relation, or refresh Work.
dashboard publicationAn E.24.PUB occurrence for one exact selected episteme edition expressed by the dashboard form, with its audience, bounded use, carrier, and availability interval. The selected edition may be a series, a coordinate result, or a view independently constituted as a C.2.1 episteme.A view element, UTS row, rendering, upload, or release label does not supply episteme identity or make publication obtain.

Conceptual forms:

DHCSeries := <
  DHCSeriesRef.edition,
  DisciplineRef,
  IntendedUse,
  ClaimScopeRef,
  ComparisonBasis,
  CoordinateResultRefs[],
  WindowOrder,
  DHCDefinitionSetRef.edition?,
  TargetSliceRef?,
  CurrentnessRuleRef?
>

DHCRow := <
  RowId,
  DHCCoordinateResultRef,
  Window,
  DisplayedValue,
  DisplayedScaleOrUnit,
  DisplayedStance?,
  DisplayAnnotations?
>

DashboardSlice := <
  DashboardSliceId,
  DHCSeriesRef.edition?,
  IncludedCoordinateResultRefs[],
  IncludedRowIds[],
  ViewSpecRef?,
  Annotations?
>

TargetSliceRef is present only when the series construction or publication consumes an A.2.6 selection. The ClaimGraph must then state how each selected slice belongs to or is covered by the authoritative ClaimScope. Identify changes to the time window. Do not silently substitute “latest.”

G.12:4.2 — Method of obtaining the result

Stage A — Select what the view is about

  1. Select the coordinate results. Use persisted C.21 coordinate-result refs for one already identified discipline.
  2. Fix use, scope, and windows. Name IntendedUse and ClaimScope. Add a TargetSliceRef only when the computation or publication consumes it, and state its relation to the scope.
  3. Check replay identity. For every coordinate, resolve the C.21 DHCReplayBasis: Characteristic, Scale, Unit when current, DHCMethodRef.edition, the Method used, MethodDescription edition when used, model or calibration pins when used, time or population basis, and any active distance or definition-set edition.
  4. Choose the comparison branch. Directly comparable C.16 readings need no Bridge. When the comparison uses a relation between distinct local senses, cite the obtaining F.9 relation, observed loss, and a separate affirmative bounded-use claim naming direction, use rule, and loss tolerance, with the current supporting reliance required by F.9. Add reference-plane routing only when the use crosses reference planes; cite its exact basis, and assess any numerical assurance consequence under the applicable B.3 model for the named use.
  5. Choose panels for the receiving use. Portfolio, QD, open-ended, maturity, SoTA, shipping, and advanced-view fields appear only through their extension blocks.

Stage B — Construct or update content

  1. When new coordinates are required, obtain their C.16 measurement results and coordinate-result epistemes with the active C.21 replay basis. Identify the Method used and the dated measurement Work, and the MethodDescription, model, and calibration basis required for that measurement use. Keep these objects separate. G.12 creates none of them from a dashboard row.
  2. When the receiving use needs one series episteme, assemble or revise the DHCSeries ClaimGraph from exact coordinate-result refs and windows. If a series episteme is unnecessary, construct the local view over the result refs. Series assembly may be dated Work; its resulting episteme remains separate from the Work or work record.
  3. Apply A.18 and the A.19/G.0 rules used for comparison, normalization, distance or aggregation. Nominal and ordinal values remain non-arithmetic unless an explicit lawful transformation creates another Scale.
  4. Construct the DHCRow and DashboardSlice representations. Keep each displayed claim linked to its result and replay basis. Label a reported rate with the population it actually describes. If the user needs a decision about a wider population, show the range or estimate supported for that population and whether it settles the decision. A filter that selects fewer rows can change the question a panel answers.

Stage C — Publish or refresh only when required

  1. If public designators are needed, use F.18 for names of already constituted series or views. A name row is not publication.
  2. If an audience must be able to obtain a selected episteme edition, establish E.24.PUB with that exact edition, audience, bounded use, dashboard form, carrier, and interval. If the view itself is the selected episteme, recover its independent C.2.1 identity. Otherwise, if the view presents several source epistemes, identify each selected edition and its publication occurrence. Construct a series episteme only when the receiving use needs that additional ordered account.
  3. If changed definitions, windows, evidence paths, crossing bases, or policies must trigger selective maintenance, emit G.11 telemetry pins naming the affected result or series slice. Otherwise stop without refresh wiring.

G.12:4.9 — Optional Extensions

An extension adds only the panel-specific fields, pins, and triggers consumed by that view. It does not redefine C.21, C.16, comparison, evidence, publication, selection, or refresh semantics.

G.12:4.9.1 - G.12:Ext.SoTAPalette — SoTA palette alignment
  • PatternScopeId: G.12:Ext.SoTAPalette
  • GPatternExtensionKind: InteropSpecific
  • GoverningPatternId: G.2
  • Optional pins: SoTA_PackRef.edition?, exact F.17 cell refs, and obtaining F.9 relation refs when alignment is displayed.
  • No additional trigger kind by default.
G.12:4.9.2 - G.12:Ext.PortfolioTelemetry — selector result panel
  • PatternScopeId: G.12:Ext.PortfolioTelemetry
  • GPatternExtensionKind: MethodSpecific
  • GoverningPatternId: G.5
  • Conditional values: TaskSignatureRef?, resolved DominanceRegime, resolved PortfolioMode, and exact selector result and basis refs.
  • Set-returning semantics remain visible. A scalar headline is only a view annotation unless a separate policy lawfully constructs it.
G.12:4.9.3 - G.12:Ext.QDTelemetry — illumination or archive panel
  • PatternScopeId: G.12:Ext.QDTelemetry
  • GPatternExtensionKind: MethodSpecific
  • GoverningPatternId: C.18
  • Conditional pins: DescriptorMapRef.edition, DistanceDefRef.edition, CharacteristicSpaceRef for the selected space and separate characteristicSpaceDescriptionRef: U.EpistemeRef when an exact description is consumed (resolve the pair under A.19:5.1.1.1), InsertionPolicyRef, EmitterPolicyRef?, ArchiveSnapshotRef?, and PathSliceId[] when refresh uses them.
  • Illumination and coverage stay telemetry unless a separate accepted policy promotes them into the comparator, dominance set, or selected-set criteria under C.18’s trade-off and authority conditions.
G.12:4.9.4 - G.12:Ext.OpenEndedTelemetry — open-ended or transfer panel
  • PatternScopeId: G.12:Ext.OpenEndedTelemetry
  • GPatternExtensionKind: GeneratorSpecific
  • GoverningPatternId: C.19
  • Conditional pins: TransferRulesRef.edition, EnvironmentValidityRegionId?, ProbeBudgetPolicyId?, and PathSliceId[].
  • Open-ended signals do not become dominance objectives by display.
G.12:4.9.5 - G.12:Ext.MaturityLadderPanel — maturity view
  • PatternScopeId: G.12:Ext.MaturityLadderPanel
  • GPatternExtensionKind: DisciplineSpecific
  • GoverningPatternId: G.8
  • Conditional values: MaturityCardRef, MaturityRungId?, and evidence-path refs when the displayed rung relies on them.
  • Adds RSCRTriggerKindId.MaturityRungChange only for a refresh-wired view.
G.12:4.9.6 - G.12:Ext.PackInclusion — shipping stub
  • PatternScopeId: G.12:Ext.PackInclusion
  • GPatternExtensionKind: InteropSpecific
  • GoverningPatternId: G.10
  • Conditional values: exact pack ref, selected DHCSeriesRef.edition or DashboardSliceRef, and the replay or shipping pins required by the included claims.
  • G.10 governs shipping; this extension only identifies what is included.
G.12:4.9.7 - G.12:Ext.ViewFamilySeed — specialized views

An embedding, prediction, change-point, or drift panel needs its selected method, inputs, limitations, and policy before it can affect a claim or decision.

G.12:5 — Interfaces

InterfaceConsumesProduces
Create_DHCSeriesexact coordinate-result refs, discipline, intended use, ClaimScope, windows, comparison basis, optional definition-set and target-slice refsone C.2.1 DHCSeries episteme edition
Update_DHCSeriesprior series edition, added or replaced exact result refs, affected windows, edition rulesuccessor series episteme edition only when C.2.1’s historical-continuation predicate holds, plus exact edition relation when asserted
Render_DHCViewexact result or series refs, view specification, annotationsDHCRow[] and/or DashboardSlice representations
Publish_DHCViewexact selected episteme edition (series, coordinate result, or independently constituted view episteme), dashboard form, and E.24.PUB audience, bounded use, carrier, and intervalobtaining publication relation for that edition when its predicate holds
Emit_DHCTelemetryexact changed definition, window, evidence, crossing, or policy pin and affected sliceG.11-facing telemetry payload
optional panel interfacesthe values specified by the corresponding extensiononly that panel’s representation and conditional refresh pins

G.12:6 — Conformance Checklist

CheckPassing condition
CC-G12-1Every displayed coordinate resolves one exact C.21/C.16 result episteme and the active C.21 replay basis.
CC-G12-2ClaimScope is authoritative; TargetSlice is optional, consumed explicitly, and related to that scope.
CC-G12-3Direct same-semantics comparison uses C.16 conditions without a Bridge; a comparison using a relation between distinct local senses cites the obtaining F.9 relation, observed loss, and a separate affirmative bounded-use claim with its direction, use rule, loss tolerance, and the current supporting reliance required by F.9.
CC-G12-4Characteristic, Scale, Unit, Method, MethodDescription, model, calibration, Work, result, result episteme, series episteme, row, slice, publication, form, and carrier are not collapsed.
CC-G12-5Numeric, ordinal, target-band, normalization, distance, comparison, and aggregation operations cite their exact lawful definitions.
CC-G12-6A series ClaimGraph identifies exact result refs, windows, intended use, ClaimScope, and comparison basis; content change uses the applicable edition rule.
CC-G12-7Rows and slices are view-only representations. They introduce no new objective, scalar winner, evidence, acceptance, or authority.
CC-G12-8Public names and E.24.PUB publication are conditional and separate; local dashboards need neither.
CC-G12-9Refresh telemetry appears only for a named maintenance receiver and identifies the exact affected slice and changed pins.
CC-G12-10Optional panel fields appear only with their extension and preserve the source pattern’s set, archive, maturity, transfer, shipping, or palette semantics.
CC-G12-11The effective G.Core obligations are expanded by value; nil-elided or unused branches are not made mandatory.

G.12:7 — Bias-Annotation

G.12 counters screen-first, “latest”-by-default, scalar-winner, and publication-as-truth bias. An uncluttered view can hide incompatible definitions, while a dense technical record can make a simple trend unreadable. Start from exact result claims, show the smallest useful view, and give readers a way to reach replay and refresh details without crowding the view.

G.12:8 — Consequences

Benefits. Dashboard claims can be read quickly and replayed from exact result and definition refs. Historical results remain distinct from changed definitions, and refresh can be local when needed.

Costs. A relied-on trend needs exact result, scope, window, and replay identities. Publication and refresh add their own conditional work.

G.12:9 — Relations

Builds on: C.21, C.16, C.2.1, A.2.6, C.29, E.24.PUB, and G.Core only for the active Part-G branches.

Coordinates with: G.6 and G.11 for relied-on evidence and refresh; A.19 and G.0 for comparison or aggregation; F.9 when a comparison uses a relation between distinct local senses; F.18 for optional public names; G.5, C.18, C.19, G.8, G.10, and G.2 through the declared extensions.

G.12:10 — Author’s Quick Checklist

  1. Name the discipline, intended use, ClaimScope, exact coordinate-result refs, and windows.
  2. Resolve the C.21 replay basis for every coordinate.
  3. Add TargetSlice only when consumed and state its relation to ClaimScope.
  4. Use the direct comparison branch unless use across distinct local senses requires F.9.
  5. Keep series episteme, measurement Work/result, row, slice, publication occurrence, form, and carrier separate.
  6. Add public naming, publication, evidence paths, assurance, optional panels, and refresh only for named receivers.

G.12:11 — Worked Micro-examples

Decision-making dashboard. A local view shows exact ReproducibilityRate, FormalRecognitionStatus, PracticeAdoptionRate, AlignmentDensity, TraditionShareEntropy, and TraditionShareConcentration result refs. A row showing 60% adoption among respondents gives the number who replied, the number eligible and the period. The portfolio owner asks whether at least half of all eligible units adopted the practice. Show the C.21 result for that population. If every admissible count reaches the threshold, it is met. If every count falls short, it is missed. Two admissible counts on opposite sides leave the answer open. If only an outer bound crosses the threshold, report the limit of that calculation. A tighter calculation with the existing observations may settle the question. The owner decides what to do. Entropy and HHI occupy separate rows with their directions visible. A portfolio panel preserves the G.5 selected set. No audience publication is claimed.

Evolutionary architecture dashboard. A DHCSeries episteme orders exact reproducibility and DisruptionBalance results over declared windows. An optional open-ended panel shows transfer events as telemetry. A later E.24.PUB occurrence makes the selected series edition available to a named audience in dashboard form; that occurrence neither changes the series content nor turns the rendering Work into the health result.

G.12:End

Referenced in the corpus

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