fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 119461–119509

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:00:09 UTC

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 explicit 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 an exact coordinate-result ref and selected readable fields.It does not compute, establish, or replace the result.
DashboardSliceA dashboard representation or grouping over exact row, result, or series refs; use C.29 when a mathematical correspondence is claimed.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. A changing time window is not silently encoded as “latest.”