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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 10:15:17 UTC

E.16:3 - Forces

ForceTension
Creativity vs SafetyExploration autonomy vs hard constraints and override duties
Locality vs ComparabilityA budget stays bound to its claim, working situation, scope, window, policy, and override rule; actual holders, assignments and authority enter a scheduled action check; a Work reference appears only when performance independently qualifies under A.15.1.
Simplicity vs AuditabilityLightweight authoring vs ledger‑grade evidence
Autonomy vs SoDHelpful self‑action vs separation‑of‑duties and human‑in‑the‑loop points

E.16:3.1 - Bias-Annotation

Bias considerations: Gov, Arch, Onto/Epist, Prag, Did. Scope: Universal when wording about a local system-role kind, Method, or Service says that a System may perform Work involving unsupervised decision or actuation, and that Work is admitted through an AutonomyBudgetDecl plus Green-Gate. It is not aimed at purely assistive suggestion-only tools where a human confirms every action at the point of execution.

  • Gov. Bias toward enforceable oversight (hard gates, SoD, canonical override SpeechActs). Mitigation: exploration autonomy is still allowed, but only inside an explicit budget and time window.
  • Arch. Bias toward gate‑and‑ledger structure (Green‑Gate + Work‑anchored AutonomyLedger). Mitigation: telemetrySpecRef can scope what is emitted when full deltas are unnecessary.
  • Onto/Epist. Bias toward typed, testable constraints (MM‑CHR tokens, explicit admissibility checks). Mitigation: budgets are optional‑field (?) so low‑risk contexts can start minimal and tighten over time.
  • Prag. Bias toward measurable quotas may under‑express “soft” autonomy goals. Mitigation: pair decision_tokens with risk_bands to capture non‑counting limits.
  • Did. Bias toward explicit mechanics increases authoring surface area. Mitigation: provide a default AutonomyBudgetDecl template and minimal harness cases in F.15.