Trinity developer docs research index

Purpose:
Use these public, source-backed pages to understand Trinity as a Hermes-first autonomous acquisition operating system with Phoenix/BEAM control plane, hosted Hermes runtime, NVIDIA/Nemotron model proof, Jido content firewall, Stripe revenue/spend rails, account/project-scoped Gmail outreach controls, ToolRouter governance, built-in CRM, documents/artifacts, Postgres, Oban, and audit/ledger proof.

Disclosure rules:
- Public docs include architecture, source paths, statuses, official references, and safe summaries.
- Public docs must not include credential values, OAuth tokens, private account/customer data, unreleased inbound email/document bodies, hidden model reasoning, or raw model context.
- Gmail docs describe account mailbox OAuth, project alias selection, and credential-vault token refs; they must not describe Gmail tokens as project secrets.
- Implemented, partial, planned, sample, fallback, and live-configured behavior must be described honestly.

Recommended reading path:
- About Trinity: /docs/about — Project overview for Trinity as a Hermes-first autonomous acquisition platform.
- Architecture: /docs/architecture — Layered system architecture for Phoenix, Hermes, Jido, NVIDIA, ToolRouter, Stripe, Postgres, and Oban.
- Hermes Integration: /docs/hermes — How Trinity uses hosted Hermes for agent work while Phoenix, policy, and ToolRouter keep authority.
- Jido Policy Firewall: /docs/jido — Specific Jido role: a narrow firewall against data poisoning and unsafe runtime payloads.
- NVIDIA And Nemotron: /docs/nvidia — Nemotron routes, safety review, ModelRouter, ModelDecision proof, and fail-closed model behavior.
- Stripe Revenue And Future Spend: /docs/stripe — How Stripe powers Revenue Mode today and guarded spend/provisioning paths later.
- Security And Governance: /docs/security-governance — Approvals, redaction, ToolRouter, quarantine, credential boundaries, and audit proof.
- Data Flow: /docs/data-flow — End-to-end demo flow from chat through Jido policy, approval, execution, and proof.

Concept, reference, security, and runbook pages:
- Approvals: /docs/concepts/approvals — status=implemented; Human-in-the-loop gates for outreach, purchase, refund, and high-risk actions.
- Audit ledger: /docs/concepts/audit-ledger — status=implemented; Append-only audit and financial proof across orders, revenue, spend, tools, models, and approvals.
- ModelRouter: /docs/concepts/modelrouter — status=implemented; Official NVIDIA/NIM-first model routing and sanitized ModelDecision evidence.
- Project-first workflow: /docs/concepts/project-first-workflow — status=implemented; How operators start in Projects while account, search, notifications, and docs stay global and permission-gated.
- Revenue mode: /docs/concepts/revenue-mode — status=implemented; How Trinity turns offers, acquisition runs, orders, approvals, revenue, and spend into auditable operations.
- ToolRouter: /docs/concepts/toolrouter — status=implemented; Policy-gated execution boundary for Stripe, Gmail, sandbox, and external tool actions.
- Built-in CRM reference: /docs/reference/crm — status=implemented; How Trinity stores companies, contacts, deals, activities, segments, meetings, and snapshot leads as source-of-truth records.
- Documents and artifacts reference: /docs/reference/documents-artifacts — status=implemented; How Trinity handles uploaded documents, quarantined source material, generated docs, graphs, previews, downloads, and proof links.
- Environment variables: /docs/reference/env-vars — status=partial; Safe environment variable names and configuration boundaries.
- Gmail outreach reference: /docs/reference/gmail-outreach — status=implemented; How Trinity separates Gmail OAuth, mailbox readiness, aliases, draft creation, sends, replies, ingestion, and approvals.
- Provider catalog and credential boundaries: /docs/reference/provider-catalog — status=implemented; How Trinity represents provider readiness, credential slots, fallback posture, and secret-safe setup state.
- Routes: /docs/reference/routes — status=implemented; Public, protected, API, and webhook route map for the current Phoenix router.
- Technology stack reference: /docs/reference/tech-stack — status=implemented; Why Trinity uses Elixir, BEAM, Phoenix LiveView, Ecto, Postgres, Oban, PubSub, Fly.io, and Tigris for agent operations.
- Vendor and integration reference: /docs/reference/vendor-map — status=implemented; How Hermes, NVIDIA, Stripe, Gmail, Jido, HubSpot, Fly.io, Tigris, and fallback providers map into Trinity.
- Webhooks: /docs/reference/webhooks — status=implemented; Stripe webhook processing, signature verification, idempotency, and replay visibility.
- Account setup and release smoke: /docs/runbooks/account-setup — status=implemented; Owner-facing setup sequence for account, team, integrations, safety, audit, and danger-zone controls.
- Provider readiness: /docs/runbooks/provider-readiness — status=implemented; How operators verify Hermes, NVIDIA, Stripe, Gmail, webhook, and fallback readiness.
- Live action gates: /docs/security/live-action-gates — status=implemented; Approval, policy, and sandbox boundaries for live sends, live spend, and high-risk operations.
- Secrets redaction: /docs/security/secrets-redaction — status=implemented; How Trinity keeps secrets out of logs, LiveView assigns, model context, and public docs.

Official source references:
- Hermes Agent docs: https://hermes-agent.nousresearch.com/docs/
- Hermes profiles: https://hermes-agent.nousresearch.com/docs/user-guide/profiles/
- Hermes skills: https://hermes-agent.nousresearch.com/docs/user-guide/features/skills/
- NVIDIA NIM LLM API: https://docs.nvidia.com/nim/large-language-models/latest/api-reference.html
- NVIDIA NeMo Guardrails: https://docs.nvidia.com/nemo-guardrails/index.html
- Stripe Checkout Sessions: https://docs.stripe.com/api/checkout/sessions
- Stripe webhooks: https://docs.stripe.com/webhooks
- Gmail API scopes: https://developers.google.com/workspace/gmail/api/auth/scopes
- Gmail drafts: https://developers.google.com/workspace/gmail/api/guides/drafts
- Jido docs: https://jido.run/docs
- Phoenix LiveView: https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html
- Oban: https://hexdocs.pm/oban/Oban.html
- PostgreSQL: https://www.postgresql.org/docs/