ERP AtlasDocs

Guides

Production release — 9 October 2026

All forty catalog repositories and the shared editor shell package were committed and pushed to their private GitHub repositories.

All forty catalog repositories and the shared editor shell package were committed and pushed to their private GitHub repositories. All forty catalog Workers were deployed with their active versions receiving 100% traffic.

Published hierarchy

Catalog Total records Imported source records
ERP 1,226 861
Applications 2,367 2,367
Extensions 4,754 4,734

The ERP source records comprise 72 industry ERP variants and 789 Micro-ERP configurations. All 41,080 directed relationship targets resolve against production API records, including their canonical IDs, slugs and names. Imported configurations retain Reference status and unverified readiness. Remote D1 migration chains were applied, and migration replay preserves existing record fields.

Example navigation: ERP → Micro-ERP → Application → Extension.

Release verification

  • Production bundles and Wrangler packaging checks completed across all forty catalogs.
  • Live inventory/API and deployed CSS checks passed for all forty catalogs. Thirty-two populated catalogs have a representative detail response checked; eight empty catalogs have their homepage and detail-template styles checked.
  • Eight representative detail pages passed Chrome checks at 390px and 1,440px with no horizontal overflow: ERP, Micro-ERP, application, extension, toolkit, editor, website and directory.
  • Existing local validation includes forty TypeScript checks, changed-detail/config lint checks, 62 unit tests, full source validation and SQLite migration replay.
  • Thirty-nine missing configured R2 buckets were provisioned. They are newly created empty storage resources; this release does not restore previously removed objects.
  • Five catalog hostnames use exact Worker routes and proxied DNS records within the existing custom-domain quota: chatbot, communication, gateway, scheduler and subscriber. Existing unrelated DNS records and domains were preserved.

Public DNS was checked through Cloudflare and Google resolvers. Three new hostnames initially remained negatively cached by the local resolver; their HTTPS/API checks used public resolver 1.1.1.1 with normal TLS verification. The hierarchy's existing hostnames were verified through ordinary browser navigation and API requests.

Detailed deployment IDs, source commits, traffic percentages, migration inventories and live measurements are saved in the local Catalogs workspace under .deploy-logs/erp-hierarchy-2026-10-09/. The local verification JSON is a historical snapshot from before this production rollout.

ERP browsing follow-up

The catalog now exposes three prominent record-type filters: All types, ERP, and Micro-ERP. ERP includes industry ERPs, existing ERP Suites and Functional ERPs; Micro-ERP includes imported configurations and existing reusable Micro-ERPs. The current inventory splits into 198 ERP records and 1,028 Micro-ERP records. Record-type filtering composes with search, domain, readiness, priority, saved items and pagination; cards display their type.

Opening an ERP shows every linked Micro-ERP in a dedicated section immediately below the hero navigation. This section is not truncated or paginated, includes existing reusable capabilities, and links to their detail pages. ERPs without documented Micro-ERP relationships show an explicit empty state. Applications and extensions remain available in Connected records, and Micro-ERP pages retain their parent ERP and downstream links.

Validation: TypeScript, full lint, production OpenNext build, Wrangler packaging, classification and composition checks for all 198 ERPs, and local browser checks for both filters and all 15 Retail ERP Micro-ERPs.

Compact names with full context

ERP, Micro-ERP and application cards and detail headings now use compact display names. The complete canonical name remains visible directly underneath, including in parent links and connected-record cards across ERP, application and extension catalogs. Full names, IDs, slugs and canonical relationship targets are preserved. Search accepts both compact and complete names.

Short name metadata covers 3,451 records, including existing reusable Micro-ERPs. The generator scripts/add-display-names.py is repeatable and runs after the hierarchy import. Migration 0020_add_short_display_names.sql in the three catalogs merges only compact-name and relationship-display metadata. Examples: Retail ERP / Retail Management ERP; Counter Sales & Billing / Grocery Retail Counter Sales and Billing Micro ERP; Billing Operator / Grocery Retail Billing Operator App.

Application configuration context

Application card and detail titles now use Micro-ERP: short application name. Cards retain the full canonical name and additionally show parent ERP, parent Micro-ERP, role and the exact source workflow context. This distinguishes configurations sharing a role-app pattern, such as Client Books & Reconciliation: Bookkeeping and Finance & Receivables: Bookkeeping. Application links throughout ERP, Micro-ERP and extension detail pages use the same contextual titles. Search includes the prefixed title as well as the full canonical name.

No record merge, rename or database migration is needed for this presentation change. The list projection carries only the two parent references rather than the full relationship graph. Validation checked all 2,367 application projections and their contextual titles across ERP and extension relationships.

Last updated 2 November 2026