Node-Boot project type: simple repo vs. monorepo

This is a structural decision, separate from (and prior to) picking a server adapter or starters — make it first for any brand-new project. Node-Boot itself doesn't force either shape; both are just conventions demonstrated by full, production-grade reference repos (not the minimal samples/* in the node-boot monorepo, which only demonstrate one adapter/feature in isolation).

Decide

Ask: does this project deploy as one service, or several independently-deployable services that talk to each other?

• One deployable app (a single API, regardless of how many features/starters it uses) → simple repo.
• Multiple services that each have their own app-config.yaml, own database, own deploy pipeline, and call each other over HTTP (or need shared workspace tooling — lint/tsconfig/CI — across services) → monorepo.