Skip to main content
On this page

Guides

Key concepts

The words Kater uses for where things live, how data is modeled, and how people and agents work with it.

Kater uses a small set of words. Learn them once, and every page of these docs and every screen of the portal reads the same way.

Your organisation

TermWhat it is
OrganisationYour company in Kater. People sign in to it through PropelAuth, and everything belongs to one organisation.
ConnectionOne warehouse, Snowflake or DuckDB, and everything modeled on it. Its folder is connections/<name>/.
Content storeThe git repository where Kater keeps your organisation’s content. Nobody clones it directly.
Local copyA snapshot of everything you can read, made with kater git clone. You publish from it with kater git push.
Write-backAn optional, one-way publish of each connection’s modeling/ folder to your own GitHub repository.
RolesAdmin, Developer and Viewer. Each role carries permissions, such as running SQL or managing users.
Access levelsViewer, Editor and Manager, granted on folders and files to people, groups or Everyone.

Layers

Each layer reads only from the layers above it.

LayerWhat lives thereWho writes it
SourceDatabase datasets, in modeling/db_objects/Schema sync
SharedKater datasets, semantic models and shared tests, in modeling/kater_objects/The data team
WorkspaceWorkspace roots, queries and chartsAnyone, in workspaces they can edit
SandboxScratch files in your brainstorm folder, which nothing readsYou

Modeling

TermWhat it is
Kater SQLYour warehouse’s SQL with Kater’s additions: DIMENSION, MEASURE, CUSTOM_CALCULATION, EVAL, filters, RELATIONSHIP, the KATER__ functions and -- @ comments. Every model is a .sql file with a short YAML header.
Database datasetOne warehouse table, as a generated CREATE TABLE.
Kater datasetThe governed view of one table: named dimensions, measures and formats.
Custom SQL datasetA Kater dataset written as one read-only SQL query over warehouse tables.
Semantic modelKater datasets joined with relationships into the model people ask questions of.
DimensionA field you group, filter or slice by, such as Platform or Order Month.
MeasureA reusable total, such as Spend, added up again at whatever level a reader asks for.
Custom calculationA field a query computes across rows, such as a running total or a rank.
Parameter and filterA value a reader sets, such as a date window, and the condition that uses it.

Analysis

TermWhat it is
WorkspaceA project over one shared model, with its queries, charts, dashboard, tests and apps. It is personal, or a connection workspace that others can share.
QueryA saved Kater SQL question in a workspace. Its files sit in the query_contracts/ folder.
ChartOne way to draw a query, saved in the workspace’s charts/ folder.
DashboardA workspace’s saved charts in sections, under one filter bar.
AppAn HTML page, report, deck or chat thread that draws live queries through Kater’s tags.
ExploreReady-made cards for each shared model, which you add to a workspace.
SandboxWhere you write SQL in scratch files and run it, before you select a workspace.
Brainstorm folderYour private folder for notes, scratch files, workspace copies and draft apps.
Workspace copyA private copy of a workspace where you try a change, then compare and apply it.

Agents

TermWhat it is
Kater MCPYour organisation’s MCP server. Agents connect to it and act as the person who signed in.
Ask panelWrites a prompt from what you type and the page you are on, then opens it in your agent. Kater runs no chat of its own.
StarterA ready-made prompt, such as Brief me, in the Ask panel and in your agent.
Scheduled workflowA workflow with a schedule: block, which your own agent runs on its own, such as every Monday at 08:00.
Skill, workflow and agentMarkdown files in ai_tools/ that teach your assistant a task, a multi-step process or a role.
About youYour about.md: your role, metrics, answer style and team. The company has one too.
Connection contextconnection_context.md, where the data team tells agents what a connection holds.
Rulesrules.md, your organisation’s own rules. Every agent reads it at the start of a conversation, after Kater’s rules.

Trust

TermWhat it is
Verified fieldA field a shared model defines. The server decides this, and a field computed in a workspace is not verified.
CuratedA model, query or workspace the data team recommends, with curated: ["true"] in its frontmatter tags. It grants no access and verifies no field.
PromotionMoving a field from a query to its workspace root, or from a workspace into a shared model.
Promotion requestA person’s request, with a reason, to move a field into a shared model. The data team approves or denies it.
Promotion recommendationA field Kater finds defined the same way in several models, offered to the data team.
TestA question with the rows you checked, run again after changes and after each sync.
History and UndoEvery change to a workspace, app or file, each of which you can undo as a new change.