FPF Reference

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

    Preface node heading:g-9-5-interfaces-minimal-i-o-conceptual:80933

    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

    InterfaceConsumesProduces
    G.9‑1 Plan_ParityBaselineSet, BaselineBindingRef, FreshnessWindows, Budgeting?, EpsilonDominance?, CNSpecRef.edition, CGSpecRef.edition, ComparatorSpecRef.edition, SCPRef.edition?, MinimalEvidenceRef.edition?, UNM_id?, NormalizationMethodId[]?, NormalizationMethodInstanceId[]?, ParityPinSet, PlanItemRefs[]?ParityPlan@Context (UTS entry; edition‑pinned)
    G.9‑2 Run_ParityParityPlan@Context, TaskSignatureRef (S2), G.5‑3 SelectSelector outputs (selected sets / archives / sets as refs), DRR+SCR pins with PathId[]/PathSliceId?
    G.9‑3 Publish_ParityReportparity-run trace refs + active pinsParityReport@Context (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.

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)