Greenfield bootstrap
Checklist for starting a new host project on Modular Hexagonal Domain-Driven Design. This site is the architecture source of truth — keep only host wiring and product backlog in the consuming repository.
The architecture is AI-neutral. Bootstrap succeeds with humans and ordinary tooling; AI assistants are optional.
If you are porting existing modules, keep standards from here, but plan a separate migration of code and quality gates (boundary tests, formatter, static analysis).
1. Point the team here
In the new repo’s root README (short pointer is enough):
Architecture standard: Modular Hexagonal Domain-Driven Design
Canonical docs: <URL of this site> (Core 1.0.0-draft)
Host adapter: <URL>/v1/adapters/<host>
# <host> = laravel | symfony | yii | codeigniter | cakephp | spiral | slim | mezzio
2. Documents in the new repo
| Keep locally | Notes |
|---|---|
| Thin README pointer | Links to this site; optional host-only deltas |
ROADMAP.md | Product delivery only — not architecture essays |
| Optional PRD | Product/stack notes; MUST architecture rules must match Requirements |
Do not maintain a long divergent architecture essay if it contradicts this site.
3. Code skeleton
- Create the host application (any supported host — see Adapters).
- Add module root + Shared root to PSR-4 autoload.
- Start Shared empty — promote technical ports on second use (
Clock, transactions, event dispatch, …). - Add architecture boundary tests (assertions are Core MUST; commands live on each host’s Tooling page).
- Scaffold the first module (host generator or manual folders + composition root registration).
4. Optional — AI assistant rules
Only if your team uses an AI coding assistant: prefer the host apply playbook (one-shot *.full.md for your framework). It covers Cursor, Claude, Gemini, Copilot, and generic layouts. Also see Using AI assistants and the optional assistant pack. This step is not required for architecture compliance.
5. Definition of done for “bootstrap complete”
- Boundary / arch test green with ≥1 sample module
- Formatter + test commands documented for the host
- README links to this site as canonical Core
- No unrelated product-module trees treated as the architecture standard
- (Optional) Assistant rules pack installed if the team uses AI tools