What the public website can publish, validate, and export, and what it never executes.
Read boundaryPhase 2.46 / v1.5.65
Documentation
Documentation for the custom gateway, metadata routes, UAI-1 envelope records, route contracts, quality gates, and evidence artifacts.
Documentation map
Human documents with machine-checkable edges.
Docs explain the system in human language, while schemas, route indexes, and JSON evidence routes make the same boundaries inspectable by agents.
Receipts, exports, hashes, examples, and non-claims that make readiness reviewable.
Read evidenceAgent-readable metadata fields without agent-authorized runtime control.
Read validationAmbitious product language kept separate from AGI, sentience, certification, and safety claims.
Read language boundaryProof relay
Every guide resolves into a route, schema, or receipt.
The docs are built as a trust relay: human explanations point to machine-readable artifacts, browser-local checks, and evidence a person can review before any Desktop handoff.
Each guide starts with what the public website can safely say and what it deliberately cannot do.
Routes, schemas, hashes, quality gates, and examples give agents a deterministic read-only trail.
Visitors can inspect manifests and examples locally before treating anything as connection-ready.
Docs can prepare the decision, but runtime approval and private endpoint access stay on the local machine.
Docs rule
Explain the claim
Link the artifact
Validate locally
Keep authority local
Explicit human and machine route surface.
QualityQuality gatesCurrent public readiness and non-certification status.
SchemasSchema atlasContracts for endpoint shape, evidence, deployment, and search readiness.
AgentsDeveloper discoveryAgent-readable route sequence with runtime authority false.
SecuritySecurity boundaryNo localhost probing, upload intake, telemetry, credentials, or command dispatch.
ReadinessRoadmap gatesInvited use now, broader distribution after evidence gates.
Start with boundaries
Every path explains what the public site can do before asking anyone to trust a local endpoint workflow.
Technical boundaryFollow the machine routes
Route indexes, schemas, quality gates, and examples give agents a deterministic read-only path.
Route indexTurn docs into receipts
The browser validator turns examples and manifests into local evidence without upload intake.
Open validatorOperating boundary
Public clarity, local authority.
This public site is static metadata and does not dispatch desktop commands, probe localhost, upload files, collect telemetry, request credentials, or claim runtime safety certification.