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

E.16:7.2 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomWhy it failsRepair
Autonomy-by-label“Autonomous” is claimed but there is no AutonomyBudgetDecl or ledgerAutonomy becomes opaque; cannot be audited or comparedRequire E.16‑S1/S3; reject publication without AutonomyBudgetDeclRef + version
Soft gatesBudget/guards only warn; enactment proceeds anywayViolates Safety and SoD; makes budgets non-enforceableMake Green‑Gate blocking on Core surface (E.16‑S2)
Self-overrideThe actual consumer and override assignments are missing, or their holder, actual-Work or proposed-action identity under the selected species, and window facts match the prohibited joint-allocation case in the declared A.2.7 predicate.A label pair or two different assignment IDs does not establish separation of duties.Resolve both exact A.2.1 assignments, apply the declared incompatibility predicate, reject a prohibited pair, and check the independent authority relation (E.16-S4).
Budget bypass via “scale”Scaling preference relaxes guards or ignores capsUndermines declared limits; breaks comparabilityIn ScaleLensPolicy, guards/SoD must remain non‑weakened (E.16‑S7)
Untyped quotasTokens/caps are recorded without units, or units are mixedLedger becomes non-comparable; audits become meaninglessType budgets and deltas via MM‑CHR (C.16); keep unitful rates/quotas
Ledger-as-loggingLogs exist but are not Work‑anchored (no workRef/budgetId/version or recoverable edition pins)Evidence is non-portable; cannot support parity/refreshRequire AutonomyLedgerEntry attached to U.Work with workRef, budgetId, version, and the referenced declaration’s edition pins