Skip to content

Concepts

These pages explain the model behind OpenAdapt: what a demonstration compiler is, how a compiled workflow resolves and verifies each step, and how safety is enforced. Read them in order for the full picture, 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

    Routing across web, native Windows, and pixel-only Citrix/RDP; the adapters have different maturity today.

  • The deployment matrix

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

  • Fail-closed 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

    Never click the wrong record. The identity ladder and why it refuses rather than guesses.

  • 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 program, not a trajectory.

  • Multi-trace induction

    One demo is evidence, not a specification. How more traces recover the intended program.

  • The halt-learn loop

    Halt, demonstrate the fix, induce it through a regression gate, and never halt there again. Governed, $0, no free-form agent.

  • 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

    Fail-closed safety: lint reports gaps, certify refuses an unsafe bundle before it deploys.

  • Backends: where it runs

    Browser (Playwright) is the supported end-to-end path. Windows UIA is experimental; pixel-only RDP and Citrix remain research. The ladder uses one backend protocol without implying equal maturity.

  • The on-prem VLM appliance

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