DOC · RESOURCE
№ 01
OPENS
Schema · manifest
Documentation
The provenance schema, the export manifest, and the setup paths teams open while building. Find the page, ship the workflow, pass the review.
READ THE PAGE
OPEN →RESOURCES · VERIFY BEFORE YOU SHIP
Read the docs. Then audit us.
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.
EVERY DATAPOINT CARRIES ITS RECORD
VERIFY
See the chain
Every datapoint carries a signed, identity-verified record of who made it and under what rights. The docs show the schema and the export manifest.
RUN IT YOURSELF
Keep the weights
Agent Studio Open and Robotics Studio Open are local-first tools you run on your own infrastructure. No pooled data. Weights you keep.
FRESHNESS
Versioned with the platform
Docs, references, and operating notes ship with the release they describe, so what you read is what you run.
VERIFY IT BEFORE YOU SHIP IT
Read it, run it, then check it.
This is where a skeptical reviewer confirms three things before a pilot: the data carries a signed chain of consent, the architecture is one you run yourself, and every reviewed decision exports an evidence packet that survives an audit. The reasons you came — a competitor that lost four terabytes including who its workers were, the largest data vendor absorbed by a lab it served, the EU AI Act clock running to August 2026 — are the reasons to read on.
TUT · RESOURCE
№ 02
OPENS
Walkthroughs
Tutorials
Runnable paths from first install to a reviewed run. Every walkthrough ends with a working artifact you can keep, replay, and adapt.
READ THE PAGE
OPEN →RSH · RESOURCE
№ 03
OPENS
The method
Research
The method behind the work, defended. How important AI work becomes the live surfaces teams use to measure, review, and stand behind a decision.
READ THE PAGE
OPEN →BLG · RESOURCE
№ 04
OPENS
Operating notes
Blog
Notes from the teams running real release gates. Measurement, review, regression coverage, and what a release should be allowed to claim.
READ THE PAGE
OPEN →SPT · RESOURCE
№ 05
OPENS
Owner · window
Support
Product, security review, procurement, and incidents on separate paths. Each with a named owner, a response window by plan, and a live status page.
READ THE PAGE
OPEN →DEV · RESOURCE
№ 06
OPENS
SDK · API
Developers
SDK installs, REST endpoints, signed webhooks, and integration recipes. Typed, ready to wire.
READ THE PAGE
OPEN →RESOURCES
Bring the question. We'll bring the page.
Docs to build with. Tutorials that end with a working artifact. Research to defend the method. A security path that answers the hard question before you ask it.
↳ STARTS WITH
A provenance question, a setup task, or a decision you have to defend under audit.
↳ LEAVES WITH
The schema, the export manifest, a working artifact, and the next step already named.