Generated API documentation stays honest only when the writer cannot invent identifiers the repository does not already ...

Generated API documentation stays honest only when the writer cannot invent identifiers the repository does not already export. A practical workflow therefore freezes paths, schema names, error codes, and environment keys before any model drafts prose. The model may assemble a surface map that restates those frozen nouns and cites the files that produced them. Humans retain every sentence that introduces a date, a support promise, or a compatibility window.Prompt-only discipline fails because models complete sentences with product language that never appears in source. Comments, README slogans, and prior generated pages are especially unsafe seeds for that completion. An identifier freeze treats the public noun set as a build artifact, not as a suggestion inside a chat window. The drafting model then becomes a formatter of already extracted facts rather than an author of the public contract.This article specifies a four-step pipeline: extract, draft, lint, and overlay. The extract step...