{
  "id": 15121669,
  "title": "Sign the Sentences, Not the PR: An Approval Ledger for Model-Drafted Doc Blocks",
  "url": "https://urgent.news/2026/10/17/sign-the-sentences-not-the-pr-an-approval-ledger-for-model-drafted",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-17T04:54:49.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/github_7727/sign-the-sentences-not-the-pr-an-approval-ledger-for-model-drafted-doc-blocks-4m3h"
  },
  "original_language": "en",
  "account": "Documentation reviews typically approve pull requests, not individual sentences. This issue can be addressed by assigning a unique hash to each human signature that approves a specific text block. The workflow involves creating a Python checker that runs in pre-commit and CI to verify whether a named human has signed the exact text of a block. The approval record lives in review history while the file is continuously updated, which can lead to signatures becoming disconnected from their original content. By linking both hash and approval records, you ensure that both the input content and human accountability are verifiable.\n\nBefore implementing any tooling, it is essential to define the ownership boundaries for each unit of content. Each block should be marked with an HTML comment pair, indicating the type of block (model or human) and the owner. Blocks marked as owner=human do not undergo the approval process, allowing for flexibility and explicit escape hatches. Blocks marked as owner=model require a signature, and any changes to these blocks invalidate the existing signature. The final drafting process should restrict modifications to only those blocks designated as owner=model, with no introduction of new numbers, dates, or versions.",
  "summary": "Most documentation reviews approve a pull request, not a sentence. That is the failure mode worth fixing first, because a single approval granted in October can silently keep covering paragraphs a model rewrote in December. The workflow below binds every human signature to a hash of the exact text it approved, so re-approval becomes a mechanical consequence of editing rather than a matter of…",
  "key_points": [
    "Assign unique hash to each human signature for specific text block approval.",
    "Link hash and approval records to ensure content and human accountability verifiability.",
    "Restrict modifications to owner=model blocks, no new numbers, dates, or versions."
  ],
  "editors_take": "Linking unique hashes to human signatures creates a verifiable audit trail that enforces accountability for machine-generated text and prevents unauthorized modifications to model-drafted documentation blocks.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}