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 could be composed, governed, and observed on AgentGuide. They combine current runtime foundations with roadmap tasks, cross-agent workflows, artifacts, memory, and compliance controls. They are target architectures, not prebuilt products.
Software delivery
A software factory, staffed by agents.
The target flow runs from requirement to release: 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 boundary Builtin supervisor and plan-execute topologies coordinate inline roles today. Handing work to independent ACP Codex/OpenCode agents requires the cross-agent workflow roadmap.
- Approval building block Builtin MCP actions can suspend for interactive approval; ACP agent permission requests can also route to an operator and time out fail-closed.
- Token usage per stage Attributed events expose prompt, completion, cached, and reasoning tokens. Monetary costing and enforceable budgets remain roadmap work.
Life sciences
A blueprint for evidence-rich clinical review.
Regulated review work is exactly where agent systems usually fail: not on capability, but on evidence. AgentGuide's shipping event and trace foundation can capture gateway-routed model and tool activity; a compliance-grade, immutable audit ledger is a roadmap capability. Final judgment stays human.
amber = human decision point
- Operational evidence Four usage-event families plus interaction spans capture route, tool, model, latency, result, and agent attribution when ownership is unambiguous.
- Scoped builtin reviewers Builtin definitions enforce their selected model route and declared MCP tools; platform-wide capability policy is a later control-plane layer.
- Human sign-off building block Gated builtin MCP actions and ACP permission requests fail closed when unanswered.
- Data stays home Self-hosted, single binary; you choose the model endpoints — including local models via Ollama for the most sensitive material.
Financial services
A target architecture for traceable risk decisions.
KYC, risk, fraud, and compliance agents each do one job well; the gateway can make their combined decision explainable. Current traces cover routed interactions; replayable decision lineage and compliance audit remain part of the workflow and artifact roadmap.
amber = human decision point · dashed = parallel fan-out
- Four-eyes building block Selected tool actions can require interactive human approval with a fail-closed timeout.
- Operational attribution Agent-bound events carry the responsible agent when ownership is unambiguous; failures are classified as client, upstream, or internal.
- 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 — scope it to routes, expire or disable it, and revoke access centrally.
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 Inline planner, researcher, writer, and reviewer roles can compose in a builtin supervisor topology today. Codex runs as a managed ACP agent today; joining both runtimes in one durable flow requires the cross-agent workflow layer.
- Your tools, scoped for builtin roles Email, documents, calendars, and repositories can connect as MCP services; builtin roles receive only the tools declared in their definitions.
- 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 target shape: specialist agents, scoped resources, human gates at the decisions that matter, and correlated operational evidence underneath. It scales down as well as up. On the roadmap, durable audit, artifact lineage, and capability composition make these flows declarative — ask for the outcome, and the platform assembles the team.