# `presets/business/`

Business presets add **domain-shaped** features on top of stack presets — entities, routes, knowledge seeds, and workflows specific to a business model.

| Preset               | Status | Selected when `extends` contains... |
| -------------------- | ------ | ----------------------------------- |
| `portal-platform`    | stable | `portal-platform`                   |
| `crm-platform`       | stub   | `crm-platform`                      |
| `ecommerce-platform` | stub   | `ecommerce-platform`                |
| `pdpa-platform`      | stub   | `pdpa-platform`                     |
| `saas-platform`      | stub   | `saas-platform`                     |

Stubs ship as README only — they describe what the full preset _would_ materialize so teams can plan or contribute. Promote a stub to a full preset by adding `preset.json`, `manifest.md`, and the actual templates.

Conflict rules:

- A project should generally pick **one** business preset. Multiple are allowed, but `_init.ps1` will warn if two conflict (e.g. `ecommerce-platform` + `crm-platform` sharing entity names).
