concepts · implemented
Approvals
Human-in-the-loop gates for outreach, purchase, refund, and high-risk actions.
Search source-backed pages by route, module, provider, policy, or concept.
concepts · implemented
Human-in-the-loop gates for outreach, purchase, refund, and high-risk actions.
concepts · implemented
Append-only audit and financial proof across orders, revenue, spend, tools, models, and approvals.
concepts · implemented
Official NVIDIA/NIM-first model routing and sanitized ModelDecision evidence.
concepts · implemented
How operators start in Projects while account, search, notifications, and docs stay global and permission-gated.
concepts · implemented
How Trinity turns offers, acquisition runs, orders, approvals, revenue, and spend into auditable operations.
concepts · implemented
Policy-gated execution boundary for Stripe, Gmail, sandbox, and external tool actions.
getting-started · implemented
Production-grade autonomous acquisition and revenue operations framework.
getting-started · implemented
Clone, configure, run, and verify Trinity locally without leaking secrets.
reference · implemented
How Trinity stores companies, contacts, deals, activities, segments, meetings, and snapshot leads as source-of-truth records.
reference · implemented
How Trinity handles uploaded documents, quarantined source material, generated docs, graphs, previews, downloads, and proof links.
reference · partial
Safe environment variable names and configuration boundaries.
reference · implemented
How Trinity separates Gmail OAuth, mailbox readiness, aliases, draft creation, sends, replies, ingestion, and approvals.
reference · implemented
How Trinity represents provider readiness, credential slots, fallback posture, and secret-safe setup state.
reference · implemented
Public, protected, API, and webhook route map for the current Phoenix router.
reference · implemented
Why Trinity uses Elixir, BEAM, Phoenix LiveView, Ecto, Postgres, Oban, PubSub, Fly.io, and Tigris for agent operations.
reference · implemented
How Hermes, NVIDIA, Stripe, Gmail, Jido, HubSpot, Fly.io, Tigris, and fallback providers map into Trinity.
reference · implemented
Stripe webhook processing, signature verification, idempotency, and replay visibility.
research · implemented
Project overview for Trinity as a Hermes-first autonomous acquisition platform.
research · implemented
Layered system architecture for Phoenix, Hermes, Jido, NVIDIA, ToolRouter, Stripe, Postgres, and Oban.
research · implemented
End-to-end demo flow from chat through Jido policy, approval, execution, and proof.
research · implemented
How Trinity uses hosted Hermes for agent work while Phoenix, policy, and ToolRouter keep authority.
research · implemented
Specific Jido role: a narrow firewall against data poisoning and unsafe runtime payloads.
research · implemented
Nemotron routes, safety review, ModelRouter, ModelDecision proof, and fail-closed model behavior.
research · implemented
Approvals, redaction, ToolRouter, quarantine, credential boundaries, and audit proof.
research · implemented
How Stripe powers Revenue Mode today and guarded spend/provisioning paths later.
runbooks · implemented
Owner-facing setup sequence for account, team, integrations, safety, audit, and danger-zone controls.
runbooks · implemented
How operators verify Hermes, NVIDIA, Stripe, Gmail, webhook, and fallback readiness.
security · implemented
Approval, policy, and sandbox boundaries for live sends, live spend, and high-risk operations.
security · implemented
How Trinity keeps secrets out of logs, LiveView assigns, model context, and public docs.
ui · implemented
Native Trinity visual language for dense autonomous revenue operations.