# Canonical Catalog Expansion

> Add or improve canonical data catalog collections, fields, aliases, relations, evidence tags, docs, and tests.

- Skill: `clawic/canonical-catalog-expansion-2` (Agent Skill)
- Install (CLI): `npx get-skill add clawic/canonical-catalog-expansion-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/clawic/canonical-catalog-expansion-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: clawic (https://skillmd.com/u/clawic)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/clawic/canonical-catalog-expansion-2

---


# canonical-catalog-expansion

Grow the canonical data catalog without degrading schema quality.

## Procedure

1. Read `docs/canonical-data-catalog.md`, the catalog ADR, `docs/governance/rfc-process.md`, data-storage boundary, and naming guide.
2. Use `claw collections list`, `claw collections <collection> schema`, and `claw db <collection> list|query` when available.
3. Decide whether the entity is built-in canonical or belongs in a custom database.
4. For promotion to canonical type or canonical user-profile attribute, require the RFC process record, public review link, and maintainer sign-off before treating the shape as accepted canon.
5. Add purpose, evidence tags, sparse optional fields, semantic relation fields, aliases, and migration/debt notes.
6. Keep user-facing structured records in the main database unless a sidecar reason is technical and explicit.
7. Update docs, tests, generated catalog coverage, and CLI/schema discovery together.

## Constraints

- A business category alone is not a reason for a separate database.
- Separate sidecars for volume, churn, blobs, sync complexity, logs, caches, encrypted vaults, or reconstructable indexes.
- Do not let Clawix define a parallel canonical schema.

