Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

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:50:10 UTC

A.15.2:3 - Forces (what the definition balances)

ForceTension we resolve
Universality vs. domain idiomsOne plan concept that fits hospitals, fabs, data centers, and research labs—while honoring local terms.
Commitment vs. flexibilityPlans need enough firmness to coordinate, while remaining easy to update as reality changes.
Intended performer vs. performed-work assigneePlans may name intended performers; the assignment used for performed work is still checked for the work interval.
Budgets vs. performed resource usePlans state targets and reservations; A.15.1 and the exact resource-use or ledger pattern govern performed resource-use facts.
Decomposition vs. fulfilmentPlan tasks decompose conveniently; they do not force a shape on performed Work occurrences.