{
  "id": "integration_gateway",
  "label": "Integration Gateway Canonical",
  "phase": "phase-09",
  "category": "operational_flows",
  "status": "ACTIVE_DH_MIRROR",
  "purpose": "Govern external system communication through controlled integration boundaries.",
  "function": "Route calls through connector identity, permission, payload validation, response capture and failure classification.",
  "technology_requirements": [
    {
      "technology": "Integration Gateway",
      "required_for": "Govern external system communication through controlled integration boundaries.",
      "required_by_phase": "phase-09",
      "required_by_category": "integration_gateway",
      "required_by_buckets": [
        "Prerequisites",
        "Installation",
        "Configuration",
        "Validation",
        "Observable Evidence",
        "Failure Modes & Recovery",
        "Completion & Promotion"
      ],
      "expected_version": "MISSING until Integration Gateway is implemented and validated in the future Execution & Monitoring Panel",
      "validation_command": "MISSING until integration_gateway can prove scope, evidence, execution state and promotion decision",
      "evidence_path": "/home/yeff/public_html/devon/canon/execution/state/dh_sources/integration_gateway.json",
      "status_source": "Documentation Hub + future Execution & Monitoring Panel",
      "blocking_if_missing": true,
      "failure_impact": "External connectivity expands DEVON-DEV only when the boundary is explicit. Without a gateway contract, every integration becomes a side door for unknown payloads, silent failures and uncontrolled authority. This category keeps outside systems from becoming hidden operators."
    }
  ],
  "depends_on": [
    "api_connector_registry",
    "security_governance",
    "rbac_permissions"
  ],
  "used_by": [
    "webhook_handler",
    "job_queue_task_runner",
    "external_knowledge_access"
  ],
  "overview": {
    "summary": "Integration Gateway Canonical owns the border where DEVON-DEV exchanges information or commands with external systems. It is the point where convenience can become exposure if connector identity and payload discipline are not enforced.",
    "function": "FUNCTION: Control outbound and inbound integration flow through connector identity, credential scope, payload schema, rate limit, response capture, retry policy and failure classification.",
    "system_position": "API Connector Registry defines what may be called. Webhook Handler governs inbound triggers. Security Canon decides what data and credentials can cross the boundary. Integration Gateway is where those rules become runtime routing.",
    "failure_impact": "External connectivity expands DEVON-DEV only when the boundary is explicit. Without a gateway contract, every integration becomes a side door for unknown payloads, silent failures and uncontrolled authority. This category keeps outside systems from becoming hidden operators."
  },
  "failure_impact": "External connectivity expands DEVON-DEV only when the boundary is explicit. Without a gateway contract, every integration becomes a side door for unknown payloads, silent failures and uncontrolled authority. This category keeps outside systems from becoming hidden operators."
}