Agent Infra for solo operators

Finish cross-department work alone.

Bounded specialists share the job without sharing every tool. Join early access for the self-serve baseline kit, not instant delivery.

Join kit early accessWatch one job ->
A pixel-art operations campus with a coordinator and five department workshops
Each specialist gets a lane. First Mate joins the result. You approve production.

One request. Six inspectable states.

Launch an outbound campaign and its landing page without giving one generalist every tool and write permission.

Representative installation-kit replay. This is a supplied workflow pattern, not a live customer run or measured result.

State 1 of 6: Request received

Owner: Founder

Launch an outbound campaign and landing page.

One request enters the roster. No specialist or production tool has acted yet.

Why this route is active
The founder asked for one joined campaign and page.
Read/write boundary
Reads company brief. Writes request record.
Artifact or receipt
campaign-and-page.request
Human approval
Required before any production action.
Owner: First Mate (supplied Chief of Staff template)

Name owners before opening tools.

First Mate is the supplied Chief of Staff template in this representative replay. It separates the joined outcome into bounded GTM, Content, and Website contributions.

Why this route is active
The job crosses three department boundaries.
Read/write boundary
Reads request. Writes owners and handoff receipt.
Artifact or receipt
owned-job-brief.md
Human approval
Pending. Production remains blocked.
Owner: GTM

Prepare the campaign, not the page.

GTM defines the audience, offer, sequence, and launch checks inside its own lane.

Why this route is active
GTM owns targeting and launch preparation.
Read/write boundary
Reads job brief. Writes GTM graph only.
Artifact or receipt
campaign-launch-packet.md
Human approval
Pending. Sending remains blocked.
Owner: Content

Source every concrete claim.

Content returns approved source material and copy guidance without rewriting GTM or Website records.

Why this route is active
The campaign and page need sourced claims.
Read/write boundary
Reads brief and sources. Writes Content graph only.
Artifact or receipt
sourced-copy-brief.md
Human approval
Pending. Production remains blocked.
Owner: Website

Build and test the page preview.

Website uses the approved GTM and Content inputs to create the landing-page artifact.

Why this route is active
Website owns the page artifact and preview checks.
Read/write boundary
Reads approved inputs. Writes Website graph only.
Artifact or receipt
landing-page-preview.html
Human approval
Pending. Publish and send remain blocked.
Owner: Founder

Record a representative test decision.

The roster returns the campaign packet, sourced copy, tested page, and a visible test decision point.

Why this route is active
Every required artifact is ready for one human test decision.
Read/write boundary
Reads joined packet. Writes representative test decision or redirect receipt.
Artifact or receipt
approval-receipt.json
Human approval
Representative test decision: approved. The customer-controlled send/publish action is separately configured and never called by this replay.
Inspect representative joined launch packet

Representative sample / no production action

joined-launch-packet.md

Job
Outbound campaign + landing page
Owners / route
First Mate (supplied Chief of Staff template) routes / GTM / Content / Website contribute
Ready inputs
Campaign packet / sourced copy brief / tested page preview
Production
The customer-controlled send/publish action is separately configured and never called by this replay.

approval-receipt.json

Decision
Representative test decision: approved
Approved by
Founder
Scope
Joined packet above
Result
Receipt recorded. The customer-controlled send/publish action is separately configured and never called by this replay.
Select any state or use arrow keys.

The installation kit draws the line.

Legion supplies a tested baseline. You connect it to your company and keep control of every sensitive choice.

Legion supplies

Reusable scaffolding for the first safe, inspectable install.

Five baseline templatesChief of Staff, GTM, Content, Website, and Developer/CTO.
Permission patternsOne department and one Code Mode MCP surface 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 from a mandate, not a blank prompt.

Each baseline template names what the specialist owns, what it may touch, what it writes, and how you validate it.

Chief of Staff

Route the company job.

Turns one founder request into owned work and returns a joined decision 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
GTM

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
Content

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
Website

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
Developer/CTO

Guard the system.

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

Proof starts with an inspectable boundary.

What we can show truthfully today

The replay and template bundle on this page are representative baseline material authored for the Agent Infra installation kit. They let you inspect the ownership, routing, write boundaries, artifacts, and approval gate 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.

Install, configure, then test one job.

Choose the first department boundary

Start with the smallest useful tool and knowledge surface.

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 representative replay. It routes work to bounded specialists. Each department gets its own Code Mode MCP surface and can call 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 baseline installation kit.

Do I get access now? No. The CTA joins early access through the existing waitlist.

Can agents write across departments? The baseline uses owner-write and peer-read. A peer asks the owner to make a change.

Build the roster. Keep the keys.

Join early access for the baseline self-serve installation kit. The waitlist does not provide immediate delivery or managed implementation.

Join kit early access