doc-chg-autopilot

Purpose

Automated CHG pipeline. From a change request — a diff, an incident, a prompt, or an upstream artifact edit — it detects the change, classifies the level, drafts a complete CHG record, traces the cross-layer cascade, registers it, and prepares the entry gate for approval — for one change or a batch.

CHG is NOT a lifecycle layer in the BRD..IPLAN sense: no template chain, no readiness score. The pipeline closes on gate approval, not a numeric score. For team-mode dispatch purposes the CHG layer is addressed as 09_CHG (the layer-id slot occupied by the change-management overlay).