Limits are content

There is a difference between a limit that exists and a limit that is presented, and it is a design problem before it is an ethical one. Nearly every organization that overclaims has the accurate version written down somewhere. It is in the risk register, the caveats paragraph, the asterisk at the bottom of the page in the size the layout could spare. The disclosure is real. It is also, in the only sense that matters, absent, because the reader who needed it has already formed their belief four hundred pixels higher up.

Two systems inside our own estate arrived at the same sentence from opposite ends of the building. One is a readiness protocol in the atelier, machinery that turns a claim about transformation into a packet somebody can review: it asks which mechanisms are claimed to support the change, requires source evidence and a confidence value for each, and then instructs renderers to show limits as first-class packet content rather than footnotes, with a readiness check that flags any packet carrying no recorded limit before it goes to external review. The other is a brand document for one of our sites, written by people who have never opened that file, which states as a strategic principle that honesty is the brand and that disclosures are designed content rather than fine print. One is a validator and one is positioning. They converge because the underlying fact does not care which department noticed it.

The mechanism is that a limit given its own slot in the template has to be filled or leave a visible hole, which moves the honesty of a document from a property of whoever wrote it to a property of the form everyone writes in. This is why the fix is structural rather than exhortative. Telling authors to be forthcoming produces forthcoming authors on their good days. Giving the limits a named section, a position in the layout, and a check that fails when the section is empty produces the same result on the bad days, from the tired author, under the deadline, in the quarter where the number needs to look better than it is.

The field has already built the canonical form of this. Model cards, proposed by Margaret Mitchell and colleagues in 2019, make intended uses and out-of-scope uses a required section of a model’s public documentation rather than a caveat appended after the metrics. The move looks almost trivially small. Its consequence is that a model card with the out-of-scope section missing reads as incomplete rather than as clean, and a document that reads as incomplete gets finished, while a document that reads as clean because the missing part was never allocated any space gets shipped.

None of this asks anyone to lead with their weaknesses, which would be its own kind of dishonesty and a worse read. It asks that the boundary of a claim travel at the same weight as the claim, in the same typeface, inside the same frame, so a reader takes both away or neither. That is a layout decision, a schema decision, and a validator decision long before it is a question of character. Build the slot and the honesty stops depending on who is holding the pen, which is the only version of it that survives the organization growing past the people who founded it.