Developer docs

Build governed agent integrations inside the customer boundary.

These docs cover the developer platform surfaces that exist now: signed agent activity, JS/TS connector helpers, portal approvals, portable hook packs, private capability registry metadata, and portal provenance.

Validated path

AWS Cloud + Amazon Bedrock

Data boundary

Customer-owned BYOC install

Capture model

Ingested events, not an LLM proxy

Start here

Use the dry-run path before wiring a live portal. It validates payload shape, provenance, redaction, and approval evidence without requiring secrets.

bash
npm install
npm run platform:golden-path

npm -w packages/verifier run build
node packages/verifier/dist/cli.js platform registry
node packages/verifier/dist/cli.js platform golden-path

What this proves

The golden path emits a governed connector transcript with session.started, tool.started, approval.requested, hook.blocked, agent_run_audit.source_snapshot, and session.finished events. Live mode posts the same shape through portal ingest.

Implementation truth

The docs should sell what is real without hiding roadmap gaps.

SurfaceCurrent statusDeveloper path
Signed event ingestImplemented for legacy verifier telemetry and generic agent_activity.v1 events through the portal ingest endpoint.Read the event schema
JS/TS connector helperImplemented in @autodevops/verifier-portal-client with dry-run validation, signed posting, idempotency, redaction, and provenance.Build a connector
Portal approval bridgeImplemented for signed approval request/status polling. Governed actions fail closed when approval cannot be reached.Wire approvals
Hook packsImplemented for Claude Code, Cursor, and Codex lifecycle telemetry with opt-in enforced PreToolUse guards. Live walkthrough remains pending.Install hook packs
Cloud deploymentAWS + Bedrock is the validated path. Azure and GCP adapters/providers exist as roadmap tracks, not validated customer paths.See reference