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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 08:50:20 UTC

A.15.1:2 - Problem (what breaks without a clean notion of Work)

  1. Plan and occurrence confusion. Schedules and diagrams get mistaken for performed work, so audits and KPIs attach to plans or representations instead of dated occurrences.
  2. Method-description and work conflation. A method description, code artifact, or SOP is reported as if it were performed work; conversely, logs are treated as recipes.
  3. Who and when leakage. People and calendars are baked into method descriptions; reuse and staffing agility collapse.
  4. Resource dishonesty. Energy, money, and tool wear are represented as fields or booked to Methods, local system-role kinds, or assignments instead of being stated through separately obtaining resource-use relations involving exact Work individuals; costing and sustainability measures drift.
  5. Mereology muddle. Teams hand-wave over work parts, retries, overlaps, or long-running episodes; roll-ups double-count or miss work.