FPF Reference

    TIME - Use timing and currentness claims responsibly

    Preface node heading:time-use-timing-and-currentness-claims-responsibly:538

    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

    • Situation and question. A claim about rate, rhythm, delay, effort, inertia, recovery, currentness, or validity window is being used for action. Ask whether temporal-claim adequacy or source currentness orchestration is current.
    • Optional obstacle. A snapshot is used as a trend, a trend as a control law, or an old edition as current.
    • Template A. C.27 Solution -> Dyn2TemporalClaimAdequacyCard. Select when a local temporal claim changes supported use.
    • Template B. G.11 Solution -> RefreshCurrentnessLine@Context. Select when freshness, edition, telemetry, decay, or currentness is the live claim.
    • Boundaries. Stop at the smallest supported temporal card or currentness line. Return when window, bearer, evidence relation, model assumption, source edition, or telemetry changes. Wrong-turn recovery downgrades unsupported rate or currentness claims. Stronger neighbors are C.16 for measurement, C.28 for causal use, A.15 for work, and the direct source or publication governing patterns.
    • Public coarsening. "Time check" restores to the C.27 card or G.11 line.

    Last Updated: 2026-07-12 — upstream FPF commit 44dd8818 (github.com/ailev/FPF)