The supplied HTML is treated as source data. Only the catalogue-data JSON is parsed; the document's scripts and prose are not executed as instructions.
The source contains 72 industry ERP variants, 789 Micro-ERP configurations, 2,367 role-based application configurations and 4,734 contextual extension mappings. These extension mappings cover 246 reusable patterns; the contextual rows retain their application, module and industry rather than being collapsed by name.
The existing ERP inventory has 365 records: 239 reusable MicroERPs and 126 functional/suite entries. The import preserves their IDs and URLs. Source IDs become lowercase catalog slugs (erp-001, erp-001-m01, erp-001-m01-a1, erp-001-m01-a1-x1). These IDs preserve source traceability and avoid collisions with existing products.
ERP and Micro-ERP configurations live in erp-catalog; apps live in app-catalog; optional modules, integrations and hardware connectors live in extension-catalog. The graph contains 41,080 directed references including existing suite/capability associations. Every target is checked against the catalog inventory. Parent relations retain the complete ERP → Micro-ERP → Application → Extension path; ERP and Micro-ERP records also expose descendant apps/extensions directly.
The existing 30 MicroERP repository READMEs enrich 60 functional/reusable entries with documented capabilities, roadmap and repository references. Semantic family links connect related existing capabilities without claiming that an industry configuration is already implemented by them. Source-defined configurations use Reference status and unverified readiness. Source IDs do not automatically create deployable applications or Worker bindings.
Regenerate and validate
From the Catalogs workspace:
python3 erp-catalog/scripts/import-erp-hierarchy.py
python3 erp-catalog/scripts/verify-erp-hierarchy.pyTo refresh from an updated supplied document, pass its absolute path to the importer. The importer validates the expected source counts before writing records. erp-hierarchy-source.json is the versioned source snapshot; erp-hierarchy-import-report.json records its hash and counts.
Migrations 0018/0019 add records and merge source metadata. They preserve existing owner, stage, priority, custom metadata, dates, flags and configured infrastructure on replay. Existing extension seed entries are retained through a separate additive migration. Verification replays the complete migration chains in SQLite and checks ownership/infrastructure preservation.
Detail experience
All 40 catalog surfaces receive a compact responsive detail design. Standard item pages show a summary, section navigation, readable specifications and record information, while keeping existing catalog-specific actions, content and checklist previews. Editor and directory intelligence pages retain their specialized content models with the same visual rhythm. The existing light palette and square corners are preserved.
ERP/app/extension detail pages additionally provide searchable relationship cards, type filters, parent navigation and progressive loading. Lists paginate 36 entries at a time; filtering/search runs against the full inventory. The list projection excludes large relationship arrays and long capability notes; detail records and APIs retain their full metadata. Browser code imports lightweight catalog configuration separately from the source inventory.
Cross-catalog links default to the published catalog domains. Local previews can use NEXT_PUBLIC_ERP_CATALOG_URL, NEXT_PUBLIC_APP_CATALOG_URL and NEXT_PUBLIC_EXTENSION_CATALOG_URL. No production hostnames, DNS records, Worker mappings or external provider resources are changed by the import.