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 11:53:28 UTC

C.34:3 - Forces

ForceTension
Equivalence vs useExact equivalence is rare and often unnecessary; the declared use decides how much preservation is enough.
Formal rigor vs practitioner actionFormal mapping modes help only when preserved and lost structure are named in architecture terms.
Shape vs semanticsTwo graphs, views, or diagrams can have the same shape while their relation types differ.
Compression vs lossProjection, abstraction, coarsening, and simulation relations make work possible by dropping structure. In a chain from selected source structures to architecture, architecture description or view, and narrative or framework carrier, preservation must be checked relation by relation rather than claimed as one global sameness.
Cross-context reachA mapping across teams, source traditions, tool models, or holon levels needs the applicable Bridge predicate and conformance test when substitution or transfer is claimed.