connecting… chain — engine — last decision — praetor ↗ davidagents ↗

Praetor·The live wall·outbound compliance

The gate, open for inspection.

Every outbound call, text, and iMessage this platform makes — ours and our customers' — passes one deterministic compliance gate before any carrier is dialed. This wall is that gate's own ledger: live, aggregate, and public, because a compliance promise you can't watch is just a promise.

decisions gated
allow, review, or block — never silence
people protected
distinct contacts, counted through salted hashes
checks run
statute-backed rules consulted across every decision
The pipeline — watched live waiting for the next decision…

You are watching the actual production path, not a diagram of one. Each decision lands in a tamper-evident hash chain, mirrors to Postgres, streams through Debezium CDC into the lakehouse, rebuilds the gold analytics tables, and rings this page — typically within seconds. When the beacon fires, a decision just crossed the whole pipe.

Decisions, day by day

Every ruling the gate has made, stacked by outcome.

reaching for the lake…

The clock the law runs on

Federal law closes telemarketing outside 8am–9pm local; twenty-one states go further. Decisions by hour, on your clock — the shaded arc is the federal quiet window.

reaching for the lake…

Which rules actually fire

Not which rules exist — which ones ruled. Each is a statute or a survival doctrine the gate consulted and acted on.

reaching for the lake…

Posture, honestly

How the gate is running right now — including the number most dashboards would hide.

reaching for the lake…

traffic by channel

Why we publish enforce-share: a best-effort gate that blocked nothing is not the same as a clean record. Enforce-mode decisions are the ones where the gate held final authority — so we show you exactly how much of the traffic runs that hot.

The ledger, live

The most recent rulings, exactly as chained — each record carries the hash of the one before it, so the sequence below is cryptographically welded. No numbers, no names, no tenants: the wall sees outcomes, never people.

reaching for the lake…

Integrity vs. queryability

The hash chain is the compliance record — append-only, tamper-evident, replayable for a regulator. The lakehouse is the same decisions made queryable: Postgres → Debezium → bronze → silver → gold. The chain proves; the lake explains. Neither pretends to be the other.

Aggregate by design

No phone numbers, no message content, no customer names reach this page — contacts are counted through salted one-way hashes that never leave the gate's own store. What you can watch all day here is the machine working, not the people it protects.

This page is the demo

Everything above is Cortex — the same governed lakehouse every DavidAgents deployment gets. Real-time CDC, medallion layers, gold products, and a doorbell that rings a public webpage seconds after a database row lands. See the product →