KIST / HOW IT WORKS
The pipeline behind the number on the screen
Five stages, in order, every time. Nothing on a client's dashboard skips a step, and nothing gets there by a side path.
THE FIVE STAGES
Chat, MCP, query, render, R2
Chat
A question, asked in plain English, from a dashboard, from Slack, or from your own tooling. This is the only stage a person touches directly.
MCP
The question reaches one governed gateway, never the database directly. The gateway is what pins the question to a single client before anything runs.
Query
A read against the curated tables: raw response, cleaned into one shape per client, then curated into the small set of tables everything downstream reads from. A query that reaches outside its own client is rejected outright, not quietly trimmed.
Render
The answer comes back in whatever shape the question needs: the raw rows, the tidy summary, or a chart. Nothing is recomputed for a different audience. The same figure holds across all three.
R2
A finished render is stored where it can be reused and reloaded fast, rather than rebuilt on every view. The gold data behind it never takes this hop. Only the finished picture does.
WHAT YOU ARE ABOUT TO SEE
The actual shipped hero, not a mockup of one
The panel below is not a screenshot and not a hand-composed layout with invented numbers in it. It is the same component that renders on the homepage, reading real figures (selectable text, a real chart) end to end through the stages above.
REAL PRODUCT / SEEDED DEMO DATA
What your AI would actually see
This is a real Warehouse read of Lochend Wild's ad account, shaped exactly the way a client's own dashboard is. Lochend Wildis not a client, it is our own seeded demo tenant, built so we can show the product working without touching anyone's real numbers.
- Family day passes, conversion6.92xSpend £3,580Attributed £24,786
- Brand reach reel1.06xSpend £1,135Attributed £1,200
Lochend Wild is a fictional client we built to prove the methodology on. Every figure here is seeded to a published spec, not invented, and no live client's numbers ever appear on this page.
WHERE THIS STOPS, ON PURPOSE
This page cannot ask it a new question
The panel above is a committed snapshot of a seeded demo tenant, not a live query. A client's own data is never within reach of a public, unauthenticated page. The pipeline above runs for real, but only behind a staff or client sign-in, never for an anonymous visitor. Ask it a live question on a call, or once you are in.
This is not a shortcut taken to make the demo easier to build. It is the same boundary that keeps every client's data on its own side of the query, described in full on the guards page.