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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:05:10 UTC

G.11:4.3 - Orchestration semantics (conceptual; delegating to governing definitions)

Use G.11 to plan scoped actions from typed causes; action semantics remain with their subject patterns.

4.3.1 Ingestion. Consume RSCR triggers from:

  • telemetry hooks (e.g., G.8, G.10, G.12),
  • freshness and decay events (B.3.4),
  • evidence, bridge, policy, edition, relied-on base-definition, named-substrate-edition, or derivation-applicability edits (from the respective subject patterns’ publication faces, forms, or units).

Every ingested signal is normalized into an RSCRTrigger (canonical id, scope, payload pins), with optional alias labels.

4.3.2 Scope closure over the actual dependencies. Compute the minimal dependency closure over:

  • cited evidence and source relations, with G.6 PathId and PathSliceId refs when a graph path slice is the current math-lens expression,
  • declared crossings (G.7 sentinels; CrossingBundle visibility),
  • and pinned references (editions and policies).

G.6 supplies graph expression and citation when used; a graph does not establish the source or dependency relation. For a nongraph result, name the exact source, receiving result/use and dependency under PatternScopeId; use PathSliceId when that dependency scope is actually graph-expressed or independently required by the receiving contract. The closure is a planning-time claim about affected slices, distinct from execution of the planned refresh actions. Interpret a B.3.4 trigger for the receiving claim and use: available information may establish continued applicability, a narrower use, an obtainable refresh need or a necessary suspension. An age-only signal does not determine that disposition. If support remains sufficient, stop with the usable result; retain only the limitation or reason a later recipient needs.

4.3.3 Planning (P2W boundary). When the selected response requires planned refresh, use C.11 and C.19.2 for its marginal contribution, cost, delay and displaced work. Produce RefreshPlan@Context for the actions actually selected; possible action forms include:

  • RerunHarvest (delegates to the selected harvesting or SoTA method, such as G.2; use G.1 additionally only when its generator-kit cards or wiring must change)
  • RerunParity (delegates to G.9)
  • RecomputeSelectionOrSetResult (delegates to G.5)
  • RebindBridgeOrCrossing (delegates changes to the obtaining Bridge to F.9, calibration-record changes to G.7, and crossing visibility to E.18 and the applicable visibility harnesses)
  • UpdateEvidenceBindings (delegates to G.6)
  • ReshipPack (delegates to G.10)
  • UpdateBundle (delegates to G.8)
  • UpdateDashboardSlice (delegates to G.12)
  • EmitDeprecationNotice or EmitEditionBumpLog (publication units governed by this pattern)

4.3.4 Execution and audit. When selected actions are performed as Work or Work-bound audit, publish the corresponding RefreshReport@Context. A scoped applicability judgement can reuse available information without a new experiment; a plan alone establishes neither performance nor a new observation. Gating outcomes (admit, degrade, or abstain) follow G.Core tri-state semantics and are recorded through policy ids and cited evidence or source relations, rather than as local bespoke outcomes.