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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:10:20 UTC

A.2.8.PER:4.7 - Keep the handshakes narrow

Neighboring objectExact handshake
Grant or revoke actA.2.9 U.SpeechAct <: U.Work; an admitted holder U.System performs the act under the exact grantor system-role assignment, and institutes.permissions cites the grant occurrence. The assignment supplies the holder and assigned-kind ground; any required authority is established through its own relation. The act and enduring grant retain their separate identities.
Permit episteme and carrierUse C.2.1 for claims about the permission, E.17 for a source-backed publication face, G.11 for source currentness and publication refresh, and A.10 for evidence used in reliance. Use E.24.PUB when the publication occurrence, form, or carrier identity matters.
Duty or prohibitionA.2.8 U.Commitment; permission remains outside its modality family.
Boundary claim or entry predicateA.6.B classifies the claim; an A-* predicate may consume a separately established current permission result.
Work plan and readinessA.15.2 is the pattern for the U.WorkPlan; A.15.5 may cite a separately established permission/conflict result as one readiness input.
Gate decisionUse A.21 for a gate outcome, citing the separate current grant or conflict result whenever its profile requires one.
Work and resultidentify the dated Work under A.15.1. Exercise requires the direct relation above. Claims of capability, readiness, safety, success, or result quality need their own predicates.