Documentation

Documentation that explains the system the way the product does.

Learn Open Intent, integrate the authority runtime, verify tokens, and prove No Token, No Action with operator-grade documentation.

Start with the model Quickstart

Intent verificationAuthority TokensFail-closed enforcementEvidence export

87Docs entries

9Browse tracks

No TokenCore invariant

Browse the docs

Grouped by what you are trying to do.

Every page is accurate to the running code. Anything not yet shipped is labelled Roadmap.

Getting Started

Understand what Intended is and submit your first intent for verification.

Architecture OverviewSystem components, data flow, service boundaries, and deployment topology for Intended intent verification inf↗What Is IntendedAn introduction to Intended, the intent verification infrastructure that issues cryptographic authority for au↗QuickstartSubmit your first intent to the Intended authority runtime, read the APPROVED / ESCALATED / DENIED outcome, an↗

Concepts

Understand the authority runtime pipeline, decision tokens, trust boundaries, and semantic intelligence.

Authority Runtime PipelineThe end-to-end path a request takes through Intended — interpret, evaluate, issue, enforce, audit — with the r↗Authority Token ModelThe Authority Token's real structure, Ed25519 signing, per-tenant keys, single-use nonce, 300-second lifetime,↗Policy Safety Controls — Structural Policy, Catastrophic Floor, Read/Write SignalHow Intended's authority engine decides on the raw structure of an action, enforces an always-on catastrophic ↗Semantic IntelligenceHow the Large Intent Model interprets an action into ranked hypotheses and risk signals — and how those signal↗Tenant Trust BoundaryHow Intended enforces tenant isolation through cryptographic trust boundaries and fail-closed defaults.↗Trust ModelUnderstand the trust model that underpins Intended intent verification infrastructure.↗

Operator Workflows

Author policy, simulate impact, deploy safely, and investigate incidents.

Author a PolicyAuthor an Intended authority policy as a governed draft — structure a policy set, scope its rules and effects,↗Control Center OperationsMonitor the authority runtime from the console control center and the supporting health, metrics, and live-dec↗Deploy and Rollback PoliciesPromote a reviewed policy draft to an active version and roll back to a prior version — the real /policy/deplo↗Incident ResponseContain and investigate an authority incident — query the SHA-256 audit chain, inspect and verify an Ed25519 d↗Simulate Policy ImpactPreview the effect of a policy change before deploying — read the draft impact summary (semantic diff, changed↗

Enterprise Administration

Manage tenants, roles, tokens, audit evidence, and emergency controls.

Audit ExportBuild, list, and download tenant audit evidence bundles — how the artifact is assembled, exactly how it is sig↗Emergency ControlsTenant containment actions — halt/resume a tenant or environment, pause a connector, revoke a credential — wit↗Identity Provider OperationsInspect tenant identity readiness, run the OIDC/SAML SSO flows, and operate SCIM v2 provisioning — exact endpo↗Roles and Token GovernanceThe enterprise role/permission matrix and the API credential lifecycle — create, list, and revoke tenant API k↗Tenant AdministrationTenant-scoped admin endpoints for trust posture, environments, members, and role assignment — exact routes, re↗

Developer Integration

Integrate the authority runtime, verify tokens, and build enforcement connectors.

API QuickstartObtain an intended_live_ API key, submit your first intent to POST /intent, and handle the APPROVED (200), ESC↗Connector SDKBuild a fail-closed connector by extending BaseAdapter from @intended/connector-sdk. The base class verifies t↗Enforcement SDKThe @intended-inc/sdk reference — createIntendedSdk, submitIntent, verifyAuthorityToken, simulateIntent, evide↗Enterprise-System Connectors (Beta)Connect Intended to PagerDuty, Datadog, Slack, Okta, Microsoft Entra, HashiCorp Vault, Salesforce, Google Clou↗partial Error Patterns and RemediationThe real error codes the Intended runtime returns — auth, validation, decision, token, and rate-limit failures↗LLM Gateway IntegrationGovern every agent tool call by pointing your runtime's model base URL at the Intended LLM gateway. One env va↗OpenShell and NemoClaw IntegrationCompile Open Intent intents and Domain LIM results into OpenShell sandbox policy YAML with @intended-inc/opens↗Runtime IntegrationsChoose how to put Intended in the path of an agent runtime — submit intents directly, govern through a fail-cl↗Verify Decision TokensVerify Ed25519 Authority Tokens locally with @intended/verify — pin the kid, validate claims, enforce the 300s↗

Security & Compliance

Prove enforcement lineage, understand fail-closed controls, and run readiness checks.

Enforcement LineageHow Intended makes every authority decision provable — the per-tenant SHA-256 audit hash chain, chain verifica↗Fail-Closed ControlsHow Intended behaves when a decision cannot be established — default-DENY, the 500 AUTHORITY_LOOP_FAILED fail-↗OpenShell Integration Threat ModelThreat model and mitigation controls for Intended-governed OpenShell and NemoClaw runtime integrations.↗Operational ReadinessVerify Intended is healthy and its audit integrity holds before going live — liveness/readiness probes, a toke↗Third-Party Runtime BoundariesShared-responsibility and security boundaries for Intended integrations with OpenShell, NemoClaw, coding agent↗

Physical AI

Gate real-world actuation: classify goals, mint edge-verifier tokens, and run the ROS2/PLC integrations.

Physical Authority API ReferenceEvery endpoint, request field, response field, and failure mode for /v1/physical/* — ground truth for direct H↗What is Physical AI on IntendedHow the Intended Authority Runtime layers on top of an existing safety stack to classify, gate, and audit AI-i↗C++ Industrial ControlsIntegrate Intended into TwinCAT 3, Studio 5000, TIA Portal, or custom industrial PCs via the cloud HTTP API an↗partial Edge-Verifier Operator Guide (Roadmap)The planned deployment, monitoring, key-rotation, and failure-mode model for the Intended edge verifier. The v↗roadmap Physical-AI QuickstartFrom sign-up to your first verified Authority Token for a physical action — register an actor, classify a stru↗PLC Migration PatternsCommon safety-PLC interlocks (Siemens F-CPU, GuardLogix, TwinCAT Safety, Pilz) translated into Intended policy↗Python ML PipelinesGate perception → policy pipelines (PyTorch / JAX) on Intended Authority Tokens using the Python SDK or the ra↗ROS2 IntegrationLayer Intended Authority Tokens onto a ROS2 agent — cobot, AMR, drone, surgical — using the intended-ros2 pack↗Rust Safety-Critical Firmware (Roadmap)Wire-format and verification-contract specification for the Intended edge verifier. The native Rust verifier c↗roadmap Safety-Case WritingAuthor a deployment safety case for a machine that adopts Intended. What Intended provides as mechanism, what ↗

API & CLI Reference

REST endpoints with real request/response shapes, and the flat CLI command reference.

API AuthenticationHow Intended authenticates API requests — credential types, the fail-closed gate, headers, scopes, rate limits↗API Reference: AuditQuery the per-tenant SHA-256 audit chain, verify its integrity, and export HMAC-signed evidence bundles. Exact↗API Reference: IntentsSubmit an IntentRequest to the authority runtime and get an APPROVED, ESCALATED, or DENIED decision with a sin↗Policies APIThe authority policy surface — evaluate an intent against policy with POST /authority/evaluate, manage policy ↗OpenShell CommandsCompile OpenShell runtime policy YAML from Open Intent intents and Domain LIM evaluations with @intended/cli's↗Policy CommandsInstall and inspect policy packs from the command line with @intended/cli — the real flat commands deploy-poli↗

Guides

Step-by-step guides for common platform tasks.

Deploy a PolicyInstall a policy pack for your tenant with the CLI or the API so your authority decisions reflect your rules —↗OpenShell Operations RunbookOperate a customer-run OpenShell / NemoClaw runtime governed by Intended — compile and apply policy, monitor d↗OpenShell Runtime QuickstartCompile a sandbox policy YAML for an OpenShell / OpenClaw / NemoClaw runtime from Intended presets, review the↗OpenShell Starter KitThe lightweight in-repo pattern for a first OpenShell pilot — the Open Intent taxonomy, the Intended CLI, and ↗Verify a TokenVerify an Authority Token before any downstream system acts on it — check the Ed25519 signature, the kid-pinne↗

Reference

Glossary, troubleshooting, capability truth matrix, and go-live runbook.

Capability Truth MatrixAn honest matrix of Intended platform capabilities — what is implemented in code today, what is partial, and w↗GlossaryPrecise definitions of Intended terms — IntentRequest, authority decision, Authority Token, audit hash chain, ↗Go-Live RunbookThe production rollout sequence for Intended — pre-deployment verification, required controls, staged cutover,↗Platform Roadmap ProgramsHonest status of Intended's strategic programs — what is implemented in code, what is partial, and what is Roa↗TroubleshootingSymptoms, causes, and fixes for common Intended issues — authentication errors, unexpected denials, token reje↗Platform Jobs-to-be-DonePersona-based guide to the Intended documentation and the workflows each role should follow.↗

Everything else

Additional documentation