The method is Arrangement Based Automation. The studio work, the tool and the rules all come out of it, which is what makes this a platform rather than two products in a trenchcoat.
What is different about this site
A content-managed site answers one question: what is published, and when? Everything in it serves that — the editor, the scheduler, the approval workflow. It stores and it renders, and it has no opinion about what the page says. A content system will publish a false claim exactly as cheerfully as a true one, on time, every time.
This site answers a different question: what is allowed to leave, and on what evidence? The unit is not the page, it is the claim. The check runs on the bytes about to ship rather than on anyone's intention about them, and the default is refusal.
A review step gets walked around by one person in a hurry — not maliciously, just at 11pm on the fourth revision with a client waiting. A gate cannot be walked around, because it never reads your intention. It reads the file.
Attention is the thing that runs out, and it runs out precisely when the stakes are highest. A mechanism does not get tired at the end of a long day.
Most stacks only have the first. One system answers when; the gate answers whether. Split them and "approved" stops being a rubber stamp with a timestamp on it.
A claim traces to an approved sentence or the build fails — nothing ships. That is not a policy somebody has to remember. It is the same kind of event as a syntax error.
Stated at its true scope: the build gate runs on every push and refuses rather than passes when it cannot check something. The clearance gate for marketing copy is designed and not yet built, and this page will say so until it is.
Two doors into the same method
A loudness and delivery analysis that runs in your browser and hands you the numbers, the tolerances, and the standard each one is measured against — ITU-R BS.1770-4 and EBU R128.
The production method behind it: settle the technical decisions before anyone plays, so nothing technical is competing for attention during the take.
The evidence
An architecture that refuses things is only worth anything if you can see what it refused.
Every claim this site makes, and the approved sentence it comes from. Nothing is paraphrased.
Withdrawn claims stay on the page they were withdrawn from, struck through, with the date and the reason.
The production score rests on declared heuristics, not calibration. It is described that way wherever it appears.