Schema · handoff
Documentation
The provenance schema, the handoff file, and the setup paths teams open while building. Find the page, ship the workflow, pass the review.
Start here for product docs, support paths, security materials, open-source tools, tutorials, and research notes. Find the page for what you are trying to build, deploy, or verify.
Every datapoint carries an identity-verified record of who made it and under what rights. The docs show the schema and the handoff file.
Agent Studio Open and Robotics Studio Open are local-first tools for scoped programs. Use the docs to install, run, and inspect the files yourself.
Docs, references, and operating notes ship with the release they describe, so what you read is what you run.
This is where a skeptical reviewer confirms three things before a pilot: the data carries a consent trail, the architecture is explicitly scoped, and every reviewed item can be inspected. 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.
Schema · handoff
The provenance schema, the handoff file, and the setup paths teams open while building. Find the page, ship the workflow, pass the review.
Walkthroughs
Runnable paths from first install to a reviewed run. Every walkthrough ends with a working artifact you can keep, replay, and adapt.
The method
The method behind the work, defended. How important AI work becomes the live surfaces teams use to measure, review, and stand behind a decision.
Operating notes
Notes from the teams running real launch checks. Measurement, review, regression coverage, and what a release should be allowed to claim.
Owner · window
Product, security review, procurement, and incidents on separate paths. Each with a named owner, a response window by plan, and a live status page.
SDK · API
SDK installs, REST endpoints, signed webhooks, and integration recipes. Typed, ready to wire.
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.
A provenance question, a setup task, or a decision you have to defend under audit.
The schema, the handoff file, a working artifact, and the next step already named.