{
  "id": "release_governance",
  "label": "Release Governance Canonical",
  "phase": "phase-09",
  "category": "delivery_layer",
  "status": "ACTIVE_DH_MIRROR",
  "purpose": "Govern release packaging, sequencing, approval and promotion rules.",
  "function": "Bind changes into a release scope with dependencies, exclusions, migration state, rollback conditions and promotion evidence.",
  "technology_requirements": [
    {
      "technology": "Release Governance Registry",
      "required_for": "Govern release packaging, sequencing, approval and promotion rules.",
      "required_by_phase": "phase-09",
      "required_by_category": "release_governance",
      "required_by_buckets": [
        "Prerequisites",
        "Installation",
        "Configuration",
        "Validation",
        "Observable Evidence",
        "Failure Modes & Recovery",
        "Completion & Promotion"
      ],
      "expected_version": "MISSING until Release Governance Registry is implemented and validated in the future Execution & Monitoring Panel",
      "validation_command": "MISSING until release_governance can prove scope, evidence, execution state and promotion decision",
      "evidence_path": "/home/yeff/public_html/devon/canon/execution/state/dh_sources/release_governance.json",
      "status_source": "Documentation Hub + future Execution & Monitoring Panel",
      "blocking_if_missing": true,
      "failure_impact": "Release risk is created by grouping decisions, not just by individual patches. This category prevents unrelated changes, hidden migrations and vague rollback scope from entering the same promotion package under the illusion of delivery progress."
    }
  ],
  "depends_on": [
    "patch_outcome_tracker",
    "test_validation_runner",
    "backup_rollback"
  ],
  "used_by": [
    "production_deployment_gate",
    "preview_engine",
    "disaster_recovery"
  ],
  "overview": {
    "summary": "Release Governance Canonical owns the packaging logic of delivery. It decides when a set of validated changes becomes a release and when it remains a pile of patches that should not travel together.",
    "function": "FUNCTION: Define release scope, included changes, excluded changes, dependency order, approval rule, migration linkage, rollback condition and promotion evidence.",
    "system_position": "Patch Outcome Tracker proves individual fixes. Test & Validation Runner proves behavior. Backup & Rollback defines recovery. Production Deployment Gate decides whether the release crosses into production-facing state.",
    "failure_impact": "Release risk is created by grouping decisions, not just by individual patches. This category prevents unrelated changes, hidden migrations and vague rollback scope from entering the same promotion package under the illusion of delivery progress."
  },
  "failure_impact": "Release risk is created by grouping decisions, not just by individual patches. This category prevents unrelated changes, hidden migrations and vague rollback scope from entering the same promotion package under the illusion of delivery progress."
}