fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 87054–87072

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 18:05:19 UTC

E.10:0.2c.27 - authority, permission, approval, commitment, obligation

These are deontic claims or claims carrying an authority-reference relation, not visual or rhetorical properties.

Recover:

  • the beneficiary System or reference required by the selected predicate; if source wording says role, apply E.10.ROLE and cite a local system-role kind and classification or an obtaining U.SystemRoleAssignment occurrence only when that permission or authority predicate actually uses it;
  • speech act or issuing act;
  • commitment record under A.2.8 for obligation, recommendation-as-duty, or prohibition;
  • exact A.2.8.PER strong grant, weak non-prohibition/non-violation finding, exercise relation, or permission-conflict finding;
  • policy claim and policy/currentness frame;
  • authority relation;
  • entry predicate or gate record or decision record when that is the actual claim;
  • authority-changing decision;
  • wording such as delegated permission: recover the A.2.9 granting or delegating speech-act occurrence and, only when the current policy validly institutes one, the resulting A.2.8.PER GrantedPermissionRelation@Context. Keep the grantor System, any grantor U.SystemRoleAssignment occurrence used by the predicate, the beneficiary System or reference, policy and currentness basis, scope and window, and any separate on-behalf-of or Work relation distinct. The cue mints neither DelegatedPermissionRelation nor another generic delegation or authorization kind; if the pattern that defines the permission claim cannot be recovered, block operative use of the wording rather than naming a relation without a governor;
  • contestability, revocation, scope, window, and expiry condition.

Labels, badges, signatures, dashboards, certificates, comments, reviewer praise, and generated explanations may cue authority-looking cases. They do not carry authority unless the authority act, authority record, authority-reference relation, and evidence or provenance relation selected by the direct authority pattern are named.