Trinity Docs

Architecture, runtime safety, provider integrations, data flow, and proof for Trinity's autonomous acquisition workspace.

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

Live operations platform

Agents that earn, spend, & operate with proof.

Trinity is a first-of-its-kind live production Elixir/Phoenix SaaS where a user can operate a full business system by talking to the agent while approvals, policy, and security controls stay inside the control plane.

Nous Hermes Agent handles task planning and skills, while NVIDIA routes work through NemoClaw safety posture, fast Nemotron 3 Ultra model calls, Nemotron review, and agent-skill intelligence.

Stripe turns approved intent into revenue, purchases, SaaS provisioning, and paid services so agents can earn, spend, fulfill, and run real operations at scale.

Trinity connects a buyer message to payment, run execution, Gmail drafts, deliverables, and audit evidence without hiding credentials, raw prompts, unsafe email content, or unapproved side effects.

For builders, it demonstrates a viable foundation for agent companies and enterprise accelerators: live operations, real money paths, sponsor-native integrations, and security controls that fail closed.

Runtime

Nous Hermes Agent

Intelligence

NVIDIA NemoClaw + Nemotron

Money movement

Stripe skills

Control plane

Elixir/Phoenix

Core guides

Trinity as a Hermes-first platform

Start with the operating model, then move through runtime, policy, model safety, revenue, governance, and proof. Each guide links to a concrete system boundary instead of a marketing claim.

Guides

8

Control

Policy gated

Proof

Ledger linked

Guide Role in system Operational proof Status
01
About Trinity

Overview · /docs/about

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

Defines product posture, operating loop, and shipped vs. planned boundaries.

Implemented
02
Architecture

Control plane · /docs/architecture

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

Maps Phoenix, Hermes, Jido, NVIDIA, ToolRouter, Stripe, Postgres, and Oban.

Implemented
03
Hermes Integration

Runtime · /docs/hermes

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

Explains what Hermes can plan and where Phoenix keeps authority.

Implemented
04
Jido Policy Firewall

Policy · /docs/jido

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

Documents the narrow policy path for poisoned or unsafe content.

Implemented
05
NVIDIA And Nemotron

Model safety · /docs/nvidia

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

Links Nemotron safety review to stored ModelDecision evidence.

Implemented
06
Stripe Revenue And Future Spend

Revenue · /docs/stripe

How Stripe powers Revenue Mode today and guarded spend/provisioning paths later.

Connects checkout, order, revenue event, deal, and future spend gates.

Implemented
07
Security And Governance

Governance · /docs/security-governance

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

Shows approval, redaction, quarantine, and ToolRouter controls.

Implemented
08
Data Flow

Proof flow · /docs/data-flow

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

Follows chat to policy, approval, execution, artifact, and ledger proof.

Implemented