Docs search

Search source-backed pages by route, module, provider, policy, or concept.

Keyboard: / focus search Cmd/Ctrl+K open command menu

concepts · implemented

Approvals

Human-in-the-loop gates for outreach, purchase, refund, and high-risk actions.

concepts · implemented

Audit ledger

Append-only audit and financial proof across orders, revenue, spend, tools, models, and approvals.

concepts · implemented

ModelRouter

Official NVIDIA/NIM-first model routing and sanitized ModelDecision evidence.

concepts · implemented

Project-first workflow

How operators start in Projects while account, search, notifications, and docs stay global and permission-gated.

concepts · implemented

Revenue mode

How Trinity turns offers, acquisition runs, orders, approvals, revenue, and spend into auditable operations.

concepts · implemented

ToolRouter

Policy-gated execution boundary for Stripe, Gmail, sandbox, and external tool actions.

getting-started · implemented

Trinity platform overview

Production-grade autonomous acquisition and revenue operations framework.

getting-started · implemented

Quickstart

Clone, configure, run, and verify Trinity locally without leaking secrets.

reference · implemented

Built-in CRM reference

How Trinity stores companies, contacts, deals, activities, segments, meetings, and snapshot leads as source-of-truth records.

reference · implemented

Documents and artifacts reference

How Trinity handles uploaded documents, quarantined source material, generated docs, graphs, previews, downloads, and proof links.

reference · partial

Environment variables

Safe environment variable names and configuration boundaries.

reference · implemented

Gmail outreach reference

How Trinity separates Gmail OAuth, mailbox readiness, aliases, draft creation, sends, replies, ingestion, and approvals.

reference · implemented

Routes

Public, protected, API, and webhook route map for the current Phoenix router.

reference · implemented

Technology stack reference

Why Trinity uses Elixir, BEAM, Phoenix LiveView, Ecto, Postgres, Oban, PubSub, Fly.io, and Tigris for agent operations.

reference · implemented

Vendor and integration reference

How Hermes, NVIDIA, Stripe, Gmail, Jido, HubSpot, Fly.io, Tigris, and fallback providers map into Trinity.

reference · implemented

Webhooks

Stripe webhook processing, signature verification, idempotency, and replay visibility.

research · implemented

About Trinity

Project overview for Trinity as a Hermes-first autonomous acquisition platform.

research · implemented

Architecture

Layered system architecture for Phoenix, Hermes, Jido, NVIDIA, ToolRouter, Stripe, Postgres, and Oban.

research · implemented

Data Flow

End-to-end demo flow from chat through Jido policy, approval, execution, and proof.

research · implemented

Hermes Integration

How Trinity uses hosted Hermes for agent work while Phoenix, policy, and ToolRouter keep authority.

research · implemented

Jido Policy Firewall

Specific Jido role: a narrow firewall against data poisoning and unsafe runtime payloads.

research · implemented

NVIDIA And Nemotron

Nemotron routes, safety review, ModelRouter, ModelDecision proof, and fail-closed model behavior.

research · implemented

Security And Governance

Approvals, redaction, ToolRouter, quarantine, credential boundaries, and audit proof.

runbooks · implemented

Account setup and release smoke

Owner-facing setup sequence for account, team, integrations, safety, audit, and danger-zone controls.

runbooks · implemented

Provider readiness

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

security · implemented

Live action gates

Approval, policy, and sandbox boundaries for live sends, live spend, and high-risk operations.

security · implemented

Secrets redaction

How Trinity keeps secrets out of logs, LiveView assigns, model context, and public docs.

ui · implemented

Trinity runtime UI

Native Trinity visual language for dense autonomous revenue operations.