The spine · outbound compliance

Every call. Every text. Every decision, proven.

A deterministic compliance engine in front of every outbound contact the platform makes — 51-jurisdiction calling rules, a consent ledger, instant opt-out enforcement, and a tamper-evident audit trail. No LLM in the decision path: same input, same answer, every time.

In Rome the praetor published the edict that set what the republic would permit, then ruled by it. It belongs beside Michelangelo's David — the ideal made real, and the magistrate who guards its conduct.

Put a gate on my outreach See it running

The problem

Agents that reach out are agents that carry legal risk.

TCPA suits start at $500 per violation and carriers suspend first, ask later. Most platforms bolt compliance onto the campaign tool and hope nothing else sends. But the risk lives in everything else — the agent that texts a follow-up at 8:10am into California, the callback that fires on a Sunday in Alabama, the number that said STOP last month. So we built the gate we could not buy, put it at the carrier door where nothing can route around it, and turned it on for every line we sell.

Capabilities

The gate

One deterministic door for every outbound contact

Before any SMS or dial leaves the platform — agent-initiated or human-initiated — the sender asks the engine. It runs every check and returns allow, review, or block with the statute behind each ruling. Consumer STOPs are honored instantly on every line and suppress the recipient platform-wide: a hard block that nothing overrides, not even an allow-list.

● a suppressed number is refused before the carrier is ever called — re-proven on our live test wall

51 jurisdictions

State law is the rule, federal is just the floor

Twenty-one states enforce stricter calling windows than the federal 8–9; eight close Sundays or holidays; forty-one carry their own mini-TCPA statutes, most with a private right of action. The engine resolves the recipient's local clock and applies the tightest law — each rule citation-backed and adversarially machine-validated, with the contested ones held for counsel rather than silently allowed.

● 36 of 51 jurisdictions independently re-derived and confirmed

Consent & caps

The paper trail and the throttle, built in

A consent ledger with proof, source, expiry, and revocation; established-business-relationship windows applied exactly where the law honors them; per-number and per-campaign velocity caps over rolling windows; SHAFT content screening before a carrier ever sees a message. Your own business rules ride the same engine — as data, evaluated safely, never as code.

● quiet-hour sends reschedule themselves to the next legal minute

Evidence

Compliance you can hand to a regulator

A policy document says what you intend. A hash chain proves what you did. Every decision links to the one before it — alter any record and the chain visibly breaks. When someone asks for every contact decision on a number, that is one export, regulator-ready, not a discovery project.

● the audit chain verifies live from our portal, every day

iMessage

The only compliance engine for the blue bubble

iMessage has no carrier regulation — no 10DLC, no campaign vetting — and every vendor stops the sentence there. We finish it: Apple bans senders without appeal, and any "unregulated" send to a phone number can silently fall back to carrier SMS, where the $500-per-message statutes attach in full. So the engine evaluates every blue-bubble send at its worst-case channel — the complete 51-state text ruleset — layered with the platform-survival governance nobody else sells: per-line new-conversation velocity, fresh-number warm-up ramps, no-reply chains, cold-first-touch gating, blast fingerprints. A STOP on any text channel suppresses them all.

● a suppressed number is refused on iMessage before the provider is ever called — proven on the live wall

What's inside

The manifest.

01 Deterministic gate allow / review / block — no LLM in the path
02 51-state ruleset citation-backed, machine-validated
03 Opt-out enforcement STOP honored instantly, platform-wide
04 Consent ledger proof, basis, expiry, revocation
05 EBR windows purchase 18mo / inquiry 3mo, where honored
06 Velocity caps per-number, per-campaign, rolling windows
07 Content screening SHAFT + carrier-filter risk, pre-send
08 iMessage governance worst-case-channel gate + Apple survival rules
09 10DLC / STIR-SHAKEN campaign + attestation posture per number
10 CAN-SPAM · CASL · GDPR email + international headline regimes
11 Custom business rules your policy as data, safely evaluated
12 Hash-chained audit tamper-evident, regulator-ready export
13 Quiet-hour rescheduling blocked sends move to the legal minute

How it lands

Already on

Every AgentsFast plan ships with the gate live: opt-outs enforced, federal quiet hours applied, content screened. There is nothing to install — outbound simply cannot skip it.

Go enforcement-grade

Compliance Plus flips your business to enforce mode: the 51-state rules block instead of warn, the consent ledger and velocity caps come alive, and the evidence trail is yours to export. One flat $99/mo — your agent turns it on in chat.

Bring your counsel

On DavidAgents, Praetor runs inside your own instance with your counsel's rulesets layered onto ours — compliance isolation, data residency, and the same provable gate wherever your agents run.

Proof · the compliance framework

We show you where the law is unsettled.

Most compliance tools sell you a green checkmark and a confidence you can't audit. Ours is built the opposite way — every rule traced to primary law, adversarially attacked before we trust it, and honest about the exact places the ground is still moving.

01
Research the source
Every rule is traced to primary law — the eCFR text of 47 CFR 64.1200 and 16 CFR 310, the state statute itself, the FCC orders and the court opinions — never a vendor's summary of a summary.
02
Attack it
A second pass tries to REFUTE each rule: does the statute actually reach texts, or only voice? Is the citation the right subsection? Did a 2024–2026 amendment or ruling quietly change it?
03
Grade the certainty
What survives gets a tier — SETTLED (clear statute + cases), LIKELY (reaches it, thin authority), or CONTESTED (a genuine live split). The ruleset is flagged validated only when counsel-confirmed.
04
Gate by certainty
The engine acts on the grade: block on settled, review on likely, advise on contested. No LLM in the decision — same input, same ruling, every time, with the statute printed behind it.

The validation ledger — what's settled, and what isn't

51 US jurisdictions · state calling rules 42 counsel-validatedsettled

The 7 formerly-contested states (CA·IL·ME·MA·MS·NV·SD) resolved 2026-07settled

Federal TCPA / TSR — 6 of 7 rule blocks validatedsettled

Federal — autodialed wireless written consent heldcontested

⚖ Why the federal ruleset still says "pending sign-off"

In February 2026 the Fifth Circuit (Bradford v. Sovereign Pest Control), riding the Supreme Court's McLaughlin decision, held the FCC's prior-express-WRITTEN-consent rule for wireless marketing unenforceable in Texas, Louisiana and Mississippi. It's a live circuit split. So we keep the strict written-consent floor in the gate — but we refuse to stamp the federal ruleset "validated" while the law is genuinely contested. We'd rather show you the edge than hide it.

158 deterministic engine tests — compliance checks live on the wall — failing last run —

Certainty where the law is settled. Honesty where it isn't. For a deterministic gate that decides whether your message is legal to send, that distinction is the whole product.

See the live gate All the receipts

Put Praetor on your payroll.

Same platform we run our own company on. First line is a purchase — the second is a decision.

Put a gate on my outreach