Interoperability contract,
without private internals.
These docs explain the public contract, how execution and proof stay governed, what is live in production, and what exists only in the Release 3 candidate—without publishing private implementation logic.
Public documentation exposes VCM/AVUF/PCC/result-authorization/settlement semantics and release-qualified protocol projections while withholding private scoring, qualification thresholds, provider selection, policy/compiler internals, Evidence Graph structure, credentials, and economic margin/exposure mechanics.
Verification Contract
The Verification Contract is the shared definition of what a successful job looks like: the result, facts that must be true, evidence needed, decision rules, and spending context.
VCM
VCM keeps one definition of success consistent everywhere SITEBORNE exposes it.
PCC
PCC records what happened. In Release 3 candidate work it is a full proof-carrying result envelope; it is evidence, not permission.
AVUF
AVUF is the governed fulfillment layer that determines how an eligible contract can be fulfilled without changing what the customer asked for.
Constitutional thin waist GOVERNING DESIGN
SITEBORNE’s governing design further separates permission to run, permission to commit, proof, result access, and permission to settle. Those boundaries prevent one successful step from silently authorizing the next.
Payment can be authorized without meaning the result is correct or settlement may complete. Economic completion remains a separate governed decision.
Settlement Authority
A result can exist without being authorized for release. Release 3 candidate semantics keep sensitive result access separate from payment and execution.
Result Authorization
Protocol projections
MCP, A2A, OpenAPI, and catalog/registry surfaces are different ways to expose the same governed meaning. The live production projection and Release 3 candidate projection are separate release states.
Public-safe boundary
Public docs show what customers and integrators need to connect, understand decisions, and verify behavior. Proprietary implementation details and secrets stay private.
State words are part of the contract.
SITEBORNE uses the same small set of state labels so a buyer can tell what is only designed, what is being qualified, and what is actually live.
| State | Meaning | May be called production? |
|---|---|---|
| DESIGN | Governed architecture or requirement without an admitted candidate implementation claim. | No |
| CANDIDATE | Implemented or generated pre-release state under qualification. | No |
| QUALIFIED | A defined gate or evidence requirement passed for its stated scope. | Not by itself |
| PRODUCTION | Activated on the authoritative runtime and verified by current read-back. | Yes |
| DISABLED | Published/known but unavailable for production execution. | No |