Menu

Who Signs This Paragraph? A Doc Contract That Separates Model Drafting From Human Accountability
📰

Who Signs This Paragraph? A Doc Contract That Separates Model Drafting From Human Accountability

DEV Community: python·Avery Lin·9 days ago
#r9PsXJj2
Reading 0:00
15s threshold

The core problem with model-drafted documentation is not that the sentences are wrong, but that nobody can tell which sentences someone has actually vouched for. A redrawn section can be 95% accurate and still ship a changed rate limit, a dropped prerequisite, or a security claim that no human ever read. The workflow below fixes the accountability gap instead of the wording: it classifies every claim in a doc, allows the model to draft only the low-risk classes, and requires a named human signature on the rest before the build turns green.

The artifact is a claim contract: a small YAML ledger beside your docs plus a ~90-line Python checker. It runs in under a second, needs no API key, and produces the same pass/fail in a local shell, a pre-commit hook, or a background job. I present it as a template to adapt rather than a finished product; run it against your own repository before trusting any of the checks.

1.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.