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 12:30:19 UTC

D.3:4 - Boundaries

Do this in D.3Do not do this in D.3
Derive the declared levels and scopes from the case.Invent U.Level, U.Frustration, U.Emergence, or a fixed moral ladder.
Connect every side’s claim, affected entity, scope, value frame, consequence, and horizon.Present flat bags of entities, values, evidence, and relations as if their connections were obvious.
Keep the conflict description, the situation it describes, and its narrative, table, graph, form, carrier, and publication separate.Treat a file or diagram as the conflict, or treat description content as proof that a direct relation obtains.
Add Method, Work, assignment, classification, evidence use, agency, responsibility, publication, assurance, causal, or architecture detail only when current.Require assurance-like apparatus before the first useful map exists.
Stop at an inspectable tension and next-use question.Choose the compromise, refusal, override, or accepted residual; those are D.4 uses.
Use C.30.ILC when an architecture residual is also current.Route every cross-scope architecture problem to ethics.