HALO CRM research
Real and working
Domain 9 · content · ~2,300 LOC

Customs tracker

Tracks custom content orders through status transitions. customStatusHistory is the ONLY history-shaped table in the entire 56-table schema.

What it is and how it feeds the rest

Mechanically

Tracks custom content orders through status transitions. customStatusHistory is the ONLY history-shaped table in the entire 56-table schema.

How it connects

Consumes creator identity; order value should feed the money domains.

Worth knowing

2,209 LOC across 21 files and nobody has yet explained what 'customs' means in this business, or whether its status-history pattern is the audit-trail primitive the rest of the app is missing.

Pages

  • src/pages/CustomsTracker.tsx

Components

  • src/components/customs/

Convex modules

  • customs.ts

Tables

  • customs
  • customStatusHistory

Open questions

Research priority for this domain is highest. Agent findings splice in below this line and survive regeneration.