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 13:55:20 UTC

A.2.8.PER:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
MAY stored as a U.Commitment modalityRecover whether the claim is a strong grant, weak finding, entry predicate, or ordinary prose; use the applicable subject pattern.
No prohibition found, therefore permissionRequire currentness and frame completeness; otherwise return unresolved.
Permit document as permissionRecover the instituting act, current grant occurrence, policy, scope/window, and evidence relation.
Gate pass as authorizationKeep GateDecisionResult in A.21; cite a separate grant/conflict result when the gate actually consumes one.
Permission as readiness or capabilityKeep readiness in A.15.5 and capability in A.2.2; permission supplies neither.
Work “violates permission”Test exercise coverage and any separately governed prohibition; uncovered work is not a permission violation by default.
Unnecessary evaluation records for action match or beneficiary eligibilityTest the Work against the action specification and the performer against the beneficiary branch; cite the already obtaining assignment or on-behalf-of relation and add separate evaluation evidence only when a receiving use needs it.
Precedence “owner” as resolutionApply a policy rule that itself selects the outcome, or name the authorized system’s dated decision Work and current conflict-resolution result; a system-role kind, office, assignment, or policy title alone decides nothing.
Hidden generic beneficiary kindKeep the closed reference union and branch-specific eligibility checks.