Cultivation, inventory, compliance execution, fulfillment, dispatch, delivery, and point-of-sale operations.
The map
What Herbert is made of.
The declared shape of the platform: zones, the features inside them, and the surfaces, capabilities and deployments each one rests on.
Zones
The broad territories every feature lives in.
Customers, pricing, wholesale, proposals, orders, invoicing, accounts receivable, procurement, and supported financial workflows.
Identity, organizations, facilities, users, app access, invitations, platform configuration, provisioning, and superadmin inspection.
Public discovery, education, business profiles, and customer entry points.
No features declared yet.
AI-assisted operations, automation, communication, and orchestration.
No features declared yet.
Capabilities
The atomic things Herbert can do, which features bind. Grouped by domain.
Admin 2
Commerce 8
Compliance 1
Cultivation 5
Messaging 2
Operations 4
Platform 4
Security 1
Deployments
The independently deployed applications that serve it all, by owning domain.
Commerce 9
Intelligence 3
Operations 14
Platform 7
Public 3
Seams
Declared journeys from one deployment to another.
- platform.admin-to-commerce.invoicesA declared journey from admin-web to a surface on sales-web. Declared topology only — not a permission grant.
- platform.superadmin-to-payments-control-planeA declared journey from superadmin-web to a surface on payments-web. Declared topology only — not a permission grant.