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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:25:17 UTC

G.11:3 - Forces — Minimal recomputation under strict invariants

  • Minimal scope vs. completeness. Refresh must be as local as possible (slice-scoped), but still include a defensible dependency closure over evidence and crossings.
  • Operational urgency vs. auditability. Actual refresh Work must remain inspectable through the needed pins, references and paths. A currentness decision or an unchanged use must not become a fictitious Work occurrence.
  • Alias stability vs. semantic unification. Existing trigger labels must remain usable, but their meaning must be one governing definition and id-based.
  • Modularity vs. orchestration power. G.11 must coordinate harvesting, parity, and shipping without re-implementing them or importing discipline-specific method semantics into core.
  • Policy-bound behavior vs. “smart defaults.” Ordering of refresh, priority heuristics, and budget handling are valuable—but must live as policy-bound extensions, not as hidden universal rules.