In NPL (Noumena Protocol Language), what is a "protocol", and why is it the central object?

A protocol is the core business-logic object: a stateful agreement between parties that bundles together its data, its allowed actions, and who may perform them.

Rather than scattering business rules across services, NPL packages them into a protocol — think of it as a smart contract for a workflow (a rent contract, a stablecoin issuance, a credit check). A protocol carries:

• State — where the workflow currently is (e.g. requested, verified, rejected), advanced by explicit state transitions.
• Parties — the entities allowed to interact with it.
• Permissions and obligations — the actions those parties can or must take, gated by the current state and by authorization.

Because state, actions, and access all live in one place, the Runtime can enforce them atomically and produce a clear, auditable trace of everything that happened — which is exactly what regulated financial workflows need.

Go deeper:

• Protocols (Noumena documentation) — how a protocol bundles states, fields, permissions, obligations, and parties into one executable agreement.