Reports
Depth
Time-stamped operational records (incidents, alarms). Create-when-needed; never fabricated to fill the pillar.
Reports is one of the pillars of every .human/. It holds time-stamped operational records — incidents, alarms — created only when there's something real to record.
.human/ workspace — you are here
Comprehension_contextreset.md
Goals
Evergreen
Reports
captainslog.md the append-only spine
Where it sits
Reports is a create-when-needed pillar: it's present in the floor but stays empty until a real operational event needs recording. Nothing is fabricated to fill it.
Example
A report exists only because something happened. Here's a generalized incident record:
## 2026-06-26 — incident: a deploy deleted a live file
- Detected: A post-deploy check found a published file missing (returning 404).
- Impact: One data layer of the site went offline; everything else kept serving.
- Cause: The deploy ran without a required setting, so it removed the file instead of keeping it.
- Fix: Re-ran the deploy with the setting in place — the file rebuilt from source, nothing lost.
- Follow-up: Make the deploy refuse to run without that setting, and verify the file is live afterward.
Related
Last updated