Protocol · UCP
UCP is exposed here as posture, not as authority.
Spann’s current UCP layer sits over persisted internal seeded state. That means the surface is inspectable and stable enough to describe publicly, while still remaining explicitly outside live inventory, settlement, and property-authorized execution.
Current claim
A bounded, persistent internal test surface.
The current UCP posture is truthful at the discovery layer because the underlying state is durable, restart-proof, and internally addressable. What it is not is a live transactional promise. Public readers should treat this as proof of shape and discipline, not as a claim that Spann can currently hold, price, settle, or confirm a stay.
Persistent
The underlying seeded state survives restart and redeploy. This is no longer a runtime-only demo surface.
Internal
The surface is still bounded to internal proof and operator-side testing. It is not a public booking lane.
Agent-addressable
The interface is shaped for agent inspection, but that does not mean a public caller can transact through it.
Boundary
Public discovery does not equal live authority.
This page exists to remove ambiguity. A persistent internal surface can be public documentation without becoming a public promise. That distinction is the point of Class 1.
- No live availability or rate claim.
- No public transaction surface.
- No payment handling or merchant settlement.
- No property-authorized execution or guest confirmation.
Next surface
The MCP proof layer is public today.
The public machine-readable proof surface available today sits on the Persimmon MCP side. That surface is read-only and documented separately so readers do not confuse proof of read access with proof of action authority.