TRACK · 01
5 min
LEVEL
Beginner
Your first evaluation
Install the SDK, create one run, inspect the response. The code path is the one new teams need first.
OPEN TRACK
OPEN →RESOURCES · TUTORIALS
Learn by doing.
Quickstarts first. Deeper rollout paths next. Every walkthrough ends with a working artifact you can keep, replay, and adapt — repo-level eval material and reviewed exports, not a sandbox you throw away.
ONE WORKING ARTIFACT PER WALKTHROUGH
WHAT YOU GET
Something you keep
First run, regression bank, field workflow setup, and reviewed rollout. Each one ends with a working artifact you can replay and adapt.
FRESHNESS
Versioned with the platform
Code paths follow the SDK. When the API shape moves, the walkthrough moves with it. No stale snippets.
WHERE IT ENDS
A reviewed export
Install, run, then review. You leave with an export a reviewer can open, not a sandbox you throw away.
LEARNING TRACKS
Pick the next working move.
Each card shows the level, the duration, and the kind of artifact you should leave with. No diagrams. Working code.
TRACK · 02
15 min
LEVEL
Intermediate
Build a regression bank
Turn caught failures into replayable tests. Run the bank before every release. Catch what already slipped once.
OPEN TRACK
OPEN →TRACK · 03
10 min
LEVEL
Intermediate
Wire signed webhooks
Route run.completed, export.ready, and escalation events into CI, incident response, and the archive.
OPEN TRACK
OPEN →TRACK · 04
30 min
LEVEL
Advanced
Field workflow setup
Start from a real input in your field, route the hard cases, and define the signed export the workflow has to produce.
OPEN TRACK
OPEN →TRACK · 05
20 min
LEVEL
Intermediate
Reviewed rollout
Move from a working evaluation to release gates, escalation paths, and exports that survive an audit.
OPEN TRACK
OPEN →TRACK · 06
12 min
LEVEL
Intermediate
Defend the release
Open the signed proof packet, walk the rubric history, and answer the reviewer in one window.
OPEN TRACK
OPEN →TUTORIALS
Run the snippet. Keep the artifact.
The walkthrough finishes when something is running on your own infrastructure. You keep the artifact. The next page tells you what to wire next.
↳ STARTS WITH
An install command, a clean repo, and a question your team can name.
↳ LEAVES WITH
A working artifact, a reviewed reference, and the next step already named.