A tour of the dashboard: six panels, zero mysteries

Live verdicts, hit-type economics, top misses, safety blocks, tenant accounting, system pressure, what each panel answers and who keeps it open.

The live verdict feed is the dashboard's heartbeat and the fastest trust-builder in the product: every hit, miss, and refusal streams past with its confidence score and the gate that decided, DUAL HIT at 0.94, BLOCKED at stage 3. New operators watch it the way you watch a fish tank; auditors watch it the way they watch evidence.

The economics panels translate engineering into budget language: hit-type breakdown (vector, structural, dual, dedup, reasoning) shows which intelligence earns; saved-spend counts dollars and tokens per tenant and per model; top queries and top misses rank where value concentrates and where pre-warming would pay. The misses list doubles as a roadmap for your docs team.

flowchart TD
  Q["incoming query"] --> I["intent classifier"]
  I --> T["template match"]
  T --> V["HNSW neighbours"]
  V --> C["confidence gate"]
  C --> TR["trust + freshness"]
  TR -- pass --> A["answer · <1ms"]
  I -. veto .-> M["(nil) → your model"]
  T -. veto .-> M
  V -. veto .-> M
  C -. veto .-> M
  TR -. veto .-> M
  style A fill:#fbe9e8,stroke:#d62221,stroke-width:2.5px
  style M fill:#f3eee5
Figure 1. the crowkis read path, five gates, every one can veto Reuse only when meaning, structure, confidence, and trust all agree.

Safety and pressure round out the picture: anti-poisoning rejections by stage characterize what your traffic drags in; memory, block-cache, and SSTable-level gauges narrate capacity; license state sits in the corner being uneventful, as licenses should.

The bottom line

Everything mirrors to Prometheus for your real estate, but the built-in view costs zero setup and answers the only question that matters on day one: is this thing earning? It is, and it shows its math.