G.12:4.2 — Method of obtaining the result

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, 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. Actual distinct-local-sense use cites 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 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, obtain their C.16 measurement results and coordinate-result epistemes with the active C.21 replay basis. Identify the exact Method and 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 row.
2. When the receiving use needs one series episteme, assemble or revise the DHCSeries ClaimGraph from exact coordinate-result refs and windows. Otherwise construct the local view directly over those result refs. Series assembly may be dated Work; its resulting episteme remains separate from 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 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 a view over several source epistemes identifies 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.