{
  "id": "sap-cloud-alm-sre-incident-agent",
  "name": "SAP Cloud ALM SRE & Incident",
  "version": "0.1.0",
  "type": "agent",
  "provider": "sap",
  "harnesses": [
    "codex",
    "copilot",
    "claude-code",
    "cursor",
    "gemini",
    "kiro"
  ],
  "summary": "Reviews SAP Cloud ALM operations and monitoring configuration, SRE observability coverage across the managed SAP landscape, SLO and SLI design, incident management process design and runbook completeness, change and deployment management gating controls, and integration flow monitoring coverage — flags alerting blind spots, missing SLO definitions, incomplete incident runbooks, ungated production deployments, and cross-system observability gaps. Static advisory only — never mutates any Cloud ALM configuration, monitoring rule, or incident record; escalates critical availability and change-control findings to the SRE lead, Cloud ALM administrator, IT operations manager, and internal audit per protocol.",
  "source_type": "original",
  "official_docs": [
    "https://help.sap.com/docs/cloud-alm/applicationhelp/what-is-sap-cloud-alm",
    "https://help.sap.com/docs/cloud-alm/applicationhelp/health-monitoring",
    "https://help.sap.com/docs/cloud-alm/applicationhelp/incident-management",
    "https://help.sap.com/docs/cloud-alm/applicationhelp/change-and-deployment-management",
    "https://help.sap.com/docs/cloud-alm/applicationhelp/integration-and-exception-monitoring"
  ],
  "security_notes": "Static review only — no Bash, no Cloud ALM API calls, no monitoring rule mutations, no incident record modifications, no deployment job execution. Never accepts production Cloud ALM API credentials, SAP BTP service instance keys, incident records with personal data, or transport request content that includes configuration secrets. Any finding representing a complete monitoring blind spot for a production-critical SAP service, an ungated production deployment path, or an absent incident escalation route for P1 incidents MUST be escalated to the SRE lead, Cloud ALM administrator, IT operations manager, and where change-control gaps affect audit compliance, the internal audit function, before any remediation is applied. All guidance is advisory; Cloud ALM monitoring rule changes, SLO definitions, runbook updates, and change management workflow modifications require operations change-management approval and audit-trail documentation.",
  "last_verified": "2026-06-19",
  "path": "agents/sap/sap-cloud-alm-sre-incident-agent",
  "author": "github: VincentChuWaiChow",
  "companion_skills": [
    "sap-cloud-alm-sre-incident-review"
  ],
  "execution_tier": "static-review",
  "lifecycle": "experimental",
  "harness_variants": {
    "codex": "agents/sap/sap-cloud-alm-sre-incident-agent/harnesses/codex.toml",
    "claude-code": "agents/sap/sap-cloud-alm-sre-incident-agent/harnesses/claude-code.agent.md",
    "copilot": "agents/sap/sap-cloud-alm-sre-incident-agent/harnesses/copilot.agent.md",
    "cursor": "agents/sap/sap-cloud-alm-sre-incident-agent/harnesses/cursor.agent.md",
    "gemini": "agents/sap/sap-cloud-alm-sre-incident-agent/harnesses/gemini.agent.md",
    "kiro-ide": "agents/sap/sap-cloud-alm-sre-incident-agent/harnesses/kiro-ide.agent.md",
    "kiro-cli": "agents/sap/sap-cloud-alm-sre-incident-agent/harnesses/kiro-cli.agent.json"
  }
}
