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

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

A.2.3:2 - Problem

Without a first-class U.PromiseContent, a project description tends to make five recurring category errors:

  1. Provider = Service. Calling the provider system or team “the service” collapses that provider referent with the promise-content episteme.
  2. API = Service. Treating an interface or endpoint as the service hides the promised consumer-side outcome and its acceptance criteria.
  3. Method or plan = promise content. Treating a semantic method, a method-description episteme, or a work plan as the promise content hides the consumer-facing outcome and acceptance claims.
  4. Run = Service. Logging Work as “a service” erases the promise-content episteme and acceptance specification needed for SLA reasoning.
  5. Business ontology lock-in. Large domain schemes are imported wholesale, losing FPF universality and comparability across projects and domains.