G.12:4 — Solution
Preface node
heading:g-12-4-solution:141927
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
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 throughG.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
Conceptual forms:
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
- Select the coordinate results. Use persisted C.21 coordinate-result refs for one already identified discipline.
- Fix use, scope, and windows. Name IntendedUse and ClaimScope. Add a
TargetSliceRefonly when the computation or publication consumes it, and state its relation to the scope. - 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. - 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.
- 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
- 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.
- When the receiving use needs one series episteme, assemble or revise the
DHCSeriesClaimGraph 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. - 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.
- Construct the
DHCRowandDashboardSlicerepresentations. 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
- If public designators are needed, use F.18 for names of already constituted series or views. A name row is not publication.
- 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.
- 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:Ext.SoTAPalette — SoTA palette alignment
PatternScopeId:G.12:Ext.SoTAPaletteGPatternExtensionKind:InteropSpecificGoverningPatternId: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:Ext.PortfolioTelemetry — selector result panel
PatternScopeId:G.12:Ext.PortfolioTelemetryGPatternExtensionKind:MethodSpecificGoverningPatternId:G.5- Conditional values:
TaskSignatureRef?, resolvedDominanceRegime, resolvedPortfolioMode, 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:Ext.QDTelemetry — illumination or archive panel
PatternScopeId:G.12:Ext.QDTelemetryGPatternExtensionKind:MethodSpecificGoverningPatternId:C.18- Conditional pins:
DescriptorMapRef.edition,DistanceDefRef.edition,CharacteristicSpaceReffor the selected space and separatecharacteristicSpaceDescriptionRef: U.EpistemeRefwhen an exact description is consumed (resolve the pair under A.19:5.1.1.1),InsertionPolicyRef,EmitterPolicyRef?,ArchiveSnapshotRef?, andPathSliceId[]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:Ext.OpenEndedTelemetry — open-ended or transfer panel
PatternScopeId:G.12:Ext.OpenEndedTelemetryGPatternExtensionKind:GeneratorSpecificGoverningPatternId:C.19- Conditional pins:
TransferRulesRef.edition,EnvironmentValidityRegionId?,ProbeBudgetPolicyId?, andPathSliceId[]. - Open-ended signals do not become dominance objectives by display.
G.12:Ext.MaturityLadderPanel — maturity view
PatternScopeId:G.12:Ext.MaturityLadderPanelGPatternExtensionKind:DisciplineSpecificGoverningPatternId:G.8- Conditional values:
MaturityCardRef,MaturityRungId?, and evidence-path refs when the displayed rung relies on them. - Adds
RSCRTriggerKindId.MaturityRungChangeonly for a refresh-wired view.
G.12:Ext.PackInclusion — shipping stub
PatternScopeId:G.12:Ext.PackInclusionGPatternExtensionKind:InteropSpecificGoverningPatternId:G.10- Conditional values: exact pack ref, selected
DHCSeriesRef.editionorDashboardSliceRef, and the replay or shipping pins required by the included claims. - G.10 governs shipping; this extension only identifies what is included.
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.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)