Ops Command
Six registers you keep — stock, movements, services, incidents, people and shifts — and thirty-five readings of them. No monitoring and no feeds: everything here is arithmetic over records you enter. Stock on hand is the sum of its movements Availability computed from your own incident log
Operations Overview
ROLL_UP: Everything below is counted from the stock, service and roster registers you keep. Nothing on this page is fetched, guessed or simulated.
Wants attention
Every row here names the record that produced it
Last thirty days
Incident minutes per day, from the incident log
Recent activity
Stock Register
ON_HAND_IS_COMPUTED: Stock is the sum of its movements, never a number typed into a cell — so every level has a history behind it.
Movement ledger
Every receipt and issue, newest first. This is what stock on hand is made of.
Services & Incidents
UPTIME_IS_COMPUTED: from the incidents you log, over the window you choose. Nothing here pings anything.
This page does not monitor anything. It has no agent, no ping, no webhook and no network access to your infrastructure. It is a place to RECORD outages after the fact, and the availability figures it produces are arithmetic over what you recorded — which is a real number, and a different thing from a monitor.
Incident log
Newest first. An incident with no end time is still open and counts to now.
People & Roster
COVERAGE_IS_COMPUTED: from the shifts you assign. Gaps and clashes are found by comparing them, not by watching anyone.
People
Everyone on the roster, with the hours they are assigned
Shifts
Newest first
Toolkit
REGISTER_INSTRUMENTS: Thirty-five readings of the records you keep.