Getting Started
Understand the genuine public interface and the production-control boundary.
Explore →Evidence ceiling E3Proof boundary
Developers
Inspect the boundary before you integrate.
The public surface exposes genuine read-only status and standard artifacts. Protected tenancy, identity binding, authorization, approvals, lifecycle, webhook, credential, data-policy, recovery and incident controls are implemented and seller-reference-tested; customer-specific bindings remain externally gated.
Documentation map
Interfaces, controls, and exact activation state.
Implemented seller-controlled contracts are separated from external customer bindings and customer-live evidence.
Quickstart
Inspect deployment status and public standard metadata.
Explore →API Reference
Interfaces actually exposed by this public deployment.
Explore →Authentication
Public reads need no credential. Durable institutional tenancy and protected identity-binding controls are implemented and seller-reference-tested; external customer IdP bindings and customer roles remain unprovisioned until institution activation.
Explore →Organizations
Durable tenant and organization records, role controls and lifecycle operations are implemented and seller-reference-tested; external customer tenants remain 0 until activation.
Explore →Agents
Agents receive identity and bounded delegated authority; model output never grants permission.
Explore →Identity
Human, service, and agent principals are separated and purpose-bound.
Explore →Authority
Mandates define purpose, scope, limits, validity, and revocation.
Explore →Policies
Versioned inputs produce permit, deny, or stop decisions.
Explore →Executions
Execution interfaces deny without side effects on this public Site.
Explore →Evidence
Public schemas illustrate portable receipts without protected records.
Explore →Verification
Verify safe demonstration hashes locally in the Proof Lab.
Explore →Integrations
Protocol classes are documented without implying partnerships.
Explore →Webhooks
Protected webhook registration plus signing, replay, retry and dead-letter semantics are implemented and seller-reference-tested; external customer receivers remain unbound.
Explore →Errors
Unavailable controls return explicit errors; successful mutation is never synthesized.
Explore →Idempotency
Consequential actions are designed around bounded replay and idempotency keys.
Explore →Rate Limits
Tenant/principal rate-limit semantics are implemented and reference-tested; exact production quotas remain deployment policy and are not represented as customer-active.
Explore →Examples
Safe public examples and adverse cases only.
Explore →SDKs
Dependency-free TypeScript and Python reference clients for the protected application API contract.
Explore →CLI
Local configuration, contract validation, offline verification, Outcome Pack inspection, conformance and reference demos.
Explore →Events
CloudEvents-compatible envelopes for application events; the envelope never becomes semantic authority.
Explore →Outcome Packs
Versioned first-party packages binding domain schemas, contracts, sources, adverse cases, corrections and fixtures.
Explore →Connectors
A typed adapter framework across identity, agents, enterprise systems, ledgers, infrastructure and authoritative sources.
Explore →Conformance
Executable seller-controlled reference tests with explicit external evidence boundaries.
Explore →Sandbox
A deterministic local reference environment is implemented; no customer-live multi-tenant sandbox is claimed.
Explore →Developer Security
Verify identity, authority, policy, and evidence independently.
Explore →Schemas
Public standard schemas remain available through read-only endpoints.
Explore →Developer Status
Read the deployment truth boundary from the live status endpoint.
Explore →