Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · specializations/observability/incident-lifecycle
lib-process:observability--incident-lifecyclea5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewjsongraph
II.
LibraryProcess overview

lib-process:observability--incident-lifecycle

Reference · live

specializations/observability/incident-lifecycle overview

DEPRECATED. The full detection-to-postmortem incident lifecycle that once lived here (single-workflow lifecycle, severity matrix, non-incident early exit, timeline accumulation, comms phase model with no-blame rules, iterative 3-pass diagnosis, SLO breach detection, and follow-up issue creation) is now owned by the incident-management flagship, whose header records this module as an `@absorbs` seed — every one of those features is implemented there against a superset contract (same signal shape, additional severity-routed policy gates and an adversarial postmortem gate). This file re-exports the flagship `process` so existing callers of `specializations/observability/incident-lifecycle` keep working unchanged. Observability is now an SLO-driven practice; its flagship is `slo-lifecycle.js` in this directory.

LibraryProcessOutgoing · 13Incoming · 0

Attributes

displayName
specializations/observability/incident-lifecycle
description
DEPRECATED. The full detection-to-postmortem incident lifecycle that once lived here (single-workflow lifecycle, severity matrix, non-incident early exit, timeline accumulation, comms phase model with no-blame rules, iterative 3-pass diagnosis, SLO breach detection, and follow-up issue creation) is now owned by the incident-management flagship, whose header records this module as an `@absorbs` seed — every one of those features is implemented there against a superset contract (same signal shape, additional severity-routed policy gates and an adversarial postmortem gate). This file re-exports the flagship `process` so existing callers of `specializations/observability/incident-lifecycle` keep working unchanged. Observability is now an SLO-driven practice; its flagship is `slo-lifecycle.js` in this directory.
libraryPath
library/specializations/observability/incident-lifecycle.js
specialization
observability

Outgoing edges

lib_applies_to_domain1
  • domain:observability·DomainObservability
lib_belongs_to_specialization1
  • specialization:observability·Specialization
lib_implements_workflow3
  • workflow:incident-response·WorkflowIncident Response Workflow
  • workflow:on-call-rotation·WorkflowOn-Call Rotation
  • workflow:post-mortem-review·WorkflowPost-Mortem Review
lib_involves_role4
  • role:sre·RoleSRE
  • role:observability-engineer·RoleObservability Engineer
  • role:devops-engineer·RoleDevOps Engineer
  • role:platform-engineer·RolePlatform Engineer
lib_requires_skill_area4
  • skill-area:incident-response·SkillAreaIncident Response
  • skill-area:alerting-oncall·SkillAreaAlerting & On-Call Management
  • skill-area:observability-instrumentation·SkillAreaObservability Instrumentation
  • skill-area:sli-slo-management·SkillAreaSLI / SLO Management

Incoming edges

None.

Related pages

No related wiki pages for this record.

Shortcuts

Open in graph
Browse node kind