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

E.17.AUD.OOTD:3 - Forces

ForceTension
Local repair vs publication-unit stabilityThe pattern must not replace local precision repair, but it must become available when local repair no longer stabilizes the unit.
Primary-subject clarity vs surrounding-work convenienceThe unit must keep one primary subject without forcing the whole surrounding work process into the same text.
Interpretation clarity vs overgrowthThe section must distinguish primary subject, exact EntityOfConcern when applicable, concern, carried move, downstream use, publication form, carrier, and process without turning into a giant ontology lecture.
Plain entry vs later assuranceThe opening must stay light enough for ordinary use while preserving the distinctions needed if a concrete neighboring claim or assurance question later arises.
Publication-unit stability vs architecture replacementThe pattern must not replace view, face, carrier, publication, or moving-lineage architecture.