FPF Reference

    G.12:4.2 — Method of obtaining the result

    Preface node heading:g-12-4-2-method-of-obtaining-the-result:106935

    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

    Stage A — Select what the view is about

    1. Start from exact results. Select persisted C.21 coordinate-result refs for one already identified discipline. Do not compute from labels or restate Characteristic semantics in G.12.
    2. Fix use, scope, and windows. Name IntendedUse and ClaimScope. Add a TargetSliceRef only when the computation or publication really 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, exact Method and MethodDescription, model or calibration pins when used, time or population basis, and any distance or definition-set edition.
    4. Choose the comparison branch. Directly comparable C.16 readings need no Bridge. Actual distinct-local-sense use cites the obtaining F.9 relation, direction, admitted use, and loss. Add reference-plane routing only when a real plane crossing is used; cite its exact basis, and keep any assurance consequence in R only.
    5. Open optional panels only when used. 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, separately identify the C.16 measurement Method, MethodDescription, model, calibration, dated Work, result, and result episteme. G.12 creates none of them from a row.
    2. Assemble or revise the DHCSeries ClaimGraph from exact coordinate-result refs and windows. This assembly may be dated Work; the series episteme is its result, not the Work or work record.
    3. Apply A.18 and any exact A.19/G.0 comparison, normalization, distance, or aggregation rule actually used. Nominal and ordinal values remain non-arithmetic unless an explicit lawful transformation creates another Scale.
    4. Construct DHCRow and DashboardSlice representations. They may omit fields for readability only when every displayed claim still resolves its exact result and replay basis.

    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 the selected edition, establish E.24.PUB with exact audience, bounded use, form, carrier, and interval.
    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.

    Last Updated: 2026-09-03 — upstream FPF commit b999972c (github.com/ailev/FPF)