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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:45:07 UTC

G.9:5 — Interfaces (minimal I/O; conceptual)

InterfaceConsumesProduces
G.9‑1 Plan_Parityexactly one subject branch—one EntityOfConcernRef or exact targetRefs[] under their existing kinds and editions—plus GroundingHolonRef, ReferencePlane, ClaimScope, EvaluationWindow, BaselineSet, BaselineBindingRef, FreshnessWindows, Budgeting?, EpsilonDominance?, CNSpecRef.edition, CGSpecRef.edition, ComparatorSpecRef.edition, mode-specific measurement or normalization editions when used, SCPRef.edition?, MinimalEvidenceRef.edition?, UNM_id?, NormalizationMethodId[]?, NormalizationMethodInstanceId[]?, ParityPinSet, EvidenceGraphId, PathId[], PathSliceId?, PlannedFillingRows[]?one immutable ParityPlan WorkPlan edition and its exact ParityPlanRef
G.9‑2 Run_Parityexact ParityPlanRef and comparison inputs; G.5‑3 Select only for a selector-facing result, using the plan’s exact TaskSignatureRef and conditional matching TaskMapRefparity/comparison result refs and, when selected, G.5 outcome refs; DRR and SCR pins with PathId[] and, when needed, PathSliceId
G.9‑3 Publish_ParityReportexact ParityPlanRef, parity-run trace refs, and active pinsParityReport carrying the same exact plan ref and baseline binding (UTS publication record; emits canonical RSCR ids)
G.9‑4 Expose_ParityTelemetryTelemetry deltas (archive changes, coverage/regret signals, etc.)Telemetry events carrying PathSliceId?, policy‑ids, and edition pins for refresh wiring

Publication records are conceptual here; serialisations belong in shipping and interop publication forms (see G.10 and interop annexes), not in G.9.