Path 05 · 8 lessons · 90 min
Operate and improve
Maintenance, observability, incident management, SOC and SIRT. Close the loop with bounded self-healing and verified improvement.
- 01
Own the service after deployment
Define useful service signals, incident decisions, recovery, and maintenance. Keep operational responsibility visible after code generation ends.
- 02
Maintain software throughout its useful life
Prioritize vulnerabilities, upgrades, configuration drift, and retirement. Follow a maintenance finding through to a verified production correction.
- 03
Keep finding and fixing vulnerabilities
Build a continuous process from vulnerability detection to verified production remediation. Understand the maintenance gap a successful prototype can hide.
- 04
Observe the service and its users
Connect metrics, logs, and traces to service objectives. Design alerts, data boundaries, and checks for missing telemetry.
- 05
Manage an incident from detection to recovery
Coordinate responders, contain impact, communicate uncertainty, and verify recovery. Convert the incident into owned improvements.
- 06
Connect delivery to the SOC and SIRT
Define security monitoring, incident handoff, evidence preservation, and recovery responsibilities. Keep security response connected to the software lifecycle.
- 07
Set safe boundaries for self-healing
Automate known recovery actions with explicit authority, verification, and stop conditions. Separate runtime recovery from changing software.
- 08
Close the loop with verified improvement
Turn production evidence into requirements, tests, controlled changes, and measured outcomes. Define what self-improving software can responsibly mean.