Tisser One · Governance
The contract, the gate, and the trail.
AI can draft everything. The reason nobody wants to put their name on the output is that there is usually no way to know what it was checked against. In Tisser there is — every time.
01 · The contract
Your rules, written down once
Tone of voice, product catalog, channel rules, claims you can and cannot make — as a machine-readable set of rules with page references. Your team can change it; every change is versioned.
02 · The gate
Nothing publishes without a named human
Every output waits in the queue until a named person on your team approves it. That is not configurable — not in One, not in Studio. A refusal names the rule it broke.
03 · The trail
Every step, logged with a timestamp
Draft, edit, check, approval, publication — who did what, when, against which rule. Exportable, so your audit does not depend on us.
What a refusal looks like
The rule does the arguing, not a person.
LinkedIn post — product launch, EN
Claim “the fastest platform on the market” — no source on file Brand contract · rule 4.2 — comparative claims · p. 11
Sanne de Vries, Brand Lead — one click, on her phone
Live. Five minutes, one human, full trail.
A refusal is not a wall: it names the rule and the page, so the fix is usually one sourced claim away.
Questions your legal and IT team will ask.
- Who can approve?
- Named roles that you assign. Approval rights live in the contract, so they are versioned and auditable like every other rule.
- Where does the data live?
- Hosted entirely in EU datacenters. Everything encrypted in transit and at rest. Read the security page.
- What if we leave?
- The environment transfers with the contract intact — no export, no rebuild. Your rules and your trail are yours.
- Does the gate slow us down?
- The gate is one click for the approver, on any device. What it replaces is the week of checking, chasing and redoing that came before it.
Bring your compliance team.
The fastest way to test the gate is to try to get something past it.