--- title: "Reference architecture · intentic docs" description: "An entire company assembled from intentic sandboxes: one sandbox per role and team, connected to the services they share." url: "https://intentic.dev/docs/reference-architecture/" updated: "2026-09-15" --- Agent Orchestration # Reference architecture: a company on intentic Zoom out and the same shape repeats at every level: a co-piloted sandbox per role and per team, each connecting to a small set of shared services. It's a topology you assemble, not a template you click. ## The pattern One specialized agent is a sandbox with tools, system access, and curated context (the [autonomous-employee recipe](https://intentic.dev/docs/autonomous-employees/)). A whole company is that recipe applied org-wide: give **every role and every team its own co-piloted sandbox**, and connect them all to a **small set of shared services**: code, chat, docs, secrets. Nothing here is a new feature; it's the primitives you already have, wired together. intentic app one browser UI · every sandbox · watch and steer Human in the loop · how you supervise the fleet Agent Governance Sandbox Human-in-the-loop review Sandbox rules AI oversight Role sandboxes · one per function Operations Sandbox Strategy Products Finance summaries Legal constraints Priorities Governance Sandbox HR Legal Finance Contracts Payroll & approvals Customer & Market Sandbox Market analysis Promotion Content writing Sales Team sandboxes · one per team, per product, per customer Product Team A Sandbox Development Dev testing QA Security Product Team B Sandbox Development QA Per-customer Sandbox A private, dedicated sandbox per customer each sandbox connects explicitly · scoped via capabilities & members, never an ambient bus Shared services GitHub · code Discord · collaboration Outline · docs Infisical · secrets Tools & outputs the agents drive Email management Documents · Outline Data visualizations Infra visualization ## How it maps to shipping features - **Role & team sandboxes.** One sandbox per function or team: Operations, Governance, Customer & Market, each product team, each customer. A reviewed [sandbox definition](https://intentic.dev/docs/sandbox-definitions/) can stamp out their shared repo, connection and environment shape without copying credentials; each new owner completes the trust decisions locally. Automations wake them, and one run can fire the webhook that wakes the next, so work moves through specialized hands. - **Human in the loop.** Autonomy is co-piloted, so you drive and watch every sandbox from one browser. A dedicated Agent Governance sandbox carries the rules the others operate under and the restricted secrets they are granted. Supervision is a sandbox pointed at the rest, not a privileged control plane. - **Shared services.** A small set of services the fleet leans on: GitHub for code, Discord for collaboration, Outline for docs, Infisical for secrets. They are plain services the agents connect to through explicit capabilities, not a control plane the fleet provisions. Credentials stay per-box. - **Tools & outputs.** Email, documents (Outline), and dashboards are capabilities the agents operate; every credential stays inside the sandbox that uses it. Honest about the seams - **No ambient cross-sandbox access.** A sandbox reaches shared services and other sandboxes only through explicit capabilities and members, credentials staying per-box. The "shared services" band is a handful of connected services, not a shared filesystem or an ambient bus. - **Oversight and governance are patterns you build**, not built-in roles. And an agent "evaluating humans" is framing we avoid: these sandboxes *assist* HR, Legal, and Finance; a person stays accountable. - **Chaining** is composition of real primitives (one automation firing another's webhook), not a drag-and-drop graph builder. Start with one sandbox and one role. The org chart above isn't a switch you flip; it's what a company looks like once you've specialized enough agents and connected them to shared services, one primitive at a time. See [Quickstart](https://intentic.dev/docs/quickstart/) to bring the first one up. More in Agent Orchestration [Previous ← Autonomous employees](https://intentic.dev/docs/autonomous-employees/)