Developer integration

Developer Guide

Build against the Arobi control plane without bypassing authorization, policy, or evidence records.

Transport mesh-ready

Localhost-first MVP routes can evolve into Tailscale or tsnet-compatible providers without opening public inbound ports by default.

Workspace project-scoped

File and command actions resolve against a registered project root, with traversal and secret-path guards.

Records hash-chain

Event chains are intended to make tampering visible and replay practical.

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

Integration Checklist

Before adding a new route, command, or agent action, define the identity, scope, policy consequence, event record, and resume behavior.

  • Bind action to a subject, device, workspace, and session.
  • Evaluate policy before command execution or file write.
  • Journal intent and completion records with result metadata.
  • Run RESUME_REVALIDATE before continuing after reconnect, retry, or restart.

Route governed

API Lane

The public updater and checkout API routes on iorch proxy to the qline public release and revenue lane. That keeps the current release and payment paths centralized while iorch presents a clean product surface.