Reference

Commands, environment, and validation gates.

The compact reference behind every example in these docs — CLI commands, environment variables, current cloud status, and the test gates that back each claim.

Commands

Build first when using the verifier CLI from packages/verifier/dist.

bash
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

verifier hook pack compile --provider claude-code,cursor,codex
verifier hook pack install --provider claude-code,cursor --mode telemetry

# Customer-cloud enterprise distribution only
node packages/verifier/dist/cli.js hook pack install --provider claude-code,cursor --mode enforce
  • platform:golden-path builds the portal client and runs the governed capability dry-run or live example.
  • platform registry validates the private enterprise registry manifest.
  • platform golden-path emits the platform proof from the verifier CLI.
  • hook pack compile inspects generated hook config without writing files.
  • The public hook pack install command installs telemetry hooks.
  • The internal dist/cli.js build installs PreToolUse guards for customer-cloud distributions.

Environment

These values configure live portal ingest and approval polling.

bash
export AUTODEVOPS_PORTAL_INGEST_ENDPOINT="https://portal.example.com/api/verification-portal/ingest"
export AUTODEVOPS_PORTAL_INGEST_SECRET="shared-hmac-secret"
export AUTODEVOPS_TEAM_ID="00000000-0000-4000-8000-000000000000"
export AUTODEVOPS_INGEST_IDENTITY="portal-ingest/customer-security-platform"
export AUTODEVOPS_SIGNING_KEY_ID="customer-ingest-key-2026-05"
export AUTODEVOPS_PORTAL_APPROVAL_REQUEST_ENDPOINT="https://portal.example.com/api/verification-portal/runtime/approval-request"
export AUTODEVOPS_PORTAL_APPROVAL_STATUS_ENDPOINT="https://portal.example.com/api/verification-portal/runtime/approval-status"
export AUTODEVOPS_PORTAL_TIMEOUT_MS=1500

Cloud status

What each cloud path is today.

CloudStatusWhat this means
AWS + BedrockValidated pathReady for demos and regulated-enterprise walkthroughs today.
Azure OpenAI + FunctionsAdapter/provider code presentValidated end to end with your team before it is called supported.
Vertex AI + Cloud RunAdapter/provider code presentValidated end to end with your team before it is called supported.
Full BYOC Cloud packageGapWorker deployment exists; portal + ingest + state + audit are not packaged together yet.

Where the boundary sits

The AWS worker path is real, shipping code. Full BYOC packaging — portal, ingest, state, and audit deployed as one stack — is still open, and Azure and GCP are not at AWS parity yet.

Validation gates

The test gates that back each path — run the ones that cover the surface you are changing.

bash
npm run build:portal-client
npm run build:mcp
npm -w packages/verifier run build
npm -w packages/verifier run test

node --test packages/verifier/test/platform-command.test.js packages/verifier/test/portal-ingest-route.test.js
  • npm run build covers the portal UI and shared app code.
  • npm run lint covers the TypeScript and Next.js app surfaces.
  • The node --test invocation runs the platform command and portal ingest route suites directly.