How an automation is built
Watch an automation built to a fixed standard — or watch a check refuse to build it.
This is the real build, running in your browser. Change the brief below and the whole automation is rebuilt instantly: requirements are re-checked, every check re-decides, and the evidence chain is rebuilt. Nothing here is a recording.
The brief
How it is built
Rough asks → a coverage-checked requirement set
All required areas are covered or safely defaulted; the brief can move on to Design.
Requirements → fixed-version steps, then human sign-off
Approved by "Compliance Lead" on 2026-02-04; design covers all confirmed compliance requirements.
Run the fixed-version steps and assemble the automation
Every fixed-version step ran and the automation was assembled.
Verify the built automation before it goes live
Built automation passed final verification; cleared to deploy.
Decision and audit log · operator docs · training brief
Delivered. The record behind every decision, and the two documents the working session with your team is built on.
Delivered
Every check passed. The automation was built from fixed-version steps and handed over with the evidence behind each decision.
Discovery — coverage map
Not a vanity count of how many requirements were generated. What matters is what is covered and — louder — what is not.
12
Confirmed
backed by a client ask
0
Inferred
safely defaulted
0
Unknown
gaps — never assumed safe
Design — the steps chosen
Design assembles 3 fixed-version steps covering: audience and consent, claims and disclosures, brand and tone.
Narrative kept inside the approved template
The rewrite step changed the copy, then the check step re-checked its output against the approved template. What is handed over carries the evidence that the rewrite stayed inside the approved bound — the record a black-box builder cannot hand over.
Draft in
Guaranteed returns, risk-free. Our new savings bond is built for long-term savers.
Delivered out
Our new savings bond is built for long-term savers. Capital at risk.
Verdict on the rewritten copy: Pass
Checked by step: Financial promotion claim check, v1.0.0
- · Removed non-compliant sentence: "Guaranteed returns, risk-free."
- · Appended required disclosure: "Capital at risk."
Evidence chain
Every step emits its own traceable record — the exact input, the decision, and why. This is the record an auditor is given.
- · Both recipients have a lawful basis for email.
- · Rewrite checked by Financial promotion claim check, v1.0.0: pass.
- · Approved claims: none.
- · Removed non-compliant sentence: "Guaranteed returns, risk-free."
- · Appended required disclosure: "Capital at risk."
- · All risk-carrying phrases were approved or absent; every required disclosure present.
Version record
Fixes the exact version of every step this run used, so the run is reproducible from this record alone — and so “which runs used this step?” is a query, not archaeology.
What your team receives
Operator docs
How to run it.
- · Provide the campaign payload: recipients, copy, approved claims, required disclosures.
- · Run the automation; it holds back non-compliant sends.
- · Retain the documentation pack it produces with the campaign record.
Training brief
How to keep the record intact.
- · Why an unconfirmed answer is never treated as safe: unconfirmed consent or claims are gaps, never safe defaults.
- · Why every rewrite is re-checked before it is used.