Live production and Release 3 candidate, without marketing blur.
This page separates what is running in production from what is implemented or qualifying for Release 3. A candidate badge never means production activation.
Observed live-v2 runtime state, Release 3 candidate contract state, protocol projection status, external observations, and security-reporting state are tracked as distinct evidence dimensions.
Public-safe snapshot only. No customer data, operation identifiers, provider routing, secret material, or internal scoring is exposed here.
Public-safe snapshot only. Protected operation/result identifiers, provider topology, scoring or qualification thresholds, credentials, and internal policy/evidence-graph detail are intentionally excluded.
Production observations stay separate from candidate progress.
These values describe current live production or named external observations. Release 3 candidate values appear in their own section below and do not overwrite runtime truth.
Implemented candidate state.
Not the production default.
Release 3 is far enough along to describe precisely, but candidate progress is not the same as live activation. Each row says what is known without turning development status into a production claim.
| Candidate dimension | State | Public-safe evidence framing |
|---|---|---|
| Service Contract 3.0.0 | CANDIDATE | Governed Release 3 candidate contract; not activated as the production default. |
| PCC schema 2.0.0 | CANDIDATE | Full PCC result envelope is part of Release 3 candidate semantics; live production retains its current PCC generation until activation. |
| Four v3 service families | CANDIDATE | company_evidence_graph.v3 · web_context_verified.v3 · document_evidence_json.v3 · verify_agent_output.v3. |
| REST / HTTP candidate qualification | QUALIFYING | Candidate contract exists; production routing is not claimed. |
| MCP candidate execution wiring | QUALIFYING | Candidate execution wiring is implemented for the four v3 families; projection metadata convergence remains in progress. Not production activation. |
| MCP endpoint migration | TRANSITION | The currently published /mcp endpoint remains the observed active address while a replacement URL is being prepared. The replacement is not published here until governed metadata and public read-back establish it. |
| Constitutional thin waist | GOVERNING DESIGN | AuthorityGrant → ExecutionLease → CommitGrant where required → FinalPccDocument → ResultBinding → SettlementGrant. This is current governing architecture; implementation is not inferred from design alone. |
| A2A projection | CANDIDATE | Candidate projection is tracked separately from the live Agent Card and runtime state. |
| OpenAPI candidate contract | RELEASE-QUALIFIED / CANDIDATE | contracts/releases/3.0.0/openapi/service-contracts.openapi.json is the candidate artifact; live /openapi.json remains production authority. |
| Catalog / registry projection | QUALIFYING | Release 3 surface convergence remains in progress; no 4×4 production-convergence claim is made. |
| Result authorization semantics | CANDIDATE | Public/governed output for public services; BUYER_AUTHORIZED semantics for document_evidence_json.v3 and verify_agent_output.v3. |
| Pre-freeze / activation gate | NOT RUN / NOT VERIFIED HERE | This website does not claim a release gate passed without a machine-verifiable gate artifact and production read-back. |
Propagation is visible.
Agreement is source-specific.
Independent systems can confirm reachability, discovery, protocol support, and public metadata—but they can also lag or misread the same source. SITEBORNE records both the positive signal and the disagreement.
Observer state is classified by source, timestamp, upstream dependency, and parser behavior. External measurements never become runtime, release, pricing, authorization, or settlement authority.
Public production runtime ready.
The runtime readiness probe reports production services enabled as of 2026-09-24. This does not promote any Release 3 candidate surface to production.
Observed readiness proves point-in-time runtime reachability only. Service enablement, protocol conformance, economic admission, result authorization, candidate qualification, and external propagation remain separate status dimensions.
| Area | State | Evidence framing |
|---|---|---|
| Production runtime | READY | Observed live runtime root reports status=ready and production_services_enabled=true. |
| Verify Standard | LIVE / QUALIFIED | OpenAPI 3.1 marks verify_agent_output.v2 / standard production_enabled=true at $0.017/request over x402. |
| Web Direct | LIVE / QUALIFIED | OpenAPI 3.1 marks web_context_verified.v2 / direct production_enabled=true at $0.008/request over x402. |
| Document Evidence | DEFINED / NOT ADMITTED | OpenAPI defines document_evidence_json.v2 but production_enabled=false; max authorized job amount $0.19. |
| Company Evidence | DEFINED / NOT ADMITTED | OpenAPI defines company_evidence_graph.v2 but production_enabled=false. |
| PCC paid-result path | ENFORCED CONTRACT BOUNDARY | OpenAPI states a proof-carrying-context document is returned for paid results and PCC receipt generation precedes settlement. |
| Public result retrieval | NOT EXPOSED | Live security declaration states paid results are delivered in the paid response and no public result-retrieval route exists. |
Canonical truth is healthy.
Some projections are not converged.
Fresh observation found first-party and third-party propagation gaps. They are published here because hiding drift would make downstream machine behavior harder to debug.
| Surface | Observed conflict | Classification / action |
|---|---|---|
| siteborne.net | Network identity now correctly states paid services are active, matching runtime readiness (production_services_enabled=true). | RESOLVED Corrected 2026-09-24. |
| Runtime security.txt | utility.siteborne.net/.well-known/security.txt still publishes security@siteborne.net; governed next-release contact is security@alerts.siteborne.net. | FIRST_PARTY_DRIFT Publish the converged RFC 9116 projection and verify after deploy. |
| Mcprush | Reports zero tools and “free/no billing” while other current observers read six tools and x402 paid-service metadata. | THIRD_PARTY_PARSER_INCOMPATIBILITY Prefer standards-compatible projection; request re-crawl/correction if supported. |
| FastDrop | Reports 15 consecutive MCP probe misses while MCPMetrics, Glama, and Small Print currently observe a reachable tool surface. | PROBE / PROPAGATION DRIFT Request re-check and compare initialize/tools-list negotiation. |
| Search index | Legacy siteborne.com strategic-web/design content remains prominent alongside the Utility Network identity. | SEARCH_INDEX_STALENESS Deploy current canonical product site and monitor re-indexing. |
Configured reporting identity.
Delivery verification remains separate.
The next release is configured to use security@alerts.siteborne.net and RFC 9116 /.well-known/security.txt. This build does not claim mailbox delivery, reply behavior, monitoring, or live publication are verified.
State words mean one thing everywhere.
Production means live. Candidate means implemented or qualifying but not activated. Qualified is an evidenced gate state. Disabled means not available.
