What this panel answers
Underneath the DORA cards on the Analytics page sits a quieter block called Live system. The four DORA numbers tell you how the team is doing over weeks. Live system tells you how the team is doing right now — whether the lights are green, whether the morning ran, whether anything is waiting on a human. If you check one place before your first meeting of the day, this is the place.
It is one panel. No bordered cards, no second page to drill into. Health on the left, what is moving in the middle, what is waiting on the right.
The masthead
A single line across the top of the block. It tells you three things in plain language. The percentage of recent runs that succeeded — written as 96 percent, 100 percent, that kind of number. How long ago the last run was — "5 minutes ago", "an hour ago", "yesterday at 2 p.m." How many failures there were in the last seven days, if any. If the number is zero, the chip stays off and you do not see a colour. If there were failures, the chip is the warm coral colour and you can read the count without scrolling.
The masthead is the single most important sentence on Analytics. If everything reads green, you can close the tab. If the percentage drops or the failure count climbs, the rest of the panel tells you where to look.
Knowledge
A short line for your knowledge base. Two pieces of information: its state (idle, running, errored) and how many new articles came in today. Ingested today is a freshness number — it tells you whether your sources are actually pulling new material, or whether a docs repo went quiet because someone broke its connection. If the count stays at zero for several days in a row, open the Knowledge page and check on your sources.
The state is the health signal. Running means a refresh is in progress and you should check back in a moment. Errored — coral colour — means something needs your attention. The story behind the error lives one click away on the Knowledge page.
Routines
The two or three most active routines in your workspace, with their current state. A routine is a scheduled job your team uses to do recurring work — a daily intake pass, a weekly QA sweep, a nightly knowledge refresh. The list does not try to show you every routine, only the ones moving most right now, so the panel stays readable.
If the routine you expected to see at the top isn't there, open the Routines page from the Analytics rail — it might have been disabled, paused, or never wired up in the first place.
Daily
The daily retro queue. Every day, a small role inside Ship reads the last twenty-four hours of your team's runs and asks one specific question — "did any lane produce no movement?" A workflow that ran successfully but did not actually move a ticket forward is the silent-failure case that politely exits green and tells you nothing. The daily retro queue surfaces those quiet stalls so a person can decide what to do.
What you see in the cell is the count waiting for review. Zero means yesterday went cleanly. A small number — one, two, three — means there is something to look at. A larger number, day after day, is a signal that the routines are running but the work itself is not moving, and the conversation belongs in a planning session, not in this panel.
Specialists
The bottom cell counts the active specialists — the agent roles your workspace has wired up. Planning, development, validation, self-heal, daily retro, security audit, whichever roles your process needs. The count is a passive number, not an alert. It is here so you can confirm at a glance that the roles you expected to be running today are still configured to run.
If a specialist disappears from the count, it has been disabled — usually deliberately, sometimes by accident. Cross-check against the team's intent.
How to read the panel together
A healthy morning reads like this: green percentage on the masthead, last run a few minutes ago, no failures, knowledge ingestion not zero, the routines you expected, an empty daily queue, your specialist count where you set it.
A morning that wants your attention reads differently. The masthead drops to 80 percent. The daily queue has eight items. Knowledge ingestion is stuck at zero for the third day. The story is somewhere in the panel, and it usually takes less than thirty seconds to find. Click into the cell that looks wrong; the page behind it has the detail.
The point of the Live system block is not to give you another dashboard to monitor. It is to let you stop monitoring — to give you one panel that you can glance at, accept, and move on from. Most days, you should.