Your first workflow¶
This walks through compiling a workflow on your own web app: record what you do, compile it, replay it, and read the report. It takes about five minutes and makes zero model calls.
1. Record¶
record --url opens a headed browser pointed at your app and watches what you
do: real clicks, typing, key presses, and scrolls. It writes the same recording
format that compile consumes.
Perform the task once. When you are done, press Ctrl+C or close the browser
window to finish. The recording is written to rec/.
Record a clean demonstration
Do the task the way you want it replayed: one clear path, no dead ends. The compiler treats your demonstration as evidence of intent, so a tidy run compiles into a tidy workflow.
2. Compile¶
Compilation turns the recording into a workflow bundle: an ordered list of steps, each carrying the evidence needed to re-find its target (a template crop, an OCR label, geometry landmarks) and postconditions derived from what the demo actually changed on screen. Write-shaped clicks (save, submit, create, delete) are auto-classified as irreversible so they refuse to act on a low-confidence match.
3. Lint¶
lint reports coverage gaps before you trust the bundle: clicks that act with
no identity check, steps that assert nothing, writes that may be
under-classified. Each finding carries a severity. It is advice, not a gate. See
Write and enforce a policy for the
certify gate that refuses an unsafe bundle outright.
4. Replay¶
Recorded parameter values are the defaults; override any of them with
--param key=value. The run is deterministic and local. On the healthy path it
makes zero model calls and finishes in seconds.
5. Read the report¶
Each replay writes a timestamped run directory under runs/ containing an
illustrated REPORT.md and a machine-readable report.json. The report tells
you, per step, which rung of the resolution ladder resolved the target, whether
the identity check was armed and what it verified, which postconditions passed,
and any heals that were applied. See What you get and
Read and audit run reports.
What is next¶
- Parameterize a value and inject a secret: Parameters and secrets
- Understand why a step healed or halted: Governed self-healing
- Gate a bundle behind a safety policy: Policy and certify