# SITEBORNE Status

Snapshot date: 2026-09-23.

This page separates observed live production, Release 3 candidate state, public protocol surfaces, external observations, and security reporting.

## LIVE RUNTIME

Observed current production:
- Runtime: `ready`
- Production services enabled: `true`
- Current production service generation: v2
- Live OpenAPI: `3.1.0`
- Live PCC standard reported by the runtime: `1.0.0`
- `verify_agent_output.v2` / standard — `$0.017/request` — production enabled
- `web_context_verified.v2` / direct — `$0.008/request` — production enabled
- `company_evidence_graph.v2` — defined, disabled
- `document_evidence_json.v2` — defined, disabled
- rendered web — defined, not production admitted
- independent reproduction — defined, not production admitted

The live runtime and live OpenAPI remain authoritative for production state and economics.

## RELEASE 3 CANDIDATE

Current governed candidate:
- Service Contract `3.0.0` — **CANDIDATE**
- PCC schema `2.0.0` — **CANDIDATE**
- full PCC result envelope — **CANDIDATE**
- four v3 service families — **CANDIDATE**
  - `company_evidence_graph.v3`
  - `web_context_verified.v3`
  - `document_evidence_json.v3`
  - `verify_agent_output.v3`
- REST candidate qualification — **QUALIFYING**
- MCP candidate execution wiring — **IMPLEMENTED / PROJECTION CONVERGENCE QUALIFYING**
- MCP endpoint migration — **TRANSITION / REPLACEMENT TARGET PENDING GOVERNED PUBLICATION**
- Constitutional thin waist (`AuthorityGrant → ExecutionLease → CommitGrant → FinalPccDocument → ResultBinding → SettlementGrant`) — **GOVERNING DESIGN; IMPLEMENTATION NOT INFERRED**
- A2A Release 3 projection — **CANDIDATE**
- OpenAPI Release 3 contract — **RELEASE-QUALIFIED / CANDIDATE**
- Catalog / Registry convergence — **QUALIFYING**
- Release 3 production activation — **NOT RUN / NOT VERIFIED HERE**

No candidate state is promoted to production by this website.

## PUBLIC PROTOCOL SURFACES

### Live
- MCP current published endpoint: `https://utility.siteborne.net/mcp` — **MIGRATION IN PROGRESS**. A replacement URL is not published until governed metadata and public read-back establish it.
- A2A Agent Card: `https://utility.siteborne.net/.well-known/agent-card.json`
- OpenAPI: `https://utility.siteborne.net/openapi.json`
- Catalog: `https://utility.siteborne.net/catalog`

### Release 3
One semantic contract is being projected across MCP, A2A, OpenAPI, and Catalog/Registry. The website does **not** claim the full 4×4 candidate matrix is production-converged.

In particular, Release 3 MCP candidate execution wiring exists while projection metadata convergence remains qualifying.

## RESULT AUTHORIZATION

Release 3 candidate semantics distinguish result existence from result authorization.

- public candidate services — contract-governed result handling;
- `document_evidence_json.v3` — `BUYER_AUTHORIZED`;
- `verify_agent_output.v3` — `BUYER_AUTHORIZED`.

Payment does not prove identity. PCC is not permission.

## EXTERNAL OBSERVATION

Date-scoped independent observations:
- Agenstry — 100% 30-day uptime observed; A2A 1.0 observed.
- MCPMetrics — 100% 30-day uptime observed; 6 tools; schema compliance 100/100; MCP `2026-07-28` observed.
- Small Print — 6 tools observed; 0 public advisories recorded at the current observation.

Third-party observers are evidence only; they do not define production or release authority.

## SECURITY REPORTING

Authorized next-release reporting identity:
`security@alerts.siteborne.net`

Build state:
- contact configured — **PASS**
- contact authorized by project governance — **PASS**
- RFC 9116 product artifact configured — **PASS**
- external mailbox deliverability — **EXTERNAL VERIFICATION PENDING**
- reply path — **EXTERNAL VERIFICATION PENDING**
- monitoring — **EXTERNAL VERIFICATION PENDING**
- live publication/read-back — **EXTERNAL VERIFICATION PENDING**

No deliverability, SLA, 24/7 monitoring, safe-harbor, bug-bounty, or response-time claim is made.

## State vocabulary

- **PRODUCTION** — observed/activated live runtime state.
- **CANDIDATE** — implemented release candidate not yet production default.
- **QUALIFIED** — a specific qualification gate has passed with evidence.
- **QUALIFYING** — qualification/convergence work is in progress.
- **NOT RUN** — required activation/release gate has not been established by the available evidence.
- **DISABLED** — defined but not admitted for production use.
- **EXTERNAL VERIFICATION PENDING** — depends on independent operational read-back.

## Public/private boundary

Public status excludes customer data, result/operation identifiers, provider topology, routing weights, qualification thresholds, private scoring, credentials/secrets, internal policy/compiler logic, and private Evidence Graph structure.


## 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.
