Most teams that let a model draft documentation hand out permission per page or per section, which means every paragraph inherits the trust level of the easiest one on the page. That arrangement holds until a model writes a single sentence that promises timing, ordering, or compatibility inside an otherwise harmless tutorial. The problem is not tone or style: it is a promise that nobody owns, and it survives review because reviewers read prose instead of obligations.
This workflow moves the permission boundary down to the sentence and attaches a signatory to the small set of sentences that behave like contracts. Three artifacts carry it: a front-matter list of regions a model may draft, a registry of signed claims, and a gate script that fails a pull request when an unsigned or expired claim appears.…