Pressure State

Pressure State is the second of three operating conditions in the Waypost State Protocol. It is not an emergency. It is not a failure. It is a defined operating mode where the Expedition acknowledges that urgency requires temporary adjustments to the standard governance envelope.

In Pressure State, specific gates can be temporarily bypassed with Station Owner authorization. A Provisional Commission can be issued — deploying a Post with only scope.md and a Directive, deferring the full Groundwork. Human review requirements increase because the agent is operating with fewer guardrails. Every shortcut taken generates an entry in the Debt Ledger with a resolution deadline.

The critical design principle: Pressure State is always temporary. It has a declared reason, a declared entry date, and an expected resolution date. If Pressure State lasts longer than the declared timeline, it is reviewed at the Bearing. If it persists for more than one quarter, it is escalated at the Survey. Pressure State that becomes permanent is not pressure — it is the organisation operating below its governance standard without acknowledging it.

Enter Pressure State when operational urgency requires a shortcut that Standard State does not allow. A new customer integration requires an agent that has not been fully commissioned. A production incident requires temporarily expanding a Post's scope beyond its documented territory. A model update broke golden vectors and the Post needs to keep running while the tests are rebuilt.

All of these are legitimate. All of them are tracked. None of them are permanent.

Exit Pressure State when the conditions that triggered it are resolved. The Groundwork is completed. The scope is re-narrowed. The golden vectors are rebuilt. The Station Owner reviews the Debt Ledger entries, confirms resolution, and transitions back to Standard State.

The most common failure is not entering Pressure State when you should — instead just quietly bypassing gates and hoping nobody notices. The State Protocol exists precisely to make the bypass visible and governed. Take the shortcut. Track it. Resolve it. That is better than pretending it did not happen.