FPF Reference

    4.3 Minimal first-day construction

    Preface node heading:4-3-minimal-first-day-construction:1344

    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

    1. Declare CG‑Frame (what “quality” means; admissible units and scales) and ReferencePlane.
    2. Pick 2–4 Q components + a simple DescriptorMap (≥2 dims) for N/D; publish editions.
    3. Choose an E/E‑LOG policy (explore↔exploit budget); record policy‑id.
    4. Apply G.5 selection/dispatch with parity pins. Keep any consumed Front or Archive identified as the source set. For a set outcome, return Shortlist or RankedShortlist for retained alternatives, or JointUseSet when all named members are included for one named use. Return a handoff, abstain, or escalation when that is the actual G.5 outcome.
    5. Keep the actual G.5 outcome's required content and basis pins. Publish that result only when the receiving use calls for publication, with its applicable PathIds/PathSliceId. Add a UTS row for a named governed value only when F.17's independent naming and reuse conditions hold; otherwise reuse its existing designation. Follow the outcome's continuation or stop. An Illumination Map remains report‑only telemetry by default.

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