Solutions
Enterprise problems are organizational. So are the answers.
No single agent ships a product, clears a trial, approves a loan, or runs a client portfolio alone. These blueprints show how teams of specialist agents — composed, governed, and observed on AgentGuide — take on work that used to need a department. They are patterns assembled from the shipping platform, not prebuilt products: your agents, your policies, your topology.
Software delivery
A software factory, staffed by agents.
From requirement to release as one governed flow: planning agents shape the work, managed coding agents build it, review agents push back, and nothing deploys without a human saying so.
amber = human decision point · dashed = parallel fan-out
- Coding agents, managed Codex and OpenCode run as ACP agents — pooled processes, resumable sessions, replayable transcripts, filesystem roots you define.
- Composition that ships today Supervisor and plan-execute topologies coordinate spec → code → review inside one governed, fully traced turn.
- The deploy gate Release is an interactive permission: it streams to an operator, resolves through the API, and times out to denial.
- Cost per stage Attributed usage events show what each role spends — down to cached and reasoning tokens — so you can put the expensive model only where it earns its keep.
Life sciences
Clinical trial review with a complete audit trail.
Regulated review work is exactly where agent systems usually fail: not on capability, but on evidence. On AgentGuide, every model call and tool invocation in the review chain is a durable, attributed record — and the final judgment stays with a human.
amber = human decision point
- Evidence by default Four families of attributed usage events plus nested interaction spans — who did what, with which data source, at what step.
- Least-privilege reviewers Each agent reaches only the MCP tools and model routes bound to it; an unbound tool is a hard error, not a quiet fallback.
- Human sign-off, enforced Approval is a gateway permission, not a UI convention — unanswered requests are denials.
- Data stays home Self-hosted, single binary; you choose the model endpoints — including local models via Ollama for the most sensitive material.
Financial services
Risk decisions your auditor can replay.
KYC, risk, fraud, and compliance agents each do one job well; the gateway makes their combined decision explainable. When someone asks "why was this approved?", the answer is a trace, not a shrug.
amber = human decision point · dashed = parallel fan-out
- Four-eyes by policy High-stakes actions require an interactive human approval with a fail-closed timeout — deny is always the default.
- Attribution for the regulator Every event carries the responsible agent; failures are classified as client, upstream, or internal — no ambiguity in the record.
- Contained blast radius Recursion-depth limits stop agent-calls-agent loops; per-agent concurrency caps and timeouts reject rather than queue.
- Keys per desk Each team or application gets its own virtual key — meter it, cap its exposure, revoke it in one call.
Professional services
A delivery back office for a company of one.
Independent consultants, developers, and one-person studios lose their week to project intake, meeting follow-ups, status reports, and client replies — necessary work that earns nothing. A team of role agents runs that operations layer, and nothing reaches a client until you hit send.
amber = human decision point · dashed = parallel fan-out
- A staff of roles, not headcount Planner, researcher, writer, and reviewer agents compose in a supervisor topology today — one governed turn from meeting notes to a send-ready draft. On development projects, Codex joins the same flow as a managed ACP agent.
- Your tools, least-privilege Email, documents, calendars, and repositories connect as MCP services; each agent reaches only the tools bound to it.
- Drafts by default Nothing goes out to a client without an interactive human approval — unanswered means undelivered.
- Knowledge that compounds Project FAQs, templates, and past reports settling into a reusable asset base — on the roadmap, via the artifact bus and shared memory.
Beyond the blueprints
The same pattern fits your industry.
Every blueprint above is the same shape: specialist agents, least-privilege resources, human gates at the decisions that matter, and a complete record underneath. It scales down as well as up: a company of one runs the same control plane as a bank. On the roadmap, artifact lineage and capability composition make these flows declarative — ask for the outcome, and the platform assembles the team.