Own catalogue: sales map, demand model and market advisor (plan)

New docs/catalogue-intelligence.md for Alexander's idea of a catalogue
the plant presses for itself. Why (idle Classic hours ~60k to 160k
records a year at 60 % specials on the doc basis; two-week represses
from the metal archive; Thai catalogue sells in Japan, EM Records,
ZudRangMa), scope (Poy Records as seed; customers' data and press dates
protected), data sources with access terms (Bandcamp ship-to fields,
distributor sell-through clauses, opt-in record passport registrations,
Spotify for Artists, Discogs CC0 dumps; Discogs API marketplace and
want data restricted), ERPNext touchpoints (Licence, Channel Sales
Report, Catalogue Recommendation, geocoded addresses, CRM), PDPA rules
for the map, dashboard views on an open-source map stack, a staged
demand model with a stocking rule for run size, a propose-only advisor
on an open-weights model, phasing, cost estimates, risks and open
decisions.

Backlinks: README (planning documents, layout), roadmap item 28,
digital-factory tool rule, artist-platform repress pre-orders,
production-timeline repress, revenue-model ResurRec Japan.

docs/roadmap.md

@@ -171,6 +171,11 @@ These three run in parallel and gate everything downstream:
 27. Mastering and cutting room (can move earlier if title-services demand
     shows up in Phase 4, or to host the joint audio engineering programme
     with Payap University, see [Payap partnership](payap-partnership.md))
+28. **Own catalogue** (idea, October 2026): press our own titles in idle
+    press time, steered by a sales map and a demand model
+    ([own catalogue](catalogue-intelligence.md)). The data work starts in
+    Phase 0 with Poy Records' existing sales; whether the catalogue is in
+    scope, and with what working capital, is decided before the build
 
 ## Standing principle