Everything you need to build with AuraOne, and everything a reviewer needs to check it. The provenance chain, the export manifest, the security posture, and the open-source tools you run yourself. Bring the question. We'll bring the page.
Find the page, ship the workflow, and pass the review. The same docs serve the developer doing setup and the reviewer doing diligence.
Every datapoint carries an identity-verified record of who made it and under what rights. The export manifest and schema are here to read.
Reference and quickstart pages move when the surface they describe moves. The changelog tracks what shipped.
Each reference opens a path the team uses while building, connecting, or defending the work. Read the docs, confirm the provenance chain, and run the open-source tools yourself before a pilot.
Quickstart · cookbook
Debug, replay, and ship MCP and A2A agents. Local-first, run on your own infrastructure. Quickstart, cookbooks, CLI, and the export path into CI. You keep the weights.
Dataset · export
Local-first review for robotics datasets. Signed environments, synchronized streams, sensor QA, failure annotations, and an export manifest. Check it before a 100-500 episode pilot.
Managed cloud
Managed cloud setup, key handling, first-run guidance, and the controls reviewers ask about first.
SDK · API
SDK installs, REST endpoints, typed clients, and the snippets that get the first run on the board.
Webhooks · CI
Signed webhooks, CI connectors, incident routing, and the catalog of systems that already speak.
Walkthroughs
Runnable walkthroughs from first install to a reviewed regression bank and rollout checklist. Each one ends with a working artifact you can keep, replay, and adapt.
Controls · review
Posture, controls, response windows, and the review material procurement and risk owners open first. The answer when a buyer asks how supply-chain governance works here.
We'll point your team to the right quickstart, connector, or review material and show how it lines up with the live product. Or download the open-source tools and confirm it yourself.
An install, a setup question, or a reviewer asking where the provenance chain and export manifest live.
A working code path, an exportable evidence packet, and the next step already named.