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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:10:20 UTC

A.6:3 - Forces

ForceTension
Modularity vs expressivenessA stable boundary must be abstract, but users want operational detail “in the same doc”.
Truth condition vs governance contentWhether the sentence states what is true or observed, or states a prescription, individual duty, prohibition, commitment, or grant; visible RFC words and the selected subject pattern do not decide this axis.
Design‑time clarity vs run‑time evidenceWhat can be checked statically vs what requires executing work and observing traces.
View, viewpoint, and construction disciplineA view is an episteme satisfying exact viewpoint conformance; a viewpoint is an exact convention-bearing episteme; optional A.6.3 construction and publication remain different relations. Losing any distinction makes omissions and provenance uninterpretable.
Local meaning vs cross‑context reuseBoundaries keep meaning local ↔ cross-context reuse needs its actual correspondence and bounded-use basis. Use an F.9 Bridge only for two exact local senses when its predicate obtains; CL is optional evidence shorthand.
Evolvability vs auditabilityEvolving interfaces requires change; auditors require stable evidence trails.
Human readability vs formal precisionPlain explanations vs tech‑register constraints; both must remain aligned.