FPF Reference

    ACTUAL-TEMPORAL-STRUCTURE — Recover what actually obtains before testing coordination

    Preface node heading:actual-temporal-structure-recover-what-actually-obtains-before-testing-coordination:586

    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: A cycle, onset list, trace, notation, or geometry is called rhythm, but may be a prescription, representation, Method unfolding, or account rather than what obtains.
    • Question: Which subjects and relations support one actual selected structure, what grounds it, and what coordination change should be tested?
    • First useful result or honest blocker: One A.22-selected structure and grounded C.2.1 account—or the missing bearer, relation, observation, or grounding. Keep future specifications and representations separate. For coordination, add direct relations, trial conditions, observations, and next decision or stop.
    • Mantra: Start with actual changing subjects and use. Recover changes, Work parts or continuous carrier, plus exact obtaining relations. Select one structure; ground only supported account. Keep structure, account, future specification, representation, Method unfolding and Work distinct. For coordination, name bearers and direct relations; compare interventions, try one in bounds, observe, then decide or stop. Never infer structure from periodicity, onsets, notation or geometry.
    • Start with: A.3.4/A.15.1 for change/Work, C.27.TA/A.22 for claim/structure, C.2.1 for account; add specification, representation, decision, causal, trial, or domain patterns only when current.
    • Stop or return: Stop when use is answered. Return when bearer, relation, constraint, grounding, intervention, or use changes; domain Methods stay in DPF.

    Last Updated: 2026-09-03 — upstream FPF commit b999972c (github.com/ailev/FPF)