What Is Legatus

Legatus is a LinkedIn sales automation platform built for founders, executives, and sales operators who refuse to spend their hours doing the work a machine can do. It deploys AI agents that hunt leads, send personalized connection requests, execute multi-step outreach sequences, and route hot replies directly to you.

Unlike tools that blast and ban, Legatus operates under ICA™ — Institutional Control Architecture, a seven-layer governance framework that enforces traceability, containment, rate limiting, and reversibility on every action your agents take. Every message is logged. Every decision is hashed. Every sequence is auditable.

You set the target. Legatus runs the hunt.

Accessing the Dashboard

The Legatus operations dashboard is available at /dashboard on your deployment URL. It is password-protected and not indexed by search engines.

1. 1Navigate to your Legatus URL and click Dashboard or go directly to /dashboard
2. 2Enter your operator password (set via the LEGATUS_PASSWORD environment variable)
3. 3The session token is stored in your browser. You remain logged in for 90 days.

Dashboard Tabs

Tab	Purpose
Overview	Real-time stats — active agents, leads by state, actions fired today, unrouted replies
Leads	Your full lead database. Add, view, filter by state, and track every lead through the pipeline
Sequences	All active, paused, and completed sequences with state, step progress, and last signal
Action Log	Complete chronological log of every action your agents have fired
Replies	Inbound LinkedIn replies from leads — routed here automatically via webhook
Agents	Your deployed LinkedIn agents — status, daily action count, kill switch control
ICA™	Full seven-layer governance command center — scores, locks, incidents, threats, circuit breakers

System Architecture

Legatus is a Node.js application deployed on Railway, backed by Supabase (PostgreSQL) and the Unipile API for LinkedIn access.

Runtime	Node.js on Railway — always-on, auto-restarting
Database	Supabase (PostgreSQL) — leads, sequences, actions, agents, ICA tables
LinkedIn API	Unipile — handles authentication, message delivery, profile lookup
Governance	ICA™ engine — runs inline on every agent action
Polling	Sequence engine polls every 30 seconds for ready actions
Webhooks	Unipile sends inbound LinkedIn events to /webhook/unipile

Managing Leads

A lead is anyone you want to reach on LinkedIn. Legatus tracks leads through a defined pipeline of states from first discovery to replied conversation.

Adding a Lead

1. 1Go to the Leads tab and click + Add Lead
2. 2Enter their full name, LinkedIn URL (required — must be a valid linkedin.com/in/ URL), and optionally title, company, and notes
3. 3Save. The lead enters with state new.

Lead States

Every lead moves through a defined state machine. The sequence engine advances states automatically based on actions taken.

State	Meaning	Next Action
new	Lead added, not yet contacted	Profile view or connection request
searched	Agent has viewed profile	Connection request
connected	Connection accepted	First direct message
touched	First message sent	Follow-up message
engaged	Multi-step sequence active	Subsequent sequence steps
replied	Lead has responded — sequence stops	Operator handles manually

Sequences

Sequences are the automation backbone of Legatus. A sequence assigns an agent to a lead and walks that lead through a multi-step outreach playbook automatically.

How Sequences Work

1. 1A sequence is created linking an agent to a lead with a defined playbook (step array)
2. 2The sequence engine polls every 30 seconds. When a step is due, it fires the action through the executor
3. 3Every action passes through the ICA™ gate before execution. Blocked actions pause the sequence
4. 4If the lead replies, the sequence halts automatically and the reply appears in the Replies tab
5. 5When all steps are completed without reply, the sequence moves to complete state

Sequence States

State	Meaning
running	Active — engine will fire next due step
paused	Halted — waiting for operator review or ICA clearance
replied	Lead responded — sequence stopped, ready for your follow-up
complete	All steps executed — lead marked cold if no reply

Agents

An agent represents a connected LinkedIn account. Each agent has its own daily action limit, status, and kill switch.

Agent Status

Status	Meaning
active	Agent is running and will execute sequence steps
trainee	Agent in learning mode — limited to profile views only
suspended	Agent is halted — no actions will fire

Kill Switch

Every agent has a kill switch toggle in the Agents tab. Engaging it instantly halts all sequence execution for that agent. The ICA™ L5 circuit breaker enforces this at the engine level — no actions can bypass it.

Reply Routing

When a lead replies to any message in your sequence, the Unipile webhook delivers that reply to Legatus in real time. The sequence is halted immediately and the reply appears in the Replies tab.

Handling a Reply

1. 1Check the Replies tab — unrouted replies are highlighted with a badge count in the nav
2. 2Read the reply in context. The lead's name, company, and sequence step are shown
3. 3Reply directly in LinkedIn. Legatus does not send replies on your behalf — that is your territory
4. 4Hot replies (booked calls, interested responses) should be moved to your CRM immediately

Action Log

Every action your agents fire is recorded in the Action Log with a timestamp, type, outcome, and the lead it was performed for. This log is immutable — it cannot be edited or deleted.

Action outcomes:

success	Action executed and confirmed by Unipile
failed	Action attempted but returned an error
blocked	Action stopped by ICA™ governance before execution
dry_run	System is in dry-run mode — no real actions taken

ICA™ — Institutional Control Architecture

ICA™ is the governance framework created by Shane Schreck and The Schreck Method™. It is a seven-layer certification standard for autonomous AI systems that enforces traceability, containment, decision auditability, and incident response.

Legatus is the world's first commercial application with ICA™ fully implemented end-to-end — from the database schema through the execution engine to the real-time dashboard.

Every single action your agents take passes through the ICA™ gate before execution. There is no path around it.

The Seven Layers

ICA™ Compliance Score

The ICA™ tab displays a real-time compliance score for your deployment. Each of the seven layers is scored 0–100. The overall score is a weighted average. ICA™ Certified status requires all seven layers to score ≥ 70.

≥ 80	Green — Compliant
50–79	Amber — Partial compliance, improvement needed
< 50	Red — Gap — remediation required before certification

Scores update each time you load the ICA™ tab and are stored historically for trend analysis.

Action Locks

Action locks are emergency controls that halt agent execution. There are three levels:

Lock Type	Scope	When to Use
Selective	Specific agent only	You suspect a single account is flagged or behaving abnormally
System	All agents, engine continues	Potential platform-wide issue or API outage — stop execution while investigating
GLOBAL	Everything — full halt	Account compromise, confirmed ban risk, or any situation requiring immediate total stop

Incidents

An incident is a formal record of something that went wrong or required investigation. Open an incident any time you engage an action lock, detect unusual behavior, or receive communication from LinkedIn about your account.

Incident Lifecycle

1. 1Open — Document what happened, set severity and type
2. 2Investigating — Review action logs, forensic trace, and ICA™ scores
3. 3Contained — Issue is bounded. Lock is in place. No further spread.
4. 4Resolved — Root cause identified. Remediation complete.
5. 5Closed — Post-incident review completed. Lesson documented.

Circuit Breakers

Circuit breakers are automatic triggers built into the ICA™ L5 layer. When a threshold is crossed, the breaker trips and halts the relevant execution path. You can reset a breaker manually from the ICA™ tab once the underlying issue is resolved.

Breaker	Threshold	Effect When Tripped
daily_action_limit	750 actions/agent/day	Agent halted until midnight reset
blackout_enforcement	11 PM – 6 AM	All actions refused during window
api_failure_threshold	3 consecutive Unipile failures	All sequences paused, auto-resets in 60 min
kill_switch	Operator toggle	Agent or global halt
account_suspension	LinkedIn account error state	Agent suspended until reconnected
sequence_runaway	Lead engaged > 30 days	Lead marked cold, flagged for operator review

Platform Limits

Daily actions/agent	750 (enforced by ICA™ L5)
Connection requests/day	100 (Unipile tool limit)
Direct messages/day	50 per agent
InMail/day	20 per agent
Profile views/day	750 per agent
Blackout window	11 PM – 6 AM (no actions)
Sequence steps	Up to 6 per lead
Poll interval	Every 30 seconds

Lead States Reference

new	Added to database, no contact made
searched	Profile viewed by agent
connected	Connection request accepted
touched	First message delivered
engaged	Sequence in progress (steps 2–6)
replied	Lead responded — operator takes over

Tool Registry Reference

Every action type in Legatus is registered in the ICA™ Tool Registry (Layer 4) with an authorization level and blast radius.

Tool	Auth Level	Daily Limit	Blast Radius
profile_view	Standard	750	Signals visit intent. No message sent.
connection_request	Standard	100	Initiates relationship. Cannot be unsent once accepted.
dm	Elevated	50	Direct communication. Content logged and traceable.
inmail	Elevated	20	Paid outreach. Uses InMail credit.
like	Standard	200	Public engagement. Visible to lead and their network.
comment	Elevated	30	Public statement. Human approval required.
follow	Standard	200	Visible follow. Adds to follower count.

Frequently Asked Questions

Will this get my LinkedIn account banned?

Legatus is designed with account safety as a primary constraint. The ICA™ L5 layer enforces daily limits, blackout windows, and circuit breakers that prevent the patterns LinkedIn flags. No tool eliminates risk entirely, but Legatus operates well within safe thresholds when limits are respected.

What happens when a lead replies?

The sequence halts immediately upon reply detection. The reply is routed to your Replies tab. The lead's state updates to replied. From there, you take over the conversation manually in LinkedIn.

Can I run multiple agents?

Yes. Each agent maps to one LinkedIn account. Your tier determines how many agents you can deploy simultaneously. Each agent has its own daily limit, kill switch, and ICA™ tool authorization record.

What is the ICA™ certification threshold?

All seven layers must score ≥ 70 out of 100 for the system to display ICA™ Certified status. Scores below 70 on any single layer prevent certification regardless of the overall average.

Can I pause a sequence?

Yes. Sequences can be paused manually from the Sequences tab. They can also be auto-paused by ICA™ circuit breakers. A paused sequence resumes when you manually set it back to running, or when the circuit breaker condition clears.

How do I add my LinkedIn account?

LinkedIn accounts are connected via Unipile. Log in to your Unipile dashboard, connect your LinkedIn account, copy the account ID, and add it as an agent in the Legatus Agents tab via your server environment variables or the agent creation API.

Who built this?

Legatus was built by Shane Schreck — US Army veteran, founder of The Schreck Method™, and the creator of ICA™ Institutional Control Architecture. He built it because manual outreach was stealing his hours. It now runs for others who refuse to waste theirs.