Slim adapter
| Host | Slim 4.15.x |
| PHP | 7.4+ (use 8.2+ in practice) |
| Researched | 2026-08 |
| ORM / persistence | Chosen by you (Doctrine DBAL/ORM, PDO) — always Infra |
| Composition root | PHP-DI / Container definitions + route definitions |
| Async | Queue worker of your choice (e.g. Symfony Messenger component, bernhard/… ) |
| One-shot apply | /apply/slim.full.md |
| Short URL | /slim |
Slim is a host, not Core. Domain and Application stay framework-agnostic; the pages below map Core roles onto Slim APIs.
Topic pages
- Persistence — Chosen by you (Doctrine DBAL/ORM, PDO) — always Infra quarantine
- Composition root — PHP-DI / Container definitions + route definitions
- Cross-module bridges — ACL + async
- UI delivery — Route callables / Action classes
- Tooling — tests, SA, style
- Migrations — schema ownership
Design test
If the peer module is deleted and replaced by HTTP, does Application/Domain still compile?