FPF Reference

    A.6.8:4.7 — Runtime/telemetry rule (the “actuals” test)

    Preface node heading:a-6-8-4-7-runtime-telemetry-rule-the-actuals-test:16405

    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

    If the sentence asserts actuals (down/slow/99.9% last week/latency is X/incident occurred), the claim MUST be routed to work + carriers/evidence (deliveryWorkRef + witnesses), not to the clause.

    If an actual is used in a conformance block, KPI, or acceptance argument, it MUST cite the underlying U.Characteristic and measurement procedure and evidence carrier (C.16/C.25), with pinned {UnitType, ScaleKind, ReferencePlane, EditionId}; otherwise it is prose only and MUST NOT be treated as a verified SLO/SLA measurement.

    When needed, also name whether the actual is about the access point (entrypoint symptoms) or the delivery system (realizer symptoms). “Down” can be about the gateway even when the backend is fine; the pattern treats that collapse as an unsupported reading.

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