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 15:41:27 UTC · snapshot created 2026-10-03 15:43:46 UTC · last check 2026-10-03 15:55:10 UTC

A.6.6:3 - Forces

ForceTension
Universality vs precisionOne discipline must cover calibration, evidence linking, reference selection, attribution, gating, etc., without collapsing them into one pseudo-relation.
Minimal kernel vs decision auditabilityFew primitives are preferred, but decision-relevant declarations must expose the basis required by the decision, including witnesses, pins, or explicit time selectors when that use needs them.
Two perspectives, one realityDependent-view and base-view must both be expressible without renaming relation-end meanings or flipping meaning.
Compatibility with A.6.5When a reusable base-relation declaration needs SlotSpecs or edit history, keep SlotKind, ValueKind, and RefKind distinct and do not collapse slot edits with semantic re-declarations.
Lexical guardrailsUmbrella metaphors can hide participants, direction, and the applicable relation rule; the wording must recover those values.
Cross-local integrityWhen a declaration actually depends on a relation between different local kinds, local senses, scopes, or planes, that exact relation must remain explicit and reviewable; different sources alone do not create a Bridge.