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 14:25:10 UTC

A.2.9:9 — Consequences

Benefits

  • Explicit references to approvals, authorizations, and notices support state-condition and admission checks when the selected predicate or direct consumer requires the act.
  • Provides stable provenance: commitments, granted permissions, and status transitions can cite the instituting act explicitly.
  • Makes the actual performer recoverable in occurrence and institutional-provenance claims.
  • Lets a practitioner judge one named receiving use and repair the smallest blocker without first building a complete occurrence record.
  • Keeps observed response, achieved use, later action or change, causal contribution, and permission or admissibility as separately testable questions.

Trade-offs / mitigations

  • A receiving-use judgement may remain conversational when no later claim must cite it. A reliance-bearing use requires a small structured SpeechActRecord plus adequate evidence only when the occurrence itself must remain addressable.
  • Requires one exact recognition-taxonomy episteme and effective reference scheme for SpeechActTypeRef; mitigated by starting with a small set (Approve, Revoke, Publish, Notify, Authorize) and extending that taxonomy deliberately.