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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:25:20 UTC

C.31:3 - Forces

ForceTension
Fast architecture repair vs measurement admissibilityPractitioners often need the next modularity move before a full measurement template exists.
Characteristic plurality vs scalar pressureDifferent modularity interpretations have different subjects, scales, evidence, declared measurement or comparison basis, subject-pattern needs, and risks; one score hides that plurality.
Useful proxy vs proxy substitutionA cheap share, count, or graph interpretation can guide local repair, but it may become a false quality, evidence, or decision claim.
Module-interface view vs broader structureModularity can involve functions, flows, control, work, evidence, data, placement, or scale, not only modules.
Local repair vs cross-case useA local diagnosis can stop at report-only use; cross-case comparison needs an exact subject assertion and predicate under C.16, C.25, and G.2. Use G.5 only when selected-set result declaration is current and C.11 for local choice. For publication, use E.17 for a source-backed face and source return and E.24.PUB for the publication occurrence and audience availability. Each source pattern remains only a locator.
Complexity pressure vs complexity ontologyResidual pressure and growth signals are useful, but complexity is not one commensurable architecture characteristic.