PMFA
← Return to Index
022

Timeouts Are Legal Boundaries

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

A timeout is not a performance parameter. A timeout is a boundary of authority.

When time expires, permission expires.

I. The Misinterpretation of Timeouts

Most systems treat timeouts as:

tuning knobs

latency protection

infrastructure concerns

This is incorrect.

Timeouts decide:

how long a request remains valid

when authority ceases

whether action is still permitted

That is law.

II. Time Grants and Revokes Authority

Authority exists within time.

A request submitted at time T may be valid at T and illegal at T + Δ.

Timeouts define that Δ.

Without explicit time limits, authority is infinite.

Infinite authority is unlawful.

III. Silent Timeouts Destroy Accountability

When a system times out silently:

intent disappears

outcome is ambiguous

responsibility cannot be assigned

Did the system reject? Did it fail? Did it decide nothing?

Silence is not lawful.

IV. Timeouts Must Produce Explicit Outcomes

A lawful timeout must:

produce a definitive outcome

be classified (expired, aborted, denied)

be recorded as an event

be attributable to policy

A timeout without outcome is an illegal gap.

V. Timeouts Protect Fairness

Timeouts ensure:

no actor can block indefinitely

no resource can be monopolized

no decision can linger unresolved

Fairness depends on bounded time.

Unbounded execution is asymmetric power.

VI. Timeouts Are Not Retries

Retry decides whether to try again. Timeout decides when authority ends.

Confusing the two:

extends authority illegally

bypasses deadlines

violates policy

They are separate laws.

VII. Replay Requires Timeouts

Replay must reproduce:

the same deadline

the same expiration

the same outcome

If a timeout depends on wall-clock variance or infrastructure load, replay fails.

Failed replay is failed audit.

VIII. Timeouts Must Be Declared Law

Timeouts must live in:

policy

registry

kernel logic

Not in:

client defaults

SDK settings

infrastructure guesses

If timeouts can change silently, law changes silently.

IX. Final Conclusion

Timeouts are legal boundaries.

A lawful system:

treats timeouts as expiration of authority

produces explicit timeout outcomes

records and replays timeouts deterministically

versions timeout policy as law

Anything else allows authority to persist without limit and decisions to occur outside time.

Canonical text. Interpretations are invalid.
SHA-256: 7e6b3b2ddc5e35bdd80bca8d2afbf877421c4d5932fdd88a3346ae03af5aa8d4