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:20:09 UTC

A.1.STM:2 - Forces

ForceTension
Whole-project coherenceA distant use must stay visible without making one pattern id or ClaimGraph stand for all intermediate subject assertions.
Outside before insideArchitecture is justified by a revisable external-use hypothesis, yet discovery and feedback may reopen that hypothesis.
Backward justificationReading from value toward missing support is useful, but it is not temporal order or transformation direction.
Forward actualityWork and changes must be traced through facts that obtain, not through planned arrows or shared names.
Local contributionA team needs to know how its result matters without inventing a universal contribution relation.
Recursive buildersBuild-the-builder reasoning must recur without a creator kind, fixed levels, or a generic creates edge.
Evidence and returnA supported answer may later become stale or fail; reopening should be local rather than restarting the whole map.