Aarmos CLI bridge — local WebSocket host that gives the Aarmos PWA scoped, deny-by-default access to files, shell, git, and read-only Postgres on the developer's machine. The PWA stays the brain; this is the arms.

Aarmos CLI — run any agent locally, across any protocol (MCP, OpenAPI, deep-link), with a signed AVAR receipt on every execution. Sovereign runtime, universal tool gateway, verifiable governance.

Shared types for Aarmos protocol adapters (MCP, OpenAPI, deep-link).

Aarmos adapter for the Model Context Protocol (MCP). Brokers MCP tool calls under Aarmos policy and writes AVAR receipts. Scheme: mcp://<name>/<tool>

Aarmos adapter for deep-link / webhook targets (custom URL schemes, outbound webhooks). Scheme: deeplink://<name>/<op>

Frozen schema for the Aarmos Bundle (aarmos.bundle/1) — the signed, self-contained container of AVAR receipts, policy snapshots, egress ledger rows, and guardrail events used by `aarmos incident export` and `avar verify`.

Frozen schema for the Aarmos Scoped Tool Invite (aarmos.invite/1) — a signed, offline-verifiable capability grant that encodes audience, scope (subset of the 8×8 Action×Resource matrix), obligations, and expiry. Verifiable with @aarmos/avar-core.

Aarmos adapter for OpenAPI-described HTTP APIs. Every method+path is a distinct scope; writes require explicit write scopes. Scheme: openapi://<name>/<operationId>

Six Aarmatix-signed starter policy bundles for Aarmos — PII redaction, budget cap, no external network, approval-required-for-writes, tenant isolation, and kill-switch on anomaly.