Skip to content

Module vocabulary

The Lowerarchy names for the commerce responsibilities of Seams Pantry and their current homes.

Module vocabulary ​

The Lowerarchy names make responsibility legible. They describe ownership independently from package layout and deployment.

ModuleHuman meaningCurrent implementation homeRuntime boundary
Commerce engineCoordinates transactional commerceservices/commerceIndependent service and database
ContractsDefines shared commerce languagepackages/contractsCompiled into Pantry and consumers
Sous ChefOperates the merchant businessservices/platform/src/data/merchant-agent-skills.ts and Pantry agent configurationPantry runtime
Commerce Read LayerRecords projections, queries, and operational historyOrganisationActor projections and CommerceGraphReader sources in services/platformPantry runtime
PunterBuys and proves the system through acceptance journeysscripts/punterCLI and CI harness

Pantry hosts the organisation control plane, provider connections, Cases, agent sessions, approvals, tools, merchant console, Sous Chef behavior, and the Commerce Read Layer. The commerce engine or Shopify remains the selected commerce authority.

Boundary rule ​

A named module becomes a separate deployment only when its authority, scaling, security, or release lifecycle requires that boundary. Components communicate through authenticated versioned APIs and signed events. They never import another runtime's database or private source.

Why the names matter ​

The vocabulary prevents two common mistakes:

  • treating a projection as a second writer; and
  • treating a product role as a deployment requirement.

Use the service map for the concrete repository layout.