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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 08:35:10 UTC

G.11:4.4a - Scheduling and priority policy pins

Scheduling strategies (bandit-style allocation, queueing, cadence policies, early stopping, or manual priority rules) may influence the order and budget of refresh work, but they do not define trigger meaning, action semantics, parity semantics, shipping semantics, or Part-G-wide defaults.

G.11 therefore treats scheduling as policy-bound refresh planning:

  • RefreshPriorityPolicyIdRef names the policy used to order or prioritize queue items.
  • BudgetDeclRef names the time, compute, cost, risk, or cadence boundary for the planned refresh.
  • RSCRTriggerKindId[] still comes from G.Core; scheduling policy does not mint trigger kinds.
  • planned refresh remains the exact U.WorkPlan locally called RefreshPlan@Context; executed refresh is recorded in RefreshReport@Context or Work-bound audit.

If no priority or budget policy is declared, no scheduling heuristic is admissible by appearance; the plan must either use the ordinary queue order or state the missing policy pin as a blocker.