Development workflow

This is the API workflow that the scripts and AGENTS.md support. Release tagging for the three apps is unknown.

Change a feature

1. Find the feature folder under src/modules/<area>/<feature>/. See the code maps on domain pages.
2. Keep the write path, the outbox enqueue, and the state-machine check in the same transaction when the change has a side effect.
3. If you add a table, classify it in the tenancy extension and add a migration. See Adding an entity.
4. If the route is not for every authenticated user, add @RequirePermissions. Omission means allow.
5. Pair a test under test/.
6. Run yarn architecture:check and yarn verify.

Change a state machine

Transition legality is TypeScript, not a Postgres trigger. The order map is duplicated in two files. Update both, or they will drift:

• commerce/order/services/order-state-machine.ts
• commerce/order-status/domain/order-state-machine.ts

They matched on 2026-10-01. The header comment is narrower than the map. Do not copy the comment into a ticket as the spec. Update Order state machine in this docs site in the same change.

Change an integration

Add the provider under src/integrations. Marketplace classes must match the auto-registration names or they will not register. See Adding an integration.

Docs

Significant architectural or business-logic changes must include the matching page in pointnxt-developer-docs. See the docs repository CONTRIBUTING.md.