# Provider readiness

How operators verify Hermes, NVIDIA, Stripe, Gmail, webhook, and fallback readiness.

Status: implemented
Version: latest
Review: source-backed

## Readiness surfaces

Provider readiness is exposed through `/status`, `/api/integrations/readiness`, account Integrations cards, provider test actions, and self-launch preflight.

Readiness terms are explicit: metadata configured means public connection metadata exists; secret stored means credential material is stored in the credential vault; test-mode verified means a safe non-live provider check passed; sandbox verified means sandbox policy and account mode are proven; fallback-only means no live provider claim is made; live verified means an operator-controlled live provider smoke passed outside CI.

Fallback/test-mode proof is acceptable only when labeled honestly and never relabeled as live execution.

| Provider | Minimum readiness | Live-action implication |
| --- | --- | --- |
| Hermes | Runtime endpoint, auth posture, profile/skill scope | Chat can queue runtime work when content firewall passes |
| NVIDIA | Official route configured and model decision path verified | ModelDecision can support scoring/safety proof |
| Stripe | Checkout/webhook config and signed event handling | Revenue mode can produce paid proof |
| Gmail | Platform OAuth app, account OAuth mailbox, vault-backed token refs, active sending alias, project Gmail setting, scope posture | Drafts/sends can be policy and approval gated |
| Jido | Policy action path available or fail-closed fallback | Poisoned/unreleased content cannot enter runtime |
| Storage | Bucket/client configured where artifacts/docs are enabled | Uploads/downloads/previews stay access-controlled |


Source paths:
- `lib/autonomous_agency/integrations/readiness.ex`
- `ops/hermes`
- `docs/demo/self-launch-replay.md`