IO IORCHArobi public lane

Operator workflow

User Guide

Use JAWS as the desktop trust anchor, approve devices intentionally, and keep project work inside registered folders.

Get JAWS Pricing
Install desktop first

JAWS is the local workspace anchor for projects that live on your machine.

Approve device-aware

Remote phones, tablets, and CLIs should be approved per device and per project scope.

Verify replayable

Session journals make it easier to inspect actions after work is complete.

Screenshot of the JAWS Flight Deck native first-run workspace.
Screenshot of JAWS Flight Deck showing the native workspace in version 0.2.25, launcher dock, inspector, and first-run deck users see after install.

Route governed

First Run

Install JAWS, sign in when prompted, register a workspace, then run commands or file operations only inside the selected project.

  • Use the latest installer from the JAWS downloads page.
  • Keep sensitive files like `.env`, SSH keys, and credential stores out of remote-readable paths.
  • Treat route grants like temporary access, not permanent trust.
  • Use verification when reviewing important sessions.

Route governed

Support Boundary

The public download and checkout routes are active. Private workspace access, device pairing, and agent execution should remain governed through JAWS and Immaculate surfaces.