Wired to the Local Contexts Hub Integration Partner API

# Local Contexts Hub Integration Partner Anamata Kāhui is now wired to the **Local Contexts Hub** as an Integration Partner. The Hub maintains 42 canonical labels for indigenous data — including the 20 Traditional Knowledge (TK) labels, 10 Biocultural (BC) labels, and 12 Notices. ## What this enables - **Local Caching** of the 42 canonical labels with TTL revalidation - **Per-Project Search** by DOI or provider_id (for research papers and partner releases) - **File Metadata Embedding** — labels travel with the file: - XMP for PDFs (research papers, press kits) - ID3 for audio (waiata stems and masters) - **Visual display** above the fold on `/waiata/[slug]` and `/research/papers/[id]` ## How it works The platform caches the label catalogue in a `lc_labels_cache` table with hourly revalidation (handled by a Vercel cron). Each release can attach a `lc_project_id` that links to the Hub. On render, the labels appear in the page header with a one-line description, a colour-coded badge (TK = bronze, BC = pounamu, Notices = kōhai), and a deep-link to the canonical Local Contexts page. ## First labels attached The first release to use this is Te Tinihanga, with three labels attached: - **TK Attribution** — traditional knowledge, attribution required - **BC Provenance** — bi-cultural provenance (Māori + Pākehā origin) - **Caring notice** — handle with care, replace with care ## Why this matters Most music metadata stops at ISRC + duration. Anamata's metadata keeps going — into the cultural accountability layer. Local Contexts is the canonical way to do that. The Hub's Integration Partner programme requires a real-world deployment, which we now have. More at `/governance` and `/kaitiakitanga`.