fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 98028–98035

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 07:42:37 UTC · snapshot created 2026-10-03 07:43:27 UTC · last check 2026-10-03 07:55:10 UTC

E.18:5.6 - S6 - Cycle discipline (Selection ↔ Planning)

  • The selected structure may center a loop between the SelectionAndTuning locus, whose relation satisfies the named selector and comparator definitions or tests, and the WorkPlanning locus, which binds one exact A.15.2 U.WorkPlan. Any A.15.3 planned-filling row remains declaration-local content inside that WorkPlan.
  • The Selection-Planning loop is represented under local budget and max_iter in Γ_time; at expiry, the exact selector relation returns its declared current set or archive outcome, such as CandidateSet, with the applicable partial-optimality status. If the next step needs changed tuning, a separately identified U.WorkPlan with any declaration-local A.15.3 planned-filling rows, or a separately identified configuration or policy that passes its own applicable rule, carries that tuning; it is not another entity returned by the selector. Further improvement is placed in the next PathSlice only through that explicit planning, configuration, policy, or refresh continuation.
  • UNM occurs before the loop. When the normalized basis shows missing or stale measurements, retain the finding returned by the UNM test. A freshness request remains a request. If the receiving use plans measurement refresh, A.15.2 identifies the exact WorkPlan; when a reusable declaration member must be pinned, A.15.3 adds only a declaration-local row inside that WorkPlan. For later dated refresh Work, recover each exact actual performer through A.13 and let A.15.1 independently admit the occurrence. Add F.6 only when the receiving use also consumes precise assignment-bound attribution; F.6 neither discovers the performer nor supplies classification, and its failure leaves the Work intact. Keep the later measurement and calibration separate. A RefreshReport@Context is likewise separate from the request, plan, Work, measurement, and calibration. A publication that states a calibration target cites the calibration reference and any applicable transport-conversion rule. A penalty requires its own current policy, applicability, rule application, and any authority relation actually used; calibration, conversion, registry publication, or a report supplies no penalty by itself.
  • Work-entry claim and actual Work stay distinct. workEntryClaimRef designates one exact U.WorkPlan, A.15.5 readiness relation, or other prospective claim consumed by LaunchGate. If Work later occurs, each actual launch value is established only through an independently obtaining direct relation or exact A.6.1 application binding of that Work individual. A separate FinalizeLaunchValues episteme may then designate the Work occurrence and those facts; it neither performs Work nor fills slots in the occurrence.

Refresh orchestration. Telemetry records and publications that designate an exact Work occurrence are slice-scoped, editions re-pinned, and faces re-emitted. Telemetry remains a separate episteme and does not constitute the occurrence.