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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:35:14 UTC

F.8:3 - Forces

ForceTension
Parsimony vs coverageAvoid new durable names while keeping enough vocabulary for recurring work.
Local fit vs reuseA name may be clear under one ReferenceScheme and unsafe for another use or local sense.
Readability vs hidden ontologyShort names help readers but can hide kind, relation, scope, or occurrence identity.
Familiarity vs neutralityA source word may be a useful alias without being the selected FPF designation.
Speed vs downstream costQuick minting is cheap now and expensive when later patterns must repair it.
Traceability vs record-first collapseA result episteme can support replay without becoming the decision occurrence.
Open-world use vs false completenessNo durable name may mean “not needed now”, not “a new U-kind is required”.