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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:50:05 UTC

A.11:1.1 - Forces

ForceTension
Expressive reach vs. kind inflationFPF must name durable objects clearly, but each extra root kind increases learning, checking, and bridge cost.
Local usefulness vs. universal burdenA local project name may be helpful in one context, while a U-kind becomes a cross-corpus obligation.
Composition vs. material lossExisting slots, relations, and patterns often express the claim, but some candidates preserve a distinction that composition would hide.
Reader clarity vs. ontology compactnessA plain label can help users, but a convenient label must not conceal a relation, slot position, publication form, or mathematical lens.
Growth vs. reopenabilityFPF needs new primitives when problems demand them, but admitted values need reopen conditions when overlap or fuzziness appears.