@regixo/catalog-read

The shared read layer — one read path over the local store and the FREE compliance DRAFT, consumed by both the /api/v1 read API and the regixo mcp server so they always agree. Read-only by construction (no setter), zero metadata egress.

Part of Regixo — the free, local-first data catalog that auto-drafts EU compliance evidence (GDPR Art. 30 RoPA + DORA register). Install the CLI instead of this package directly: npx regixo start.

What it exposes

createCatalogReader(store, …) returns the one reader both agent surfaces are built on:

• Search — the same ranked, multi-word search the dashboard uses (FTS5 with an in-memory fallback).
• Datasets & columns — dataset views with personal-data flags, descriptions (suggested vs confirmed), owner and row-count estimates labelled as such.
• Lineage — dbt / warehouse / human-asserted edges, with resolvable flags on endpoints that were never scanned (an id the API emits never 404s without a flag on it).
• Compliance state — the DRAFT RoPA state, carrying who confirmed a legal field and when. The reader can report a human confirmation; nothing in this package can create one.
• DORA register — the DRAFT Register of Information (all 15 tables), for financial entities in scope.
• Changes, glossary, provenance — the append-only change log, the term glossary, and the machine-readable trust signal (seal: 'draft', staleness, classifier-method roll-up).

Because there is no write path, an AI agent reading the catalog through this layer cannot alter it, and no read ever leaves the machine.

License: AGPL-3.0-only