Project-first workflow
How operators start in Projects while account, search, notifications, and docs stay global and permission-gated.
Projects are the primary production workspace for acquisition goals, CRM work, messages, approvals, runs, proof ledger activity, and operator decisions.
Account remains global: Personal Account, Team/Members and roles, Settings with safety caps and approval rules, and Integrations/APIs with connection status are managed outside any single project and remain permission-gated.
Header search returns tenant-scoped global or project-scoped results for projects, contacts, companies, messages, approvals, activity, and docs without rendering secrets. notifications surface pending approvals, failed jobs, provider degradation, replies, spend, and revenue events from scoped read models.
The prominent Docs link stays available in the persistent navigation so operators can verify project-first workflow, live-action gates, and provider readiness without leaving the workspace context.
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
lib/autonomous_agency/agency.exlib/autonomous_agency/search.exlib/autonomous_agency/notifications.exlib/autonomous_agency_web/components/layouts.ex