catchlaw-content-pipeline

Governs the CatchLaw content pipeline that compiles hand-authored rules.yaml, species.yaml, vernacular.yaml, citations.yaml, zones.yaml and plates.yaml plus a Catalogue of Life extract into the read-only reference.db asset — the tools/content_builder CLI as a first-class deliverable, ten assertions that FAIL the build on a min_size with no measurement_method, an unresolved content_string key in any of the six locales, a null gender in a gendered locale, a citation with no retrieved_on, a plate failing the illustrator death-year test, a search_norm not written by the shared normalise, a rule-engine contradiction, or a missing per-jurisdiction changelog diff. Use when authoring rules.yaml or species.yaml, adding a locale or a vernacular name, extending tools/content_builder, seeding reference.db, adding a citation or a bundled plate, clearing a plate licence question, or reviewing content_builder_assertions.dart in a diff.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/zakariaf/catchlaw

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.

216 critical findings reported by agent-audit-kit, 0 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.