Launch an outbound campaign and landing page.
A founder submits one request. No specialist or production tool has acted.
- Why this route is active
- The request needs both a campaign and a landing page.
Products / Agent Infra
Self-serve for solo operatorsRun cross-department work with agents.
Give each specialist only the tools and write access it needs. The waitlist is for future access, not managed setup.
Follow one request through six states.
See who owns each step, why it was routed, what it can write, which artifact it creates, and where approval stops it.
What Legion supplies. What you configure.
Legion provides the starting system. You connect it to your company and control every sensitive choice.
Legion supplies
Templates, patterns, workflows, and validation for a first install.
Five baseline templatesChief of Staff, GTM, Content, Website, and Developer/CTO.
Permission patternsOne department and one Code Mode MCP connection per specialist.
Knowledge graph rulesOwner-write and peer-read boundaries for shared company context.
Starter workflowsCross-department handoffs with owners, reasons, artifacts, and approval receipts.
Installation validationA first-job test that checks routing, boundaries, artifacts, and the human gate.
You configure
Your environment stays yours. The kit does not include managed setup.
Tools and credentialsYou choose the services and keep credentials in your own host environment.
Company contextYou decide which facts and source material each specialist can read.
Grants and accessYou issue, narrow, and revoke each tool grant.
Production policiesYou define what can run, what must stop, and what needs review.
Final approvalsYou approve production actions. The baseline never takes that decision away.
Start with a defined role.
Each template states what the specialist owns, which tools it can use, what it can write, and how you test it.
Coordinate the work.
Assigns owners, records decisions, and returns one job record.
- Tool boundary
- Tasks, dates, company files, and approved messages
- Writes
- Priorities, owners, decisions, and handoff receipts
- Starter artifact
- Cross-department job brief
- Validation
- Every subtask has one owner and one approval state
Prepare the campaign.
Owns targeting, offer, sequence, launch readiness, and campaign records.
- Tools
- Research, CRM, enrichment, sending
- Writes
- GTM graph only
- Artifact
- Launch packet
- Check
- No send before approval
Source the claims.
Owns source material, claim provenance, drafts, and editorial decisions.
- Tools
- Sources, transcripts, CMS drafts
- Writes
- Content graph only
- Artifact
- Sourced copy brief
- Check
- Every claim cites a source
Build the page.
Owns pages, forms, tests, and the record of what changed.
- Tools
- Site, forms, tests, analytics
- Writes
- Website graph only
- Artifact
- Landing-page build
- Check
- Preview passes before publish
Handle technical work.
Owns code, technical design, releases, and the production boundary.
- Tools
- Code, cloud, logs, releases
- Writes
- Developer graph only
- Artifact
- Change and release plan
- Check
- Policy and rollback are explicit
What this page shows.
Representative material, not customer proof
The replay and template bundle were authored for the Agent Infra installation kit. Use them to review ownership, routing, write boundaries, artifacts, and approvals before connecting your environment.
No customer outcome, production run, security certification, or performance metric is claimed here. The campus illustration explains the model; it is not product evidence.
Set up and test one job.
Choose the first department boundary
Start with one small tool and context boundary.
Configure your environment
Add your tools, credentials, context, grants, policies, and approval rules.
Run the supplied first-job test
Check the owner, route reason, write boundary, artifact, and approval receipt at every handoff.
Expand only after validation
Add another department when the first boundary behaves as intended.
Architecture
First Mate is the supplied Chief of Staff template in this example. It assigns work to specialists. Each department has its own Code Mode MCP connection and can use only the tools you grant.
Security and permissions
Owner-write and peer-read are baseline patterns, not a security guarantee. Enforce permissions inside upstream handlers or the host request callback. Keep credentials out of generated code and tool results.
Setup responsibilities
Legion supplies templates, patterns, starter workflows, validation, and a first-job test. You perform the configuration and control production.
Common questions
Is this consulting? No. Agent Infra is a self-serve installation kit.
Do I get access now? No. The CTA joins the waitlist for early access.
Can agents write across departments? The baseline uses owner-write and peer-read. A peer asks the owner to make a change.
Join Agent Infra early access.
Join the waitlist for the self-serve kit. Access is not immediate, and managed setup is not included.
Join early access