Give CEEZ something you need done.

Your manager's desk — what needs a decision, the live pulse, and one-click actions.

1. 1After login you land here. Read how many items need your decision and how many are running now.
2. 2Scan At a Glance: worker items to review, audit-inbox items, active goals, briefings.
3. 3Note Today (runs, cost, success) and try the "Ask anything" bar.

Why it matters: a workforce needs a manager's desk — humans stay in control without micromanaging every agent.

Chat with any agent or team; sessions persist and cross-team routing is automatic.

1. 1Pick a team on the left and ask a question — it routes to the right agent and answers from live data.
2. 2Note the reply controls: a confidence chip, the evidence trail, and one-click PDF / save-as-skill.

Why it matters: answers are grounded and honest — if the data can't support a claim, the agent says so rather than guessing.

Goal-driven cases: an agent or team investigates across rounds, accumulating evidence until a verified conclusion.

1. 1Header stats: 48 cases · 88% close rate · 75% avg confidence.
2. 2Open a case: read the Objective, then the Summary with the exact rows queried as evidence.
3. 3Note the round marker (e.g. R6/6) — this took multiple verified rounds, not one shot.

Why it matters: autonomous, evidence-verified root-cause analysis a human can audit end to end.

Edit agents, teams, skills, tools, hooks, policies. Every save creates an immutable version.

1. 1Browse the agents — each has an autonomy tier (Supervised / Monitored) and a version.
2. 2Open one to see its sealed system prompt, bound model, and trust score.
3. 3Click History — every change is versioned and replayable.

Why it matters: agents are governed, versioned artifacts you can inspect, edit, and roll back — not black boxes.

Saved deterministic pipelines — replay a proven run on demand, on a schedule, or via API, with no LLM, no cost, and a sealed trail.

1. 1Each row is a frozen pipeline (e.g. which sites have the most firing alerts — 29 steps).
2. 2Click Run and read the deterministic report — same steps, same result, every time, $0.

Why it matters: once the agents figure something out, you freeze it into a runbook — cheap, instant, reliable forever.

Every consequential action, sealed across the tenant. Click any row for the forensic view.

1. 1Each row is a sealed decision — a query_data with the exact SQL, or an agent_reply with cited facts.
2. 2Click a row for the full forensic view: the trail, evidence, and its hash + version.

Why it matters: in regulated operations you must prove why a decision was made — here every one is replayable and provable.

Decisions, runs, cost, success, latency, and tool usage across the whole workforce.

1. 1Top tiles: decisions, runs, tokens, and open inbox.
2. 2Check Run Latency (P50/P90/P99) and Tool Usage — call counts and error rates per tool.

Why it matters: the workforce measures itself — throughput, spend, and reliability at a glance.

Fleet posture at a glance — with an "Ask CEEZ" bar that reaches the same agents.

1. 1Read the tiles: 22 sites · 41 devices · 56 WAN links · 22 tunnels · 22 critical.
2. 2Scan Top Alerts and Sites Needing Attention.
3. 3Try the Ask CEEZ bar ("Which sites are most at risk right now, and why?").

Value: the whole network's state in one screen — the 10-second answer to “are we okay?”

Faceted time-series: pick a site × metric × window, live from the warehouse.

1. 1Choose a site and a metric (latency, packet loss, utilization).
2. 2Switch the window (15m → 30d) and watch the chart redraw; the header shows min / avg / max.

Value: every point is a live query — what you see is exactly what's in the database.

Per-link availability vs. contract, error-budget bars, and breach flags.

1. 1Each primary link shows target vs actual, error budget used, and latency target/actual.
2. 2Spot the red BREACH flags and which providers carry them.

Value: ties raw telemetry to the business commitments operators negotiate in.

A live hub-and-spoke map of sites, tunnels, and providers — click a node to investigate.

1. 1See the three regional cores (London, Singapore, New York) on the global backbone.
2. 2Nodes are health-colored; click one to jump straight into its incident.

Value: structural context — where problems cluster and which providers carry the load.

The deterministic decision engine + the full audit ledger — "read → decide → act, without owning the hands."

1. 1Read the tiles: 29 incidents · 29 tickets · 26 paged · 28 remediations recommended · 0 executed.
2. 2Scroll the ledger: each incident shows RCA / Ticket / Page / Remediation with its autonomy level and whether it acted or was approval-gated.

Value: it kills alert noise and proves it never took an unapproved action — governance you can show an auditor.