Digest
What 3AM did, or in shadow would have done, next to what your team did; agreement, readiness for L1, and how to tell 3AM what your team did.
Digest (/digest, g d) answers can we trust 3AM with more? Pick the period (24 hours, 7, 30 or 90 days); the
page remembers it. It is also written every night at 00:00 UTC to digests/YYYY-MM-DD.{md,json}.
The answer first
- How often 3AM agreed with your team, as a ring and a sentence ("3AM agreed with your team 3 of 4 times"), and which services are ready for L1.
- Incidents, causes proven, fixes 3AM ran (verified), services.
Per service
How near it is to L1 (3 of 5 judged, Ready for L1, or already at L1), its figures, and its incidents as a timeline: when, what fired, what was proven, then 3AM's call next to your team's, and whether they agreed.
Ready for L1
A service in shadow is ready for L1 when:
- at least 5 proposals have a known outcome from your team,
- at least 80% of them agreed,
- and policy would have refused none of them.
It's advice: raising still needs two approvers (Autonomy).
Telling 3AM what your team did
On the incident's page: What did your team do? Or post it from an integration as a human.action event:
curl -s -X POST -H "Authorization: Bearer $INGEST_TOKEN" -H 'Content-Type: application/json' $URL/v1/events -d '
{"type": "human.action", "actor": "human:dba-oncall", "reason": "fixed by hand",
"data": {"service": "core-banking-db", "action": "sql.write", "detail": "SET GLOBAL read_only = OFF", "class": "db_read_only"}}'GET /v1/digest?days=7 returns the digest as JSON plus Markdown; 3am-core digest [DAY] writes one.
Approvals page
The record of every approval request, its channels, who decided, and withdrawing one that is pending.
Impact and the lookback
The business report in your own money (what 3AM returned, where it came from, how the figures are made), saved as PDF, and the lookback over your last 90 days of incidents.