# SITEBORNE

**One Contract. Any Platform. Verified Outcomes.**

**The contract and assurance layer for autonomous systems.**

Cross-platform infrastructure for contract-defined machine outcomes.

SITEBORNE lets a buyer define the required outcome once, carry that contract across compatible execution systems, verify the delivered result against the contract, preserve proof of what happened, and keep result access and settlement under their own governed authorities.

**Canonical architecture:** VCM defines what must be true. AVUF determines how to fulfill it. PCC proves what happened.

## Unified Semantic System

The same governed semantic contract projects into multiple machine surfaces rather than being independently redefined by each protocol.

- Product: `https://siteborne.com` — human-facing explanation, trust, pricing, and conversion.
- Network: `https://siteborne.net` — developer contracts, schemas, releases, discovery, and public status.
- Runtime: `https://utility.siteborne.net` — authoritative executable machine state.
- `alerts.siteborne.net` is an operational communications namespace, not a fourth product surface.

## Current live production

Live production remains the v2 generation until the runtime says otherwise.

- `verify_agent_output.v2` / Verify Standard — **$0.017/request**, x402, production enabled.
- `web_context_verified.v2` / Web Direct — **$0.008/request**, x402, production enabled.

Published but not currently production-purchasable:
- `company_evidence_graph.v2` — `$0.0312/request`, disabled.
- `document_evidence_json.v2` — authorization maximum `≤$0.19/job`, disabled.
- rendered web — `$0.029/request`, not production admitted.
- independent reproduction — `$0.049/request`, not production admitted.

For production state and request-specific economics, the live runtime, live OpenAPI, and current quote/x402 challenge are authoritative.

## Release 3 candidate

Release 3 is implemented candidate work under pre-release qualification. It is **not** the production default.

- Service Contract: `3.0.0`
- PCC schema: `2.0.0`
- PCC generation: full PCC result envelope
- Candidate families:
  - `company_evidence_graph.v3`
  - `web_context_verified.v3`
  - `document_evidence_json.v3`
  - `verify_agent_output.v3`

Candidate result authorization:
- public services — contract-governed;
- `document_evidence_json.v3` — `BUYER_AUTHORIZED`;
- `verify_agent_output.v3` — `BUYER_AUTHORIZED`.

Payment does not prove identity. Execution does not by itself authorize result retrieval. PCC is evidence, not permission. Settlement authority remains separate.

## End-to-end mental model

1. Discover a compatible surface.
2. Define the contract.
3. Make the policy/authority decision.
4. Execute through an eligible path.
5. Verify the result.
6. Produce PCC evidence.
7. Apply result authorization where the contract requires it.
8. Apply settlement authority separately.

## Machine surfaces

SITEBORNE projects one semantic truth into:
- MCP
- A2A / Agent Card
- OpenAPI
- Catalog / Registry

Current live protocol surfaces remain runtime-authoritative. Release 3 projections are separately labeled candidate/qualifying and are not described as production-converged.

## Public evidence

Independent observers may provide useful uptime, protocol, schema, registry, or advisory observations. They are evidence only; they do not become SITEBORNE runtime, release, execution, result-access, or settlement authority.

## Start

- [See a verified outcome](developers.md#contract-lab)
- [Developer integration](developers.md)
- [How it works](how-it-works.md)
- [Pricing](pricing.md)
- [Status](status.md)
- [Trust](security.md)
- [Docs](docs.md)

Live runtime: `https://utility.siteborne.net/`


## Fresh external propagation snapshot — 2026-09-24 UTC

Current public observation is intentionally kept separate from SITEBORNE authority.

- Fresh runtime readiness reports `status=ready`, `phase=production`, and paid production services active.
- `siteborne.net` still states that paid services are disabled by policy. This is first-party publication drift and should be reconciled; it does not override runtime state.
- Agenstry observes A2A 1.0, 8 declared skills, x402 metadata, machine/search discovery, and 100% 30-day uptime. Its mutable trust/owner fields have varied across current indexed views, so those scores are not canonical SITEBORNE facts.
- MCPMetrics observes 6 MCP tools and 79/79 successful probes over its current 30-day window, with p50 latency around 706 ms.
- Glama independently observes 6 tools and a healthy endpoint, but its longer-window uptime differs materially from MCPMetrics; the two measurements are preserved rather than averaged.
- Small Print tracks two registry versions, 11 semantic changes in one release, and 0 recorded public advisories at this observation.
- PluginBench exposes the official registry identifier `net.siteborne/utility` and direct Streamable HTTP configuration.
- Mcprush currently misinterprets the server as 0 tools / free. Treat this as observer/parser drift, not SITEBORNE runtime truth.
- FastDrop currently records repeated probe failures despite successful observations by other MCP observers. This is a monitoring/probe-compatibility conflict requiring re-check.
- Search indexes still expose some historical SITEBORNE paths/copy, so search identity convergence is incomplete.
- No confirmed public chain transaction, third-party package integration, or organic community adoption signal was established in the searched sources. Absence of evidence is not evidence of nonexistence.

Machine-readable evidence and monitoring configuration:
- `/osint-snapshot.json`
- `/monitoring-manifest.json`

External observers are evidence only. They never become execution, release, pricing, settlement, or semantic authority.