Account setup and release smoke
Owner-facing setup sequence for account, team, integrations, safety, audit, and danger-zone controls.
Production owner onboarding is separate from demo and submission-video docs. Real account setup starts with the selected workspace, then uses Account, Team, Integrations, Gmail, Stripe, Safety, Audit, and Danger Zone surfaces for owner-controlled administration.
Integrations store credential material outside raw database fields, expose readiness and lifecycle controls, and render only statuses, fingerprints, last-four summaries, safe refs, and audit-safe messages. For Gmail, owners connect a mailbox at account level, create/select aliases, then choose the project's default alias from /projects/:id/secrets.
The first production project should upload source documents/templates, configure Project Gmail, draft an outreach artifact, review inline approval cards, and verify proof before any live send. Release smoke requires a full gate: docs generation/verification/link/sample checks, format, compile with warnings as errors, full ExUnit, assets build, and git diff --check before marking the platform ready.
Official references
| System | Use in Trinity | Official docs |
|---|---|---|
| Hermes | Hosted agent runtime and skills context | Hermes Agent docs |
| Jido | Narrow policy/firewall action seam | Jido Actions and Workflows |
| NVIDIA | Nemotron scoring, safety, and QA decisions | NIM LLM API reference |
| Stripe | Checkout, webhooks, revenue proof, guarded spend | Checkout Sessions API |
| Gmail | Drafts, sends, aliases, scopes, inbound replies | Gmail API scopes |
| Phoenix/Oban/Postgres | Control plane, durable jobs, source-of-truth data | Phoenix LiveView |
Source paths
docs/runbooks/production-owner-onboarding.mdlib/autonomous_agency_web/live/account_livetest/autonomous_agency_web/live/account_integrations_live_test.exstest/autonomous_agency_web/product_surface_route_matrix_test.exs