Context and tests

Mapping records reports, proposed cases, observations, and questions. Confirmation creates saved Tests and versions. Runs execute selected versions.

A Project can have multiple Environments and mapping sessions. Each session keeps its own report and conversation.

A test verifies confirmed behavior. Select proposed cases and review their exact expected results before writing.

Confirmation saves the selected report version, expected text, Environment, and permitted actions. Later chat changes do not change that confirmation.

Changed steps and new cases need browser review. A correction in chat cannot create browser evidence or grant action permission.

Proof blocks actions outside the confirmed scope. Review the proposed actions before confirmation instead of assuming broad access.

Proof executes a candidate and verifies it in a fresh browser. All selected tests must pass before automatic activation.

Failure keeps previous coverage active. A separate confirmation can accept reduced coverage while retaining failed cases and the original decision.

Mapping tests use saved browser programs. Their Runs do not call a model or automatically repair failures.

Repository coverage links and the earlier Jobs API belong to a separate workflow. They do not describe the current mapping records.