iServ
Ops Reporting System
Weekly engineering briefs generated by a deterministic collector, published to fail-closed gated dashboards. No number is ever hand-typed.
01 The story
A reporting habit turned into infrastructure. A collector script derives commits, builds, and session metrics from the actual repos, a generation skill writes the weekly brief, and static dashboards render it behind passcode gates that return 503 if their secrets are missing rather than failing open. In July four drifting dashboard forks were collapsed into one. In August the internal sales command center gained a second version in a single day: team management, per-person compensation plans, forecast accuracy, a field sales log, and a shared state API so the whole team sees one book, refined through six critique-and-revise loops before it shipped. The same gate pattern protects the full-detail layer of this very site.
02 What went into it
- Deterministic metric collection from git and session logs
- Skill-generated weekly briefs with carry-forward to-do boards
- Fail-closed edge gates with HMAC session cookies
- Venture, all-up, and per-engineer scopes
- Four dashboard forks consolidated into one
- Sales command center v2: team and compensation plans, forecast accuracy, field sales log, guided operator tour
- Shared state API over Postgres with a local fallback when the database is not configured
03 Stack and capabilities