The Catalog page

The Studio tab opens here: what your org has built, who receives it, and what needs a person.

Search everything

The header’s search box covers all three libraries at once — entities, briefs, and skills — and it reads the contents, not just the names: descriptions, synonyms, instructions, brief bodies, refusal policies, procedures. Each hit says where it matched and quotes the line, and clicking one opens the artifact’s page. When you know a phrase but not which artifact carries it, start here.

The counts

Five cards — Entities, Briefs, Skills, Domains, Elements — each a number with the caveat that matters beneath it: entities not yet activated, how many object defaults answer calls that name no domain, and the element split (metrics · formulas · enrichments). Each card opens its page.

The domains

One card per domain, wearing the same colored-circle identity the Domains page draws, with counts of what it carries (entities · briefs · skills), its loads over the last seven days, and a warning when an entity in it has never been activated. The default domain leads and names its mode: it either reaches only people who have no other domain, or is received alongside every other domain.

Clicking a card opens the domain. The preview icon opens the catalog explorer, already scoped to that domain.

The catalog explorer

One screen showing everything an agent with a given access can find and fetch. The left panel is the discovery tree: Get Catalog at the top, and beneath it every drill-down the index offers — each entity’s full contract (fields per level, filterable fields with valid values, named filters, groupable fields, writable fields, synonyms, instructions), each brief Get Briefs would serve, each skill Get Skill would return.

The right panel shows the selected node exactly as an agent receives it, with a token estimate, in any of three readings: Formatted, Markdown or JSON. The tree is built from the index’s own output, so what it offers and what agents see are the same list.

Change the scope inside to look at any domain. Any node opens in Studio from there, in a new browser tab, so reading the contract and fixing it are not two trips.

Needs attention

Two rules make certain states invisible by design: an artifact that is not activated reaches nobody, and neither does one in no domain. This list is where those states become visible — in a domain but never activated, activated but in no domain, edited since it was last activated. Each row says what to do, and links to where you do it.

Recent changes · Recent issues

Two cards side by side: the Change Log’s freshest events, and the freshest assembly issues with the domain each came through. What moved, and what degraded, without leaving the page.