The rules, enforced automatically.
Write the rule once. Preflight blocks on it before launch, Scan re-checks it on live assets, and every evaluation records the exact rule version that produced it.
Six fields. Every one of them shows up in the record.
A rule is not a paragraph in a PDF. It is a versioned object with an owner, and Preflight evaluates every change against it.
A capability the other modules consume, not another place to visit.
Visual identity, verbal identity, claims, legal and compliance, accessibility, and AI governance.
A blocking rule holds the launch. A warning proceeds and is recorded, so the exception is visible rather than invented.
Scoped, owned, tied to a rule version and time bound. An exception with no end date is a rule change, and Launch does not allow one.
The rule set tells you where it is failing: worst pass rate, never triggered, unowned, overdue for review.
Brand guidelines in a PDF get read once. Rules in the release path get applied every time.
One hit, followed through the product. Scan and Preflight consume the rule, Launches enforces the result, and the audit log keeps the evidence.
What teams ask before they write the first rule.
In Settings, under Brand rules. A Brand approver writes and publishes each rule, and every publish creates a new version.
Find out what is live and off-brand.
Start with a free scan: no account, no credentials, no call.