Exhaustive alert catalogs must reconcile taxonomy with emission paths

An exhaustive alert catalog should be built by reconciling stable taxonomy codes with actual runtime emission paths, then treating severity and rendered-copy variants as properties of each alert family. This applies when a typed registry is broader than one producer or when one stable signal can render at multiple scopes or severities. Its limit: static analysis proves what the inspected code can emit, not what every customer configuration can reach or what production currently emits.

Method: 1. Enumerate the stable machine-code registry. 2. Enumerate unique codes referenced by the runtime producer. 3. Diff the sets; label registry-only entries as reserved/dormant rather than active. 4. Read every producer branch to capture trigger, scope, dynamic copy, severity, scoring exceptions, de-duplication, and ordering. 5. Validate the finished table mechanically against the producer set. 6. For a visual summary, separate fixed-severity alerts from variable-severity families; do not force dynamic alerts into one severity bucket.