Maintain the data dictionary

Who can do this

Any member can browse the Catalog and the Data Dictionary page. Editing a table’s name or description requires an admin; tables viewed from another feature and committed historical versions are always read-only.

Ronja’s answers are only as good as her understanding of your tables. Three surfaces build that understanding: table descriptions, the per-table Catalog, and an optional dictionary table you link to your data.

Describe your tables

Descriptions are the plainest way to say what a table means. Ronja drafts many of them herself — those are labeled “AI-generated · click to edit”, and correcting them is exactly the point. Descriptions matter at the feature level too: a feature’s description is “used by the agent when choosing which feature to use.”

1. Open the table from its feature page.
2. Click the description under the table title (placeholder Add a description…).
3. Type what the table actually contains and save.

Read the Catalog

The Catalog is the column-statistics view. For every column it shows Field · Kind · Rows · Missing · Cardinality · Examples — a fast way to spot gaps, check what a column really contains, and decide what needs describing.

1. Open a table and switch to the Catalog tab. (Inside the feature page’s Data Explorer, the same view lives on the Columns tab.)
2. Flip the toggle for system columns if you need them — they’re hidden by default.

The Catalog: per-column statistics at a glance.

Link a dictionary table

If your team already maintains column definitions in a table of their own, you can reuse them instead of retyping — mark that table as the dictionary and link it to the tables it describes, and Ronja reads your definitions straight from it:

1. Open the table that holds your definitions.
2. Open the … menu and click Mark as data dictionary.
3. Open the … menu again and click Linked tables….
4. Pick each data table with Select a table…, then click Done.

Browse the feature’s dictionary

Every feature has a Data Dictionary page (/features/<id>/data-dictionary) that collects column documentation across the feature. Filter with All / Text / Numeric and search by name.

The payoff compounds: the more your tables explain themselves, the less Ronja has to guess when answering. For the things a dictionary can’t hold — procedures, business rules, terminology — use notes and Knowledge; How Ronja learns explains how the three surfaces fit together.