Module Composition Guide

Modes

• Soft-disable: keep module code, gate runtime exposure with env flags.
• Hard-remove: permanently prune module slices/contracts/routes after scope is stable.

Soft-disable examples

Backend flags:

BACKEND_MODULE_BILLING_ENABLED=false
BACKEND_MODULE_WALLET_ENABLED=false

Frontend flags:

VITE_MODULE_BILLING_ENABLED=false
VITE_MODULE_WALLET_ENABLED=false

Hard-remove sequence

1. ship with module soft-disabled
2. remove frontend feature/routes
3. remove backend module + router bindings
4. remove contract sections
5. apply data migration plan if needed
6. update docs + roadmap in same PR

For full details and profile presets, see docs/guides/module-composition.md.