DEVELOPER PREVIEW
API
Schema-valid-or-fail structured completions under deterministic controls; workspace-scoped keys; endpoint activation per tenant during commissioning.
Developers
Build against governed execution
Everything technical in one place, labeled by what it is today. No invented SDK, no invented endpoint, no production-compatibility claim beyond what is tested.
The developer surface
RUNTIME
AI Motors
The governed execution runtimes: explicit authority before action, bounded workers, separate verification, bounded repair, documented safe stops.
PUBLISHED
Architecture
How models, harnesses, the kernel, Motors, and verifiers divide authority, and why promotion sits outside the executing worker.
IN USE FIRST-PARTY
Action Contracts
Execution starts from an authorized event resolved into a deterministic envelope: policy, delegated authority limits, budget, and permitted context. Motors execute authorized Action Contracts and record effects.
DIRECTION
Acceptance and verdict schema
The chartered direction for portable acceptance: contract in, one of six decisions out (accept, repair, escalate, stop, reject, not evaluable), digest-bound verdicts, signed receipts. In design, not shipped.
PUBLISHED
Receipt structure
What an accepted outcome preserves today, shown on a real run with real digests, plus the boundary that a receipt is not certification.
STATUS BOARD
Integration status
What is live alpha, in commissioning, in design, or planned across every surface.
OPEN
Technical contact
Early technical collaboration, evaluation workspaces, and integration questions.
Current limitations
The API lane is a developer preview under commissioning: activation, billing, and keys are workspace-scoped, and compatibility is tested per provider family within stated scope. The portable Acceptance Gateway and cross-platform adapters are chartered, not built. No uptime commitments are published for preview lanes. No external customers or revenue yet.