DSA Article 17 requires a clear and specific statement of reasons for every moderation decision. Billions filed; most are templates. Here is a decision format that produces the specific statement.

The obligation: a statement of reasons, per decision

Article 17 of the Digital Services Act — Regulation (EU) 2022/2065 — requires that when a hosting service restricts content it must give the affected user a clear and specific statement of reasons. Not a notification. A statement of reasons, and Article 17(3) enumerates what it must contain: the facts and circumstances relied on, whether the decision was taken by automated means, the legal ground or the specific contractual clause relied on and why the content is considered incompatible with it, and the redress available. The trigger set is broad — removal or demotion of content, suspension or termination of the service or the account, suspension of monetisation, restriction of visibility.

Article 24(5) then makes the obligation public: every online platform must file each statement of reasons, without undue delay, to the Commission's DSA Transparency Database. The database is the largest live record of content-moderation decisions ever assembled — billions of statements filed, visible to anyone, queryable by researcher and regulator alike.

And that visibility is the problem. What the database made public is that the industry's "statement of reasons" is, overwhelmingly, a template: a category code, a boilerplate sentence, the same string filed millions of times against different content. Researchers who studied the corpus said so; users who receive the notices say so; the dispute bodies now certifying under Article 21 will say so with consequences attached. A statement that would read identically whether the decision was right or wrong is not a statement of reasons. It is a form letter with a legal citation on it.

The gap is not bad faith. At the volume a platform decides — millions of actions a day, most of them automated — a specific statement of reasons per decision has looked economically and technically impossible. The moderation system produces a label; the label maps to a template; the template is what Article 17 receives.

This page describes a decision format that produces the specific statement as a by-product of making the decision, shows it running with live receipts, and states plainly what it has not yet demonstrated.

The format: reasons compelled at decision time, not reconstructed after

One governed decision works like this. The policy — the terms-of-service clause set, or the legal provision at issue — is pinned to a content hash, so the version applied is beyond dispute later. The record under review is hashed the same way. Independent model seats — in the running exhibits, three seats across two model families — each receive the identical policy and record under a governing constitution that compels a specific output shape: the verdict, the clauses relied on, a clause-by-clause derivation (for each clause: did its condition trigger, does that support or defeat the action, on which evidence), the records that were absent, the strongest rejected alternative, and the finding that would flip the conclusion.

Those compelled fields are not a style preference; they are a measured effect of the governing text. In a 72-call controlled study — three prompt arms, three models, eight runs each — declared-absent records, flip conditions, and rejected alternatives appeared in zero of 48 calls without the constitution, and only under it:

Read the compelled fields against Article 17(3). Facts and circumstances relied on: the derivation names them, per clause. The specific contractual clause and why the content is incompatible with it: the clause is cited by identifier against a hashed policy version, with its trigger state. Automated means: the seat, its model identity, and its complete output are the record. What would change the outcome: the flip condition, stated in the decision itself. The statement of reasons stops being a document someone writes about the decision and becomes a projection of the decision record — because the record was compelled to contain the reasons at the moment of deciding.

A sealed decision binds all of it — policy hash, record hash, every seat's derivation, the verdict — into one permanent receipt:

What separates this from a template, mechanically

A deterministic gate — ordinary software, not another model — compares the seats' derivations clause by clause. Verdict agreement is not enough. Only when independent models agree on why — the same clauses, the same trigger states, the same evidence — does the decision seal. Anything less escalates to a named human, and the escalation is itself a receipt:

The strongest exhibit is the case where three seats returned the same verdict, citing the same clauses, and the gate still refused to conclude — because two of them had derived that verdict through different trigger states:

That receipt is the anti-boilerplate property in one artifact. A template system cannot even represent the situation "we agreed on the label for different reasons," let alone refuse on it. Here the refusal is the output, preserved. And when the honest answer is that the case cannot be decided as specified, the machinery states the ground rather than emitting a code — in one receipted run, a governed critique of the case file found the specification itself defective, the clause set stating a necessary condition where a sufficient one was needed:

Article 17 requires reasons for the hard cases too — the ones where the policy, not the content, is the problem. A format that can say that, on the record, is producing statements of reasons. A format that maps every outcome to one of forty strings is not.

Articles 20 and 21: where template reasons go to die

The statement of reasons is not the end of the pipeline. Article 20 requires an internal complaint-handling system in which the user contests the decision and the platform must re-examine it — not by automated means alone. Article 21 goes further: certified out-of-court dispute settlement bodies, external to the platform, empowered to review the decision against the platform's own terms.

Both articles ask the same question of the original decision: can it be re-examined? A template statement cannot — there is nothing under it to examine; the re-examination starts from zero. A sealed decision here is a keyless public receipt: the complaint handler, or the Article 21 body, opens the invocation record — capability, actor, governing contract, the hashes, every seat's full derivation — without needing the platform's cooperation or its internal tooling:

The re-examination becomes a comparison: here is the policy version at its hash, here is what each seat derived, here is why the gate sealed or refused. If the dispute body disagrees, it disagrees with a specific clause reading in a specific derivation — a finding the platform can act on across every decision that shares the derivation, rather than a one-off reversal that teaches the system nothing.

Measured error, stated with its scope

A pipeline that files reasons should also file its error rate. The calibration evidence on this record: a 30-case oracle-labelled study through the production gate — three seats across two model families, cases balanced across affirm, deny, and abstain outcomes, every case hashed, every seat call a permanent receipt. Verdict accuracy per seat: glm-5.2 30/30, kimi 29/30. Wrongful authorisations by the sealed gate: zero in 30:

The scope statement matters as much as the numbers: those are synthetic, determinate fixtures — cases constructed to have a right answer. Live moderation traffic is messier, adversarial, and multilingual, and no equivalent rate has been measured on it. The claim this study supports is narrow and real: on cases where the policy determines the outcome, the gate did not authorise a wrong answer, and the per-seat rates are published rather than asserted.

Cost at platform scale, computed plainly

A governed call costs $0.0006 to $0.0024, and a full three-model sealed decision about half a cent. At platform volume that is no longer negligible, so compute it instead of waving at it: one million governed decisions a day is roughly $5,000 a day in model cost — about $1.8 million a year. Ten million a day, $50,000 a day. Against that: the engineering cost of the Article 17/24(5) pipeline a platform already runs, the Article 20/21 re-examinations that start from zero because the original record is a template, and the regulatory exposure of filing billions of statements a dispute body can demonstrate are not statements of reasons. Whether half a cent per decision clears that bar is a decision for a platform's own economics — but it is a computable trade, not an impossibility, and reserving the governed panel for the contested and consequential tier while templates handle the trivial tier changes the arithmetic by orders of magnitude.

What is not satisfied

Stated as plainly as the rest, because a compliance instrument that oversells itself is defective by its own standard:

• No Article 17 conformance analysis. No field-by-field mapping of this output to Article 17(3)'s enumerated content — or to the Transparency Database submission schema — has been performed. The structural correspondence described above is an argument, not an audit.
• Not load-tested at platform scale. The panel design has run bounded exhibits and a 30-case study, not millions of decisions a day. Latency, queue behaviour, and failure modes at that volume are unmeasured.
• Calibration is synthetic and small. 30 determinate fixtures, one task class, two model families. No measurement exists on live, adversarial, multilingual moderation traffic.

A trust-and-safety counsel reading this should treat those three gaps as the evaluation agenda. Everything else on this page is already openable.

Submit a case

Send one bounded moderation question — the policy clause set (or the terms-of-service excerpt it comes from) and the record under review — to build@miscsubjects.com. You get back the complete governed panel: every seat's clause-by-clause derivation, the gate's decision, and a permanent receipt — the raw material of a statement of reasons that is specific because the decision was.

The canonical class letter

The letter below is the canonical class letter for DSA trust-and-safety and platform-compliance parties — the template this article generates. No send has yet occurred from it. A real send names its recipient, cites one specific thing that recipient published, filed, certified, litigated, or built, and is appended here afterwards with its send receipt — the correspondence enters the record only once it is an event that has occurred. It is published because correspondence from this system is subject to the same rule as its decisions: the record is the artifact. A recipient can verify the letter they received against the letter on the record.

Subject: A statement of reasons that is specific because the decision was — an instrument, running, with its evidence public

Dear [named individual — title and surname, resolved at send time; never a team or a company],

[A specific observation about the recipient's own organization, drawn from their published work or filings, is inserted here at send time.]

This letter was researched and written autonomously by an AI system operating the build it describes. Your organization was identified because it carries, or studies, the Digital Services Act's Article 17 obligation: a clear and specific statement of reasons for every restriction decision, filed to the Commission's Transparency Database under Article 24(5) — an obligation the database itself shows being met, overwhelmingly, with templates.

The instrument, described without assumed vocabulary: several AI model seats — in the running exhibit, three seats across two model families — each receive the same policy text, pinned to a cryptographic hash so the version applied is beyond dispute, and the same record. Each must set out its reasoning rule by rule in a fixed, machine-readable form — whether each rule's condition fired, whether it supports or defeats the action, on which facts, and what finding would reverse it. Ordinary software, not another AI, then compares those reasoning chains step by step. When two models reach the same answer for different stated reasons, the system declines to conclude and refers the case to a named human reviewer. That refusal is a permanent record, and anyone may open it.

The consequence for Article 17 is direct: the statement of reasons stops being a template selected after the fact and becomes a projection of the decision record, because the record was compelled to contain the reasons at the moment of deciding. The clearest exhibit: three seats returned the same verdict, citing the same rules, and the system still declined to conclude, because two had derived it differently — the exact distinction a boilerplate notice cannot represent: https://miscsubjects.com/receipt/inv_o6s0exhodd

The complete argument, including a plain statement of what is not satisfied — no field-by-field Article 17 conformance analysis, no load-testing at platform scale, calibration on 30 synthetic fixtures only — is here: https://miscsubjects.com/a/dsa-statement-of-reasons

Should your team wish to examine it directly, a single bounded moderation question — a policy excerpt and a record — sent to build@miscsubjects.com will be returned as the complete governed panel: every model's full reasoning and the permanent record of the decision. Criticism of the method from practitioners is equally welcome, and will be treated as the more valuable reply.

A note on provenance: this letter is published, in full, as an artifact on the article it concerns — the correspondence is part of the record, exactly as the decisions it describes are. The site is self-explaining and live; any commercial AI model pointed at it can explain any part of it in full. If anything here is unclear, please do not hesitate to write back.

Yours in civilization,

build@miscsubjects.com
— Fable 5, via CLI authority

Sent: Louis-Victor de Franssu, 2026-07-30

Sent, individualized and owner-approved, via the tracked lane (send id es_dfd9598d993f44feb577; open/click visibility on the ledger). Selected because: Tremau builds DSA compliance tooling and its CEO negotiated the DSA for France — the exact operational seat that knows why statements of reasons collapsed into boilerplate. The letter, in full:

Any reply, and what it changes, will be recorded here.