The operational backbone: pipelines, monitoring, incident response, security, quality gates, compliance, support. Specialised playbooks cover team rituals.
incidentv0.2.0What this builds
One step: run the devops creation sequence — pipelines, environments, deployments, runbooks.
7 phases · 26 entity types
Follow these steps in order. Each one adds entities to the graph and sets up the next.
Establish the pipeline. How does code go from commit to production reliably and reversibly?
Decide what you measure for availability, latency, and quality. Set targets. Wire alerts to people, not silence.
Define how you respond when things break. Every incident gets a postmortem; every postmortem identifies root causes; root causes drive change.
Model what could go wrong. Catalog known threats. Wire controls and access policies that actually constrain risk.
Establish what does not ship until tests pass. Define the test pyramid: unit, integration, end-to-end. Quality is a delivery concern: gates guard the features they cover and the bugs they catch, which is also where incidents trace back (a shipped defect becomes a production incident).
Map the frameworks you must comply with: SOC 2, GDPR, HIPAA, WCAG. Surface controls and audit cadence.
Define how customers reach you when things break, and how you build collective memory from each interaction.