Skip to content
Start an evaluation

DOCUMENTATION

Know what runs. Know where it runs.

Use this map to understand the packaged macOS application before building a flow. It separates deterministic execution, integrated authoring, evidence and optional model use.

Start with quickstart Review data boundary
  • Packaged desktop app
  • macOS · Apple silicon
  • No public runner API

DOCS / CONCEPTS

RUNTIME MAP

Author. Replay. Review.

  1. 01

    Authorized origin

  2. 02

    Deterministic timeline

  3. 03

    Privacy-mode artifacts

  4. 04

    Optional model boundary

DESKTOP APPLICATION CURRENT PRODUCT
DOCS SCOPE Packaged capabilities only
REFERENCE
VERSION Desktop · current packaged build SCOPE macOS · Apple silicon · local runtime

OPERATING GUIDE

Controls are named exactly as they appear in the current desktop application for the selected interface language.

01 · QUICKSTART

Create one short flow. Make the result observable.

Choose a journey with a clear final state, use a controlled environment and confirm the first passing run before introducing deliberate drift.

  1. 1.1
    INSTALL

    Prepare the desktop runtime

    Confirm a supported Mac and keep the application under test reachable from that machine.

    macOS · Apple silicon
  2. 1.2
    FIRST FLOW

    Record or author the journey

    Fix the origin, provide encrypted credential references if needed and end with an assertion.

    Observable outcome required Open quickstart

02 · CORE CONCEPTS

Deterministic by default. Intelligence by selection.

The timeline owns execution. Ordinary actions replay predictably; agent authoring creates that timeline, while a selected AI step is an explicit runtime choice.

  1. 2.1
    EXECUTION

    Local browser control

    Sessions, steps and evidence remain owned by the desktop runtime.

    Tested-app traffic still leaves the machine Product overview
  2. 2.2
    MODEL USE

    A separate boundary

    Configure no model, a provider key or the supported local authoring harness according to policy.

    No silent fallback Boundary reference

03 · EVIDENCE

Inspect the failure. Keep privacy mode visible.

A run can retain several evidence layers, each with different sensitivity. Apply the policy before the workflow reaches real customer data.

  1. 3.1
    ARTIFACTS

    Screenshot, DOM, network, console

    Use the smallest evidence set that answers why the result changed.

    Manifest linked to run ID Evidence reference
  2. 3.2
    TRACE

    Explicit sensitive debug mode

    Full trace capture stays off in privacy mode until deliberately enabled for an approved run.

    Opt-in only Privacy guide

Integrated desktop QA agent

Describe it once. Replay it deterministically.

The integrated agent authors the journey inside the site you authorize. Later runs replay that deterministic flow and keep the redacted evidence on the Mac your team controls.

Start an evaluation Review commercial model

macOS · Apple silicon · Signed device entitlements