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/digital-factory.md

@@ -708,7 +708,8 @@ is kept outside it.
    own, and keeps its records in ERPNext. A tool that cannot read from or
    write to ERPNext this way is not finished; a tool with its own
    database of business records is not allowed. Machine data is the only
-   exception.
+   exception. The [own catalogue](catalogue-intelligence.md) dashboard,
+   sales map and demand model are planned this way.
 
 ### Hosting on NixOS