Best for
- Projects where 'what does this table do?' takes an hour to answer
- Onboarding anyone (human or AI) without a guided tour
- Audits, handovers and due diligence
What you give it
- Access to the project, and the item you want documented
- Corrections when reality and the catalogue drift
What you get back
- One metadata page per item: purpose, owner, shape, relationships, caveats
- A consistent format across business, technical and operational items
- An index that answers 'what do we have?' in one read
How it works
- Reads the real artefact — schema, code, configuration — not just its name.
- Writes one page per item in a fixed template, in plain language.
- Links related items so the catalogue is a map, not a pile.
- Updates the index with every page, keeping one entry per item.
- Flags drift when the artefact and its page disagree, instead of papering over it.
Example
You: Catalogue the orders table and the nightly cleanup script.
Result: Two pages: the table's purpose, columns with meanings, who writes to it and the two gotchas in its status field; the script's schedule, what it deletes, how to run it safely by hand — both linked from the index.
Limits — please read
- It documents what exists; deciding what SHOULD exist is design work, not cataloguing.
- Pages age — schedule refresh passes or tell it when things change.
- Secrets and credentials are never written into the catalogue.