Documentation

Docs

Start with the operating model, then move into developer integration and operator workflows.

Developer guide User guide

Operators JAWS

Install JAWS, sign in, approve devices, and keep work inside project-scoped routes.

Builders JAWS

Integrate operator and agent workflows through route grants, policy checks, and event records.

Auditors LaaS

Use journal exports and verifier checks to review what happened.

Route governed

Core Concepts

The public lane is built around a few durable terms that should stay consistent across product surfaces.

Local workspace authoritative: the desktop project folder is the source of truth.
Device-approved: access starts from approved devices and scoped sessions.
Route-governed: transport and workspace actions are mediated by grants.
Verifier-checkable: sessions can be replayed against their event chain.

Route governed

New users should install JAWS first. Developers should read the route and policy model before wiring agents into production workflows.