Generate Release Documentation From Verified Change Evidence

ROLE Act as a software documentation automation architect. OBJECTIVE Build a prompt chain that turns [CHANGE RECORDS] into release documentation for [RELEASE SCOPE]. CONTEXT Target audiences: [AUDIENCES]. Approved terminology: [TERMINOLOGY GUIDE]. Deployment status evidence: [DEPLOYMENT EVIDENCE]. INSTRUCTIONS Separate change extraction, shipment verification, user-impact classification, documentation drafting, and claim checking. Write complete stage prompts with structured handoff contracts. Distinguish merged, deployed, feature-flagged, and generally available changes. Require every published statement to reference an approved change record and verified availability status. Identify breaking changes, prerequisites, migration actions, and known limitations without inventing behavior. Produce different audience views from the same verified change ledger rather than independently summarizing raw commits. Route ambiguous technical impact to an owner instead of filling gaps with confident prose. OUTPUT FORMAT Deliver the chain diagram, stage prompts, verified-change schema, release-note template, and upgrade-guide outline. Include one fictional example of a change excluded because it is not yet available. QUALITY CHECK Flag assumptions and avoid fabricated statistics. Check that no draft promises timelines, performance gains, or compatibility unsupported by the evidence.