PMFA

Essays

40 axioms. Closed canon.

001

Why Flexibility Is a Form of Corruption in Enterprise Software

Flexibility replaces law with negotiation. Negotiation creates violations. Violations destroy trust.

002

Why ERP Failed: No Law at the Core

ERP systems did not fail because they lacked features. They failed because they lacked law.

003

Determinism Is the Only Form of Trust

Trust is created by determinism, not transparency. A system is trustworthy only if the same input produces the same outcome, every time.

004

Configuration Without Authority Is Fraud

When configuration can override law, the system becomes a tool for concealment, not governance.

005

Audit Without Replay Is Fiction

If past decisions cannot be replayed under audit, audit reports are narratives, not evidence.

006

Multi-Tenancy Without RLS Is Theater

Shared databases with tenant IDs are not isolation. They are a single breach away from catastrophe.

007

Configuration Is Not Law

Configuration describes preference. Law defines obligation. Any system that treats configuration as executable authority has no law.

008

State Is a Side Effect

State is not truth. State is residue. Truth is the sequence of decisions. State is what remains afterward.

009

Events Are the Only Source of Truth

Truth is not what exists now. Truth is what happened. Anything that does not preserve what happened cannot claim truth.

010

Determinism Is a Legal Requirement

A decision that cannot be reproduced cannot be defended. Law does not tolerate probability. Law requires certainty.

011

Intent Is the Only Valid Input

A system that accepts raw commands accepts chaos. Intent declares what should happen. Commands declare how.

012

Commands Are Not Decisions

A command expresses intent. A decision is the system's response. Only decisions create history.

013

Projections Are Contracts, Not Storage

A projection is not data storage. It is a contractual transformation of events into queryable state.

014

Schemas Are Legal Boundaries

A schema is not documentation. It is a legal boundary. What the schema forbids cannot happen.

015

Time Is a First-Class Dimension

Time is not metadata. It is a structural dimension. Every decision must be locatable in time.

016

Security Is a Property of Architecture

Security is not a feature added later. It is a structural property of how the system is designed.

017

Validation Is Law Enforcement

Validation is not error checking. It is law enforcement. Invalid inputs must never reach the system.

018

Defaults Are Decisions

A default value is not convenience. It is a policy decision made by the system designer.

019

Silence Is a Decision

When a system says nothing, it has decided not to speak. Silence is not absence of decision.

020

Failure Is a First-Class Outcome

Failure is not an exception. It is a legitimate outcome that must be designed for and recorded.

021

Retries Are Policy Decisions

A retry is not a technical recovery. It is a policy decision about what failures mean and how to respond.

022

Timeouts Are Legal Boundaries

A timeout is not a performance optimization. It is a legal boundary that defines when patience ends.

023

Concurrency Is a Legal Problem

Concurrency is not a performance feature. It is a legal problem about who can act when and in what order.

024

Idempotency Is a Contract

Idempotency is not a technical property. It is a contractual promise that repetition changes nothing.

025

Backpressure Is Governance

Backpressure is not flow control. It is governance about what happens when capacity is exceeded.

026

Queues Are Courts

A queue is not a buffer. It is a court where work waits to be judged and scheduled according to law.

027

Schedulers Are Legislators

A scheduler is not an optimizer. It is a legislator that decides what runs, when, and with what priority.

028

Caches Are Treaties

A cache is not storage. It is a treaty about what can be remembered and for how long.

029

Consistency Is a Promise

Consistency is not a property. It is a promise about what observers will see and when.

030

Availability Is Permission

Availability is not uptime. It is permission to act. Without availability there is no authority.

031

Failure Is a Signal

Failure is not an error. It is a signal that must be transmitted, recorded, and acted upon by policy.

032

Recovery Is a Policy

Recovery is not automatic restoration. It is a policy decision about what to restore and how.

033

Rollback Is Not Undo

Rollback does not erase history. It creates new history that compensates for what happened before.

034

Compensation Is Law

Compensation is not error handling. It is law enforcement for when actions must be legally reversed.

035

Observability Is Accountability

Observability is not monitoring. It is accountability. What cannot be observed cannot be governed.

036

Metrics Are Incentives

Metrics are not measurements. They are incentives that shape behavior. What you measure you govern.

037

SLAs Are Public Promises

An SLA is not a target. It is a public promise that creates legal obligation and accountability.

038

Contracts Are Executable

Contracts are not documents. They are executable rules enforced by the system at runtime.

039

Policy Is the Product

The product is not the software. The product is the policy that governs what the software does.

040

The System Is the Law

If the system allows it, it is allowed. If it does not, it never existed. The system is the law.