4 min readCalm pace · scan the outline anytime

Adopt in another project

How other repositories should use this site as the sole Modular Hexagonal DDD architecture reference.

Adopt in another project

This documentation site is the sole architecture canon for Modular Hexagonal Domain-Driven Design.

The standard is tool-neutral and AI-neutral: it does not require Cursor, any other AI assistant, or AI at all. Engineers adopt Core + the matching host adapter; assistants are optional helpers.

Other products — greenfield, brownfield, demos, or production hosts — should:

  1. Read Core here for framework-agnostic rules.
  2. Read the matching adapter (Adapters overview) for host wiring.
  3. Keep product backlog local (ROADMAP.md in that repo) — never mix feature IDs into architecture docs.
  4. To have an AI agent apply the standard, point it at the matching host apply URL (/laravel, /symfony, /yii, /codeigniter, /cakephp, /spiral, /slim, /mezzio) — see Apply playbooks. Assistant files are optional and covered per vendor inside each playbook.

Illustrative bounded-context names on this site are only Ordering, Warehouse, Directory, and Identity. Rename them to your domains. Do not treat any other repository’s product module tree as the architecture standard.

One-shot apply (for AI agents)

Apply Modular Hexagonal DDD from <ORIGIN>/apply/<framework>.full.md
AI assistant: <cursor|claude|gemini|copilot|generic|none>
Do not commit unless I ask.
FrameworkFile
Laravel 13/apply/laravel.full.md
Symfony 8.1/apply/symfony.full.md
Yii3/apply/yii.full.md
CodeIgniter 4.7/apply/codeigniter.full.md
CakePHP 5.4/apply/cakephp.full.md
Spiral 3.17/apply/spiral.full.md
Slim 4.15/apply/slim.full.md
Mezzio 3.28/apply/mezzio.full.md

Short URLs: /laravel · /symfony · /yii · /codeigniter · /cakephp · /spiral · /slim · /mezzio · /llms.txt

Paths depending on your situation

SituationStart here
AI agent should bootstrap this appApply index · pick host one-shot
New empty host project (humans)Greenfield bootstrap
Want the MUST checklistPortable requirements
Want folder intuitionWhere does this code go?
Host mapping detailsAdapters overview
End-to-end mental modelOrdering ↔ Warehouse cookbook · Identity ↔ Directory
No framework yetPure PHP + PSR skeleton
AI layout examples (optional)Using AI assistants

What stays in the consuming repo

ArtifactRole
Project ROADMAP.mdDelivery backlog with stable IDs
Host composer.json / app bootstrapFramework wiring
Module code under that product’s domainsBusiness implementation
Optional local README pointerLink to this site + Core / adapter version

What must not become “the standard”

  • Product module catalogs from any application repo
  • Feature / GAP backlog rows
  • Shop-specific seeders and journeys
  • A second long architecture README that contradicts this site
  • A requirement to use a particular AI product

Architecture rules and greenfield patterns belong here; product features belong in each application.

Modular Hexagonal Domain-Driven Design
Core 1.0.0-draft