RESOURCES

A focused library. Every piece earns its place.

Start with the workflow you need today: understand the product, configure a first local run, set the evidence boundary and apply it to a release-critical journey.

Open quickstart Watch the workflow

Product-grounded
No capability theatre
English and Spanish

RERUN / RESOURCES

FIELD NOTES

From first run to release review.

01
Understand the local boundary
02
Build the first journey
03
Set evidence policy
04
Repeat before release

3 STARTING PATHS NO FILLER

CURATED Docs · guide · use case

PRACTICAL

Choose a path

01 · DOCUMENTATION

Understand the runtime. Then create the first flow.

The documentation starts with the operating boundary and the concrete sequence from installation through the first passing run.

DOCS

Documentation overview

A map of execution, authoring, evidence and model-boundary concepts.

Concepts + operating notes

QUICKSTART

First repeatable check

A focused checklist for one short, observable browser journey.

About 15 minutes

02 · GUIDE

Decide what to keep. Decide what to omit.

Use privacy mode intentionally: know which artifacts are produced, how familiar secrets are masked and why full traces deserve separate approval.

GUIDE

Privacy mode in practice

A pre-run review of screenshots, DOM, network, console and trace behavior.

Evidence policy

BOUNDARY

Follow the egress

A precise map of application traffic, local state and optional model context.

Architecture

03 · USE CASE

Turn a release ritual into repeatable evidence.

Use one critical journey before a deployment: establish a passing baseline, capture drift and rerun after the fix.

USE CASE

Release validation

A practical operating rhythm for a checkout, sign-in or critical back-office flow.

Before each release

DEMO

Clean → drift → restored

See the same outcome demonstrated as one concise product sequence.

Guided product tour