There is a real difference between a person using ChatGPT and a firm
operating a supervised AI Team. This is how the second one works, and why
the system around the agent is the part that matters.
Six rungs from a chat window to a managed operation.
Each rung is more useful than the last, and each one needs more
management. Most firms stop at rung one and wonder why nothing changed at
the level of the business.
Category ladderAI chat → Managed AgentOps
01AI ChatA person asks ChatGPT or Copilot for help.Useful for individuals. Disconnected from operations.
02AutomationFixed rules move data between tools.Good for predictable steps. Brittle around ambiguity.
03AI WorkflowAI is embedded in one business process.Helpful, but often one-off and project-based.
04AI AgentAI performs a defined role with tools.Useful, but narrow without supervision.
05AI TeamSpecialized agents coordinate around a function.Needs an operator, permissions, evals, monitoring.
06Managed AgentOpsOngoing management of supervised AI Teams.This is the LanternOps lane.
02
§ 2The build
One workflow, designed and operated end to end.
Start with the work, not the model
We map one high-friction workflow: where information enters, who touches it, which systems it crosses, and where it gets stuck.
Design the AI Team
Each agent gets a job description, tools, permissions, outputs, and a review cadence. Sensitive actions get an approval gate.
Connect to real systems
Secure connectors to email, documents, CRM, calendars, and billing, scoped to exactly what the team is allowed to touch.
Supervise and improve
We monitor the work, manage the review queue, tune the agents, and report on what changed, month after month.
03
§ 3The artifacts
Six artifacts we use to make supervision concrete.
Each one is a working document: how we design, explain, and operate every
AI Team, and how you stay in control of what it does.
Artifact 01Workflow map
Make hidden operational drag visible. Disconnected systems, manual handoffs, and the single managed path that runs through them.
Artifact 02Agent card
Drafting Assistant
Reports to Lead attorney
AI Team
Tools
Docs
Templates
Permissions
Read matter fileAllowed
Draft documentsDraft only
File with courtNever
Outputs
First-draft motion
Cite check list
Every agent is a managed role: job description, tools, permissions, outputs, performance, and a review cadence.
Artifact 03Permission map
Allowed
Controlled actions
Approval-gated
Never allowed
What the team can read, draft, do under approval, and never touch. Boundaries you can see.
Artifact 04Approval gate
Sensitive actions pause until a professional approves. AI prepares. Humans decide.
AI-prepared work waits for human review, then leaves as approved, edited, or escalated.
Artifact 06AgentOps dashboard
Managed AgentOpsexample dataOperating
Items handled1,284this month
Hours returned96to senior staff
Awaiting approval7in queue
Edit rate6%down from 11%
Edit rate trendlower is betterStuck points
Ambiguous matter type on 3 intakes
Billing connector token expired
New client template not yet mapped
Connector health
Email
CRM
Docs
Billing
Calendar
The operating view after launch: work handled, approvals waiting, edit rates, stuck points, and connector health. Proof that someone is operating the system.
§ 4The point
The value is the managed system around the agent.
Tools, permissions, review queues, logs, quality checks, escalation,
and ongoing improvement. That is the part that keeps an AI Team useful,
safe, and worth paying for.