04 of 14
Heartbeat
Prove the AI. At every output.
What it does
Heartbeat signs every output of one AI deployment. When the AI behaves correctly, the pulse is steady. When it drifts, the pulse changes, the receipts show it, the ledger keeps the record.
The proof is yours, produced locally, with no outbound call required. The evidence is the byproduct of running the AI, not a report assembled afterward.
Heartbeat creates a signed record of governed AI activity over time. The resulting evidence can support monitoring, audit and review requirements without requiring the underlying work to be sent to Regulayer™.
Heartbeat does not determine whether the system was legally compliant or whether an individual decision was correct. It preserves evidence that an authorised reviewer can evaluate.
What it covers
In practice
Move money
The payments agent is paying approved invoice 7782, $42,500, under the authority of Dana Whitfield, Finance Director, and that authority stays live only while a fresh pulse arrives. The pulse goes quiet, and every action stops. Authority could not be confirmed. No payment ran. The stop is written to the record as it happens.
Why it matters
Regulayer™ supplies the evidence. Your auditor, regulator or court makes the determination. Steady when it behaves. Provable when it drifts.
The pulse
A doctor takes the pulse before reading the chart.
Heartbeat is that, for AI. Every governed output is a beat: a signed receipt.
A consistent record shows that the monitored state remained within the conditions being recorded. A change in the record shows when the monitored state moved outside those conditions.
How the proof works
Three steps, one architecture.
Proof you can hold, made where the data lives, sent nowhere.
- Govern at the moment of output. It deploys inside your environment, bound to your license. Every AI output passes through it, and the decision to allow, refuse, hold, or escalate is made on local computation alone.
- Issue the receipt as a byproduct. Each governed event produces a signed receipt. No outbound call is made, and nothing leaves.
- Hand the proof to whoever asks. Export the bundle for your auditor, counsel, or regulator. You never call us, and we never see your data.
The pulse and the memory
The pulse, and the memory.
Heartbeat is the pulse of one AI surface: outputs signed as they are written, beat by beat.
The Witness is the whole estate’s memory: every moment across every tool, with the human decision sealed beside it.
Clean answers
What counts as one AI surface?
One stable AI deployment with one identifier: a legal-AI deployment, a productivity-suite AI tenant, an enterprise model endpoint, an internal RAG, a customer-facing chatbot, a drug-discovery assistant. Heartbeat binds to that one deployment and signs every governed event from it.
What happens if the AI drifts?
The signed record shows it, contemporaneously. Your team, your auditor, your counsel, or your regulator interpret it. The point is that the evidence is there, signed and verifiable, before anyone asks.
Does it phone home?
No. It runs entirely on your infrastructure. No telemetry, no analytics, no remote update. Block all outbound traffic at your firewall and it still works.
What happens if my license expires?
It keeps running. New outputs stop being covered by the Heartbeat Attested mark, but every receipt issued before expiry remains valid. A lapse creates a gap going forward, never backward.
Is this a compliance certification?
No, and that distinction protects you. We are infrastructure. You generate the signed evidence, you and your auditor interpret it, you and your regulator settle it. You hold the keys. You hold the evidence.