{
  "schema": "org-writing@v1",
  "slug": "the-proposer-cannot-ratify",
  "kg": {
    "id": "org:writing:the-proposer-cannot-ratify",
    "type": "brick",
    "graph": "/kg.json"
  },
  "title": "The proposer cannot ratify",
  "subtitle": "Self-approval is best prevented by a format in which the sentence cannot be written",
  "abstract": "How a claim format removes self-ratification from the language instead of forbidding it, and why promotion stays a human edit in a graph that agents are writing into. The canonical treatment of the proposer-authority split.",
  "kind": "brick",
  "topics": [
    "Machine judgment"
  ],
  "courseMemberships": [
    {
      "course": "org:courses:machine-decides",
      "topic": "Machine judgment",
      "wall": "org:walls:engineering",
      "position": 3,
      "total": 5
    }
  ],
  "publishedAt": "2026-08-03T00:00:00.000Z",
  "version": 1,
  "guidelinesVersion": 15,
  "brief": {
    "problem": {
      "text": "When the same actor may both propose a relationship and record it as accepted, the record stops being a review and becomes an echo, and the control that forbids this arrangement elsewhere is a rule a person can decide to break.",
      "claims": [
        "the person who initiates a transaction is not the person who approves it"
      ]
    },
    "mechanism": {
      "text": "Fixing the status field to a single permitted value and the promotion flag to a single permitted value removes the self-ratifying document from the format, so there is no ratified claim to reject and no override to find.",
      "claims": [
        "fixes status to the single permitted value proposed"
      ]
    },
    "move": {
      "text": "Give agents a proposal format that cannot express its own acceptance, and keep promotion as a separate human edit in a different file, reviewed like any other.",
      "claims": []
    }
  },
  "sources": [
    {
      "repo": "mnstry-atelier",
      "path": "contracts/atelier-claim.v1.schema.json"
    },
    {
      "repo": "mnstry-org",
      "path": "ONTOLOGY.md"
    }
  ],
  "canonicalPath": "/writing/the-proposer-cannot-ratify/",
  "body": "An agent reading across our corpus notices that two pieces belong together and wants to say so. The format it must use to say it is a small document with eight required fields, and three of them decide the whole governance. The status field permits exactly one value, proposed. The promotion flag permits exactly one value, false. The field naming who filed it is documented, in the schema itself, as the claim proposer and not the authority, which is the whole design in five words and the reason we call this *the proposer-authority split*.\n\nRead those three constants as a group and something quietly severe becomes visible. A document asserting that it has been accepted is not a claim we would reject. It is not a claim. It fails validation on its shape, the way a date of the thirty-second of a month fails, and it never reaches anyone with the standing to disagree with it. There is no ratified claim in the system to review, no permission to check, and no policy string for a persuasive request to talk its way past.\n\nThe mechanism is a constant standing where a rule would ordinarily stand, because pinning the status to one value and the promotion flag to one value removes from the format the sentence in which a proposer records its own proposal as accepted, and a sentence that cannot be written needs no rule against writing it. This is the same move the corpus argues for consent that fails the build, applied to authority rather than to permission, and it costs two lines of schema.\n\nWhat the format leaves out has to happen somewhere, and it happens in the open. Promotion means an operator opens the node the claim was about, writes the edge into that node's own relations, and deletes or archives the claim, which is an ordinary reviewed edit with a name attached to it. Our graph contract states the principle in the same words it uses for the editorial gates. Proposal is open, ratification is not. Agents file freely and constantly, and none of that filing moves anything, which is precisely what makes the filing safe to encourage.\n\nThe arrangement is old enough to have an accounting name. Segregation of duties, the internal control requiring that the person who initiates a transaction is not the person who approves it, is standard in every serious financial control framework, and it exists because the two roles collapse quietly and the collapse is invisible from inside the books. The cathedral builders had a version of it in stone. A mason's mark recorded who cut a block, which is a claim about provenance, and it never recorded that the block was fit to set. The lodge decided that, and the two marks were never the same mark.\n\nThe reason this matters more each month is arithmetic. Machine systems now read and relate faster than any reviewer can, and a graph that lets its readers write their own conclusions in becomes, within a few weeks, a structure whose shape is a summary of what its most prolific reader believed. Keeping the proposal cheap and the ratification human does not slow the reading down at all; it only refuses to let volume become authority. The cathedral gets its stones from everyone who can cut one, and someone still has to say where they go.",
  "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:the-proposer-cannot-ratify:r01",
        "author": "MNSTRY Atelier",
        "work": "atelier-claim@v1, the proposal-only relationship claim contract",
        "year": 2026,
        "relevance": "The primary artifact. Status and promotion are JSON Schema constants rather than validated enums, the provider field is documented as proposer and not authority, and the contract's own description states that a claim cannot mutate canonical front matter, graph relations, public exports, feeds, or runtime imports."
      },
      {
        "id": "org:references:the-proposer-cannot-ratify:r02",
        "author": "MNSTRY (this corpus)",
        "work": "ONTOLOGY.md, the claims lane",
        "year": 2026,
        "relevance": "The governance half. Agents never write kg.relations on published nodes; promotion is copying the edge into the subject's relations and deleting or archiving the claim, an operator edit reviewed like any other."
      },
      {
        "id": "org:references:the-proposer-cannot-ratify:r03",
        "author": "COSO and the internal-control tradition",
        "work": "Segregation of duties as a standard internal control (initiation separated from authorization and from recording)",
        "relevance": "The accounting name for the same arrangement, and the reason the brick treats self-approval as a known control failure rather than a novel machine risk."
      },
      {
        "id": "org:references:the-proposer-cannot-ratify:r04",
        "author": "Yaron Minsky (and the typed functional programming tradition)",
        "work": "'Make illegal states unrepresentable' (Effective ML and subsequent practice literature)",
        "relevance": "The design maxim the brick applies to authority. Cited here for lineage; the maxim's canonical treatment in this corpus belongs to 'Consent that fails CI'."
      }
    ],
    "claims": [
      {
        "id": "org:claims:the-proposer-cannot-ratify:c01",
        "claim": "The atelier-claim@v1 contract fixes status to the single permitted value proposed and the promoted flag to the single permitted value false, and documents the provider field as claim proposer rather than authority.",
        "basis": "The schema read directly on 2026-08-03; both fields are JSON Schema const declarations, and the provider description carries the proposer wording verbatim.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:the-proposer-cannot-ratify:c02",
        "claim": "A claim document asserting its own promotion fails schema validation on its shape rather than being rejected by a review step.",
        "basis": "Follows from the const declarations above: the document is invalid against the contract, so no valid instance of a self-ratified claim exists.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:the-proposer-cannot-ratify:c03",
        "claim": "In this corpus, agents never write editorial relations onto published nodes, and promotion of a proposed edge is an operator edit made in the subject node and reviewed like any other change.",
        "basis": "ONTOLOGY.md, the claims lane section, read directly.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:the-proposer-cannot-ratify:c04",
        "claim": "Segregation of duties, the internal control requiring that the person who initiates a transaction is not the person who approves it, is standard practice in financial control frameworks.",
        "basis": "Standard internal-control literature and audit practice; the principle is uncontroversial, the specific formulations vary by framework.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:the-proposer-cannot-ratify:c05",
        "claim": "Masons' marks recorded which mason cut a block, functioning as payment accounting and accountability, and did not record acceptance of the block.",
        "basis": "Restated from the cathedral essay's own treatment of masons' marks; the acceptance half is the brick's reading of what the mark does not do, offered as illustration rather than as an archaeological finding.",
        "confidence": "directional",
        "sources": []
      }
    ],
    "concepts": [
      {
        "id": "org:concepts:proposer-not-authority",
        "name": "Proposer not authority",
        "definition": "The separation between filing a claim and ratifying it, held by a format in which a proposal cannot express its own acceptance. The status and promotion fields carry a single permitted value each, so a self-ratified claim is not rejected on review, it is invalid on its shape. Proposal is open to any agent; promotion is a separate human edit made in the subject node and reviewed like any other change.",
        "provenance": "canonical"
      }
    ],
    "researchContext": "Sourced from the Atelier claim contract and this corpus's own graph\ncontract, a pairing chosen because the schema and the governance rule are\ntwo halves of one design and neither is legible alone. The schema is a new\nsource label for the corpus (mnstry-atelier).\n\nThe brick's contribution is reading the two schema constants as a\ngovernance decision rather than a validation detail, and the observation\nthat an unrepresentable sentence needs no policy, no permission check, and\noffers nothing for a persuasive request to argue with. The lineage to\n\"make illegal states unrepresentable\" is credited and not re-argued: that\nmaxim's canonical treatment in this corpus is \"Consent that fails CI\",\nwhich applies it to permission, where this brick applies it to authority.\n\nGrading note: the masons' marks entry is graded directional because the\nclaim the brick actually makes is about what the mark did not do, which is\nan argument from the mark's documented functions rather than a separate\nfinding. The payment-and-accountability half is verified and belongs to the\ncathedral essay's apparatus, which this file does not duplicate.\n\nBoundary with the parent essay: \"Cathedral of the mind\" argues that a\nstructure meant to outlast its builders needs provenance, preserved dissent,\nand governance that survives its founders. This brick takes the third of\nthose and shows one mechanical form it can hold when the contributors write\nfaster than the reviewers read."
  },
  "contract": "https://mnstry.org/contracts/org/org-writing.v1.schema.json",
  "releaseHash": "7205e5d3a704befd8a07a41139f5b987f10776ceba8e05ccf466c073584549c2",
  "versions": [
    {
      "version": 1,
      "cutAt": "2026-08-03",
      "note": "Initial publication, machine-decides wave",
      "visibility": "published",
      "path": "/writing/the-proposer-cannot-ratify/",
      "contentHash": "sha256:231ec91aff0fb369",
      "releaseHash": "7205e5d3a704befd8a07a41139f5b987f10776ceba8e05ccf466c073584549c2"
    }
  ]
}