Skip to content

Concepts

How OpenAdapt works: what a demonstration compiler is, how a compiled workflow resolves and verifies each step, and how safety is enforced. Read in order, or jump to what you need.

  • The demonstration compiler

    Why compile a demonstration instead of re-reasoning through it. The record, compile, replay loop.

  • The substrate model

    How one runner contract routes work across browser, native Windows, native macOS, native Linux, RDP, and Citrix/VDI.

  • The deployment matrix

    Hosted browser launch, customer-controlled execution, self-hosting, and the authoring-versus-runtime data boundary.

  • Regulated execution

    replay is the local $0 dev path; run refuses to execute unless certified, identity-covered, effect-verified, signed, and config-pinned.

  • The capability ladder

    One semantic step, many implementations: structural (DOM/UIA), API, and visual. First viable rung wins.

  • Effect verification

    The screen is not the system of record. The five silent write faults and how OpenAdapt catches them.

  • The identity gate

    How the identity ladder distinguishes records and refuses ambiguous input.

  • Governed self-healing

    Repairs under UI drift, written back as reviewable diffs, with zero model calls on the healthy path.

  • The workflow-program IR

    Typed parameters, guards, wait_until, loops, branches, and subflows. A compiled workflow uses these elements to express the intended work.

  • Multi-trace induction

    How several demonstrations provide enough evidence to recover a more complete program.

  • The halt-learn loop

    Demonstrate a correction, compile it, and pass it through regression and promotion gates before the workflow uses it.

  • Durable runtime

    Checkpoint verified progress; a halt becomes a durable pause an operator approves and resumes, never re-running a confirmed write.

  • Policy and certify

    lint reports gaps, certify refuses an unsafe bundle before it deploys.

  • Read a compiled program

    The program map, live evidence, a composed parent, and a process parent.

  • Process contracts

    A parent receipt over independently admitted capabilities. Handoffs copy effect facts. Compose sequences recordings; process points at admissions.

  • Backends: where it runs

    Browser (Playwright), native Windows (UIA), native macOS, native Linux (AT-SPI), RDP, and Citrix/VDI use one backend protocol. Each surface uses the same bundle, identity, result, and policy contracts. Each workflow is qualified in its real environment.

  • The on-prem VLM appliance

    Optional local grounding and identity. When deployed on-prem, observations remain inside that declared customer boundary.