Lifecycle-Based Authority Map Proposed to Keep AI Out of GA Support Docs

A framework published on DEV Community argues that AI models should be barred from editing generally available (GA) support documentation, as incorrect statements on such pages can become operationally binding commitments. The proposal classifies every documentation unit along two axes: feature lifecycle stage (experimental, preview, GA, or deprecated) and section type (derived reference, task procedure, migration narrative, or support commitment). Based on the intersection of these axes, a generator is assigned one of three authority levels — draft, propose, or hands-off — determining whether it can overwrite published content. The system relies on a product catalog, not the docs file tree, to assign ownership, since filenames often lag behind actual release states. A merge checker enforces the rules by rejecting any AI-authored changes to sections classified as human-owned.