{
  "schema": "org-writing@v1",
  "slug": "limits-are-content",
  "kg": {
    "id": "org:writing:limits-are-content",
    "type": "brick",
    "graph": "/kg.json"
  },
  "title": "Limits are content",
  "subtitle": "A limit set in six-point grey has been disclosed and not communicated, and everyone involved knows the difference",
  "abstract": "The design difference between a limit that exists and a limit that is presented, and the template move that makes the second one structural. The canonical treatment of first-class limits.",
  "kind": "brick",
  "topics": [
    "Honest claims"
  ],
  "courseMemberships": [
    {
      "course": "org:courses:honest-claims",
      "topic": "Honest claims",
      "wall": "org:walls:ethics",
      "position": 5,
      "total": 6
    }
  ],
  "publishedAt": "2026-08-03T00:00:00.000Z",
  "version": 1,
  "guidelinesVersion": 15,
  "brief": {
    "problem": {
      "text": "Most systems that record their limits honestly still render them at the edge of the artifact, where the disclosure is technically present and functionally absent.",
      "claims": [
        "instructs renderers to show limits as first-class packet content rather than footnotes"
      ]
    },
    "mechanism": {
      "text": "A limit given its own slot in the template must be filled or leave a visible hole, which converts the honesty of a disclosure from a property of the author into a property of the form.",
      "claims": [
        "make intended uses and out-of-scope uses a required section"
      ]
    },
    "move": {
      "text": "Allocate the limits a designed position in the artifact and a check that fails when the position is empty, so a document cannot read as complete while the part that bounds it is missing.",
      "claims": []
    }
  },
  "sources": [
    {
      "repo": "mnstry-atelier",
      "path": "src/readiness-protocols/bundled-pack.mjs"
    },
    {
      "repo": "mnstry-website",
      "path": "PRODUCT.md"
    },
    {
      "repo": "mnstry-org",
      "path": "src/content/writing/the-owed-disclosure.md"
    }
  ],
  "canonicalPath": "/writing/limits-are-content/",
  "body": "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.\n\nTwo 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.\n\nThe 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.\n\nThe 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.\n\nNone 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.",
  "apparatus": {
    "note": "The human-facing essay is deliberately practical; this apparatus carries the full references, evidence-graded claims, article-local concepts, and research context behind it. Canonical concept definitions come from the concept registry.",
    "references": [
      {
        "id": "org:references:limits-are-content:r01",
        "author": "MNSTRY Atelier",
        "work": "Transformation map readiness protocol, bundled protocol pack (internal)",
        "year": 2026,
        "relevance": "The machinery half of the convergence: an output hint requiring limits to render as first-class packet content, and a readiness rule that flags a packet with no recorded limit before external review."
      },
      {
        "id": "org:references:limits-are-content:r02",
        "author": "MNSTRY",
        "work": "Product and brand direction for the mnstry.ai site (internal)",
        "year": 2026,
        "relevance": "The positioning half of the same convergence, written independently of the protocol pack: honesty as the brand, disclosures as designed content rather than fine print."
      },
      {
        "id": "org:references:limits-are-content:r03",
        "author": "Margaret Mitchell, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji and Timnit Gebru",
        "work": "Model Cards for Model Reporting (FAT* / ACM FAccT)",
        "year": 2019,
        "relevance": "The canonical public form of the template move: intended use and out-of-scope use as required sections, so a card missing them reads as incomplete rather than as clean."
      }
    ],
    "claims": [
      {
        "id": "org:claims:limits-are-content:c01",
        "claim": "Our transformation readiness protocol instructs renderers to show limits as first-class packet content rather than footnotes, and carries a readiness rule that flags a packet recording no explicit limit before external review.",
        "basis": "Internal: the bundled readiness protocol pack, whose transformation map declares a required limits array, a limits output hint, and a limits-present readiness rule at warning severity.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:limits-are-content:c02",
        "claim": "A brand document for one of our sites states as a strategic principle that honesty is the brand and that disclosures are designed content rather than fine print.",
        "basis": "Internal: the product and brand direction document for the mnstry.ai site, strategic principles section.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:limits-are-content:c03",
        "claim": "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.",
        "basis": "Mitchell et al., Model Cards for Model Reporting (2019), and the subsequent adoption of the format across major model releases.",
        "confidence": "verified",
        "sources": []
      }
    ],
    "concepts": [
      {
        "id": "org:concepts:first-class-limits",
        "name": "First-class limits",
        "definition": "Limits given a designed slot in the artifact rather than a footnote at its edge, so an author must fill the slot or leave a visible hole. The move relocates the honesty of a document from a property of whoever wrote it to a property of the form everyone writes in, which is the version that survives a tired author under a deadline.",
        "provenance": "canonical"
      }
    ],
    "researchContext": "Extracted from the honest-claims parent essay, taking the presentation half of\nits claim set. The model-card claim is restated verbatim from the parent's\napparatus and graded identically; the two internal claims are stated at\ngreater length here, since the convergence is the brick's evidence and needs\nboth halves described.\n\nThe convergence itself is the contribution. A validator in the atelier and a\nbrand document for a consumer site, written by different people who have not\nread each other's files, land on the same sentence about where a limit\nbelongs. That is offered as corroboration rather than as proof, and the\ngrading says so: each claim is verified as a statement about what our\ndocuments specify, not as a claim that the specification changes reader\nbehavior, which we have not measured. The readiness rule is recorded here at\nits real severity, a warning rather than a blocker, because overstating our\nown enforcement inside a brick about honest disclosure would be a\nself-refuting error.\n\nThe argument that structure beats exhortation, and the closing point that a\nbuilt slot is the only version of the honesty which survives the organization\noutgrowing its founders, are the brick's own. The surrounding protocol\nmaterial, including the export mappings, claim mappings, and the rest of the\nbundled pack, is internal machinery and none of it is used here."
  },
  "contract": "https://mnstry.org/contracts/org/org-writing.v1.schema.json",
  "releaseHash": "01061479ee8e9cec62d7837bdc155cf393e9ec1881aa232b0d58e3f02eecdf60",
  "versions": [
    {
      "version": 1,
      "cutAt": "2026-08-03",
      "note": "Initial publication, honest-claims wave",
      "visibility": "published",
      "path": "/writing/limits-are-content/",
      "contentHash": "sha256:a9d6d63dc266a719",
      "releaseHash": "01061479ee8e9cec62d7837bdc155cf393e9ec1881aa232b0d58e3f02eecdf60"
    }
  ]
}