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 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:05:10 UTC

C.3.3:4 - Forces

ForceTension to resolve
Same-kind reuse vs bridge disciplineDo not invent a bridge for provenance, but make real distinct-kind correspondence explicit.
Minimal disclosure vs precisionState only what the receiving use consumes while keeping direction, definedness, and loss inspectable.
Local autonomy vs reuseReceiving kinds keep their membership distinctions; correspondence does not merge them.
Separate channels vs workloadScope, sense, and kind correspondence remain separate without forcing all three into every use.
Fresh truth vs useful supportSource results may support reliance but never substitute for receiving admissibility or judgment.