LanternOpsField Guide · Responsible AIManaged AI Teams
LanternOps Book a diagnosis →
§ 0Responsible by design

Safety creates speed.

The risk is not that your firm misses AI. The risk is that AI enters your firm without an operating model. Every LanternOps AI Team works inside visible boundaries, with a human at every decision that matters.

01
§ 1The boundary

Boundaries you can see.

A permission map defines what each AI Team can read, the actions it can take, what needs approval, and what it can never do. The boundary is part of the design, not an afterthought.

Fig. 1 — The Permission MapPlate I
  • Allowed
  • Controlled actions
  • Approval-gated
  • Never allowed
Concentric zones, from an allowed inner core out to a never-allowed edge. What the team may read, draft, gate, and never touch is fixed before launch.
02
§ 2The decision

A human at every decision that matters.

AI-prepared work flows to an approval gate. A professional approves it, edits it, or escalates it. Judgment, advice, compliance, and client-facing output stay under human control.

Fig. 2 — The Approval GatePlate II
AI-prepared drafts Human approval Approved work Escalation
AI-prepared drafts reach a human checkpoint, then route to approved work or to an escalation. AI prepares. Humans decide.
§ 3The controls

Six things that keep supervised AI supervised.

Permissioned access

Every AI Team is scoped to exactly what it may read, draft, do under approval, and never touch. Nothing more.

Human approval gates

Sensitive and client-facing actions pause until a professional reviews and approves. AI prepares. Humans decide.

Reviewable outputs

Work moves through a review queue with pending, approved, edited, and exception states, not straight to a client.

Audit trail

What the team did, what it accessed, and who approved it is logged and reviewable.

Stuck-point monitoring

When the team is unsure, it escalates instead of guessing. Exceptions are surfaced, not buried.

Ongoing supervision

Prompts, connectors, and evals are maintained as your systems and staff change. Safety is operated, not assumed.

04
§ 4The careful partner

The questions a careful partner asks first.

Is this safe for a regulated firm?

The model is supervised by design. Sensitive actions are approval-gated, outputs are reviewable, data access is permissioned, and logs and exceptions are monitored. Professional judgment stays with your professionals.

Will it act without us knowing?

No. The team works inside defined permissions and routes anything sensitive to a human gate. You see the queue, the approvals, and the audit trail.

Can it run itself?

Not responsibly. Prompts change, systems change, vendors change, and exceptions appear. We operate the AI layer after launch, which is the entire point of Managed AgentOps.

Will it replace our people?

The starting point is reducing repetitive information work: copying, checking, chasing, drafting, summarizing, routing, and reporting. Your people move up to judgment and client service.

§ 5The first step

Adopt AI without losing
control of the firm.

You can move faster than your peers and stay disciplined about it. That is the entire promise. It's also the foundation of our AI governance consulting — governance you operate, not a policy on a shelf.