Running on this client's infrastructure

Your file. Your next step, prepared.

This is the Typeless service. It reviews each file's documents, prepares the screen beside the operator, stops before every commitment, and learns the process from the operator's own work. Pair the browser extension below.

Pair the extensionOpen the console

Documents and screenshots leave this network only to the model endpoint the client chose. Final save stays with the operator.

  1. 01 · Work

    Prepare

    The operator drops the file's documents into the side panel. Typeless reads them, asks what is missing or conflicting, and prepares the screen.

  2. 02 · Guard

    Stop

    Final saves, attestations and destructive controls are classified outside the model and left to the operator, in the extension and again here.

  3. 03 · Verify

    Check

    After every action the verifier checks the screen: each value is from the document, seen on screen, or verified.

  4. 04 · Learn

    Promote

    Captured files become skill versions nightly; a regression gate promotes a version only when acceptance does not fall.

Pair the extension

Work alongside it. Teach it your process.

On a managed machine the extension is force-installed by browser policy with this service's URL. To install it by hand:

Load the extension in Chrome or Edge
  1. Open chrome://extensions (or edge://extensions) and turn on Developer mode.
  2. Choose Load unpacked and select the typeless-browser folder.
  3. Put the service URL in the extension's config.json: {"serviceUrl": "…"}
  4. Open the panel, choose Pair and enter the pairing code.

Pairing issues a per-device token. The operations lead can rotate or revoke it from the console at any time. Nothing is stored in the browser except that token.

Pairing code

Checking whether this service issues codes here…

Service

What the extension and the console connect to.

—
contract version
—
service version
—
model

Health

What this service is running on.

—
database
—
object store
—
OpenAdapt bridge

Operators pair from here or from a code the operations lead issues in the console. Runs, episodes, skills, audit entries and metrics are in the console at /console.