PMFA
← Return to Index
025

Backpressure Is Governance

Backpressure is not flow control. It is governance about what happens when capacity is exceeded.
Version 1.0.0 — Ratified

Backpressure is not flow control. Backpressure is authority to say no.

When a system slows or rejects work, it governs demand.

I. The Lie of “Capacity Management”

Backpressure is often described as:

queue limits

rate limits

buffering strategy

throughput tuning

This hides the truth.

Backpressure decides:

who gets served

who must wait

who is rejected

when service is denied

That is governance.

II. Acceptance Is Permission

Accepting work grants permission.

Rejecting work revokes it.

Backpressure defines:

when permission is granted

when it is withheld

under what conditions demand is legitimate

Undeclared acceptance rules are arbitrary power.

III. Silent Backpressure Is Unlawful

When a system silently slows:

clients wait without explanation

intent stalls without outcome

responsibility is unclear

Delay without decision is implicit coercion.

Governance must speak.

IV. Backpressure Must Produce Outcomes

A lawful backpressure decision must:

accept

defer

reject

or redirect

Every outcome must be:

explicit

classified

recorded

attributable to policy

Unobservable pressure is invisible law.

V. Backpressure Shapes Fairness

Without backpressure:

aggressive actors dominate

polite actors starve

systems collapse unpredictably

With declared backpressure:

demand is shaped

fairness can be enforced

abuse can be prevented

Fairness requires constraint.

VI. Backpressure Is Not Infrastructure

Queues, buffers, and thread pools do not decide law.

They execute it.

If governance lives in:

broker defaults

framework internals

network behavior

Then law is accidental.

VII. Replay Requires Backpressure

Replay must reproduce:

the same acceptance

the same rejections

the same deferrals

If load-dependent behavior changes outcomes, audit fails.

Governance must be deterministic.

VIII. Backpressure Must Be Declared Policy

Backpressure belongs in:

kernel rules

registry configuration

versioned policy

Not in:

client retries

infrastructure heuristics

undocumented limits

If pressure changes silently, governance changes silently.

IX. Final Conclusion

Backpressure is governance.

A lawful system:

treats acceptance as permission

declares backpressure explicitly

produces observable outcomes

enforces fairness deterministically

replays pressure decisions faithfully

Anything else governs by congestion instead of by consent.

Canonical text. Interpretations are invalid.
SHA-256: 39920d024685c559d4500fd7bf24f43cc87f49dced233d4885e16f538bc8893a