Monitoring Templates¶
Purpose¶
These templates support ES-113 — Operations and Monitoring.
Use this family after ES-112 deployment and transition has completed. ES-113 observes the system in operation and converts operational reality into evidence. The goal is not merely to check whether the system is up. The goal is to determine whether the deployed system is behaving within approved scope, preserving guardrails, respecting access/data controls, handling incidents, gathering user feedback, and producing enough learning to support ES-114 stewardship.
Recommended workflow¶
Deployment Readiness Summary
↓
Operations Monitoring Overview
↓
Monitoring Log
↓
Operational Event Log
↓
Incident Log
↓
Access and Data Monitoring
↓
Guardrail Monitoring
↓
AI Monitoring Record
↓
User Feedback Log
↓
Risk and Issue Updates
↓
Operations Monitoring Summary
↓
ES-114 Stewardship and Continuous LearningCopy location¶
Do not edit the reusable templates directly. Copy completed project versions into:
docs/project-workspace/monitoring/
Template set¶
Operations Monitoring Overview
Connect monitoring to deployment evidence, approved scope, monitoring objective, question, and risks.
02Monitoring Log
Record recurring checks, scope area, result, evidence, owner, and follow-up.
03Operational Event Log
Record operational events, category, impact, evidence, owner, and follow-up.
04Incident Log
Record incidents, severity, response, owner, evidence, status, and no-incident statement.
05Access and Data Monitoring
Monitor access, data use, data restrictions, prohibited data controls, issues, and follow-up.
06Guardrail Monitoring
Monitor architecture, design, evidence, access, security, privacy, AI, and operational guardrails.
07AI Monitoring Record
Track AI status, AI behavior checks, evidence, concerns, drift, fallback, and human review.
08User Feedback Log
Record user feedback, category, severity, themes, actions, owner, and carry-forward items.
09Risk and Issue Updates
Track new, changed, retired, and carried-forward operational risks and issues.
10Operations Monitoring Summary
Summarize operational findings and decide whether to continue, pause, stop, or move to ES-114.
Completion expectations¶
| Question | Evidence |
|---|---|
| What are we observing and why? | operations_monitoring_overview.md |
| What recurring checks were performed? | monitoring_log.md |
| What operational events occurred? | operational_event_log.md |
| Were there incidents or no incidents? | incident_log.md |
| Did access and data stay within approved scope? | access_and_data_monitoring.md |
| Did guardrails remain intact? | guardrail_monitoring.md |
| Was AI behavior acceptable or not applicable? | ai_monitoring_record.md |
| What did users report? | user_feedback_log.md |
| What risks or issues changed? | risk_and_issue_updates.md |
| Can ES-114 stewardship begin? | operations_monitoring_summary.md |
Do not treat monitoring as passive observation. ES-113 must produce actionable evidence: continue, continue with conditions, pause, stop, or transition to stewardship.
Monitoring is the first real test of operational trust. The deployed system must earn continued operation through evidence, not assumptions.