slug: firehydrant provider: FireHydrant generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 13 edges: - tag: Incidents spec_file: firehydrant-incidents-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.95 evidence: POST /v1/incidents createIncident; PUT /v1/incidents/{incident_id}/close closeIncident; Get chat channel information for an incident reason: 'Core incident lifecycle: declare, update, assign roles/teams, close — production incident response management.' - tag: Retrospectives spec_file: firehydrant-retrospectives-api-openapi.yml capability_id: BC-4220.40 capability_id_l1: BC-4220 capability_name: Postmortem & Reliability Improvement confidence: 0.95 evidence: POST /v1/post_mortems/reports createRetrospectiveReport; "Publish a retrospective report"; "Create a contributing factor for a retrospective report" reason: Postmortem report authoring, publication and contributing-factor tracking is exactly Postmortem & Reliability Improvement. - tag: Signals spec_file: firehydrant-signals-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.9 evidence: GET /v1/signals/ingest_url getSignalIngestUrl; schemas postV1TeamsTeamIdEscalationPolicies, patchV1TeamsTeamIdOnCallSchedulesScheduleId reason: Alert ingestion, escalation policies and on-call schedules/shifts are precisely on-call response and incident detection. - tag: Alerts spec_file: firehydrant-alerts-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.88 evidence: GET /v1/alerts listAlerts List alerts; POST /v1/incidents/{incident_id}/alerts createIncidentAlerts Attach alerts to an incident reason: FireHydrant is an incident management platform; alerts here are production incident alerts attached to incidents, i.e. on-call detection/response, not financial-crime alerting. - tag: Incident Settings spec_file: firehydrant-incident-settings-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.8 evidence: GET /v1/incident_roles listIncidentRoles; GET /v1/incident_tags listIncidentTags; List custom field definitions reason: Configuration of incident roles, types, priorities, tags and lifecycle milestones — configuration surface of incident response management. - tag: Runbooks spec_file: firehydrant-runbooks-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.8 evidence: POST /v1/runbooks/executions createRunbookExecution; "Terminate a runbook execution"; schema Runbooks_ExecutionStepExecutionEntity reason: Runbook definition and execution during incidents is the automation backbone of on-call/incident coordination on this incident management platform. - tag: Communication spec_file: firehydrant-communication-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.75 evidence: GET /v1/status_update_templates listStatusUpdateTemplates reason: Status update templates are used for incident communication to stakeholders/customers during production incidents, part of incident response management. - tag: Tasks spec_file: firehydrant-tasks-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.75 evidence: POST /v1/incidents/{incident_id}/tasks createIncidentTask "Create a task for an incident"; "List checklist templates" reason: Incident-scoped task lists and checklist templates coordinate work during production incidents, which is incident response coordination. - tag: Teams spec_file: firehydrant-teams-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.72 evidence: POST /v1/teams/{team_id}/on_call_schedules createTeamOnCallSchedule Create an on-call schedule for a team reason: Operations manage incident-response teams and their on-call schedules/shifts on an incident management platform, which is the on-call response element of Incident Response Management. Some of the surface is plain team CRUD (team directory), which tempers confidence, but the on-call schedule and shift operations and the Incidents_* / ScheduleEntity schemas ground it in SaaS platform incident response rather than HR team management. - tag: Change Events spec_file: firehydrant-change-events-api-openapi.yml capability_id: BC-4210 capability_id_l1: BC-4210 capability_name: Software Release & Deployment Management confidence: 0.7 evidence: POST /change_events createChangeEvent Create a change event reason: Change events record deployments/production changes correlated with incidents; closest fit is software release & deployment management, though sub-capability is ambiguous (deployment orchestration vs production change authorisation). - tag: Metrics/Reporting spec_file: firehydrant-metrics-reporting-api-openapi.yml capability_id: BC-4220 capability_id_l1: BC-4220 capability_name: SaaS Platform Operations Management confidence: 0.7 evidence: GET /v1/metrics/incidents listIncidentMetrics "List incident metrics and analytics"; "List retrospective metrics for a date range" reason: Operations expose incident, milestone-funnel and retrospective metrics for a production service — reliability/incident analytics within SaaS platform operations. Sits across Service Reliability Engineering and Postmortem & Reliability Improvement, so no single L2 is named by the evidence. - tag: SCIM spec_file: firehydrant-scim-api-openapi.yml capability_id: BC-4230.50 capability_id_l1: BC-4230 capability_name: Tenant Identity Federation confidence: 0.7 evidence: POST /v1/scim/v2/Users createScimUser "Create a user via SCIM"; GET /v1/scim/v2/Groups "List teams via SCIM" reason: SCIM user and group provisioning exposed by the SaaS vendor for customer-directory-driven account lifecycle, matching tenant identity federation via SSO and SCIM. Could alternatively be read as generic IAM, hence moderate confidence. - tag: Status Pages spec_file: firehydrant-status-pages-api-openapi.yml capability_id: BC-4290.30 capability_id_l1: BC-4290 capability_name: Trust Portal & Public Disclosure confidence: 0.7 evidence: POST /v1/nunc_connections createStatusPage; "Create a status page subscription"; "Unsubscribe from status page notifications" reason: Operation of customer-facing hosted status pages with components and subscriber notifications matches public status disclosure; partially overlaps incident customer communication.