> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Production Readiness

A launch checklist for publishing B3OS workflows safely and keeping docs, APIs, actions, and operations in sync.

Use this checklist before turning a workflow, template, connector, webhook, or API integration into a production dependency.

**Launch readiness coverage**

**Required coverage**

| Check | Requirement |
| --- | --- |
| Definition validates | The workflow passes validation and every node payload matches its action or trigger schema. |
| Connectors are scoped | Each connector belongs to the correct organization, has the minimum required provider access, and has a clear owner. |
| Wallet actions are bounded | Any action that can move funds has chain, recipient, token, amount, and approval behavior reviewed with simulation or test funds. |
| Failure paths are observable | Failed runs, failed nodes, webhook delivery errors, and retry exhaustion are visible through the app, API, or execution webhooks. |
| Docs are updated | Any new action, trigger, endpoint, or workflow pattern has matching public docs and reference output. |

**Production launch loop**

**Validate definition**
  **Scope access**
  **Bound side effects**
  **Observe failures**
  **Publish and document**
  **ready**
  **least privilege**
  **test paths**
  **launch**

## Operational Policy

| Area | Requirement |
| --- | --- |
| API keys | Use service-specific keys with the narrowest available scope. Rotate after incidents and team changes. |
| Connectors | Store credentials in connectors, not workflow payloads or documentation. |
| Wallets | Use dedicated organization wallets for automated workflows. Avoid mixing operational wallets and human wallets. |
| Webhooks | Verify signatures, handle retries idempotently, and monitor replay volume. |
| Templates | Treat public templates as product surfaces. Remove organization-specific secrets, IDs, and assumptions. |

## Public Contract Review

Before launch, confirm the public docs, API reference, action reference, trigger reference, and runbook match the workflow behavior users will rely on.

**References are part of the product**

Action and trigger schemas are user-facing contracts. Keep public references aligned with the product behavior
  developers will build against.