MODULES.md section 9 puts a module- prefix in Composer package names that no published package uses

architecture/MODULES.md §9 gives five presentation-adapter rows the form:

| Filament presentation adapter | liberusoftware/module-{independent-module-name}-filament |

That module- prefix is inside the Composer package name, and no published package follows it.

Evidence

All 40 packages installed by boilerplate-laravel drop the prefix. The pattern throughout the fleet is:

The prefix is a repository naming convention, not a package one. §9's other rows (Product capability, Shared core, Aggregate distribution) are all conformant with what the fleet actually publishes — only the five adapter rows are not.

Why it matters now

ecommerce-laravel is planning ~100 module packages. Following §9 literally would publish liberusoftware/module-ecommerce-cart-filament alongside an existing fleet of liberusoftware/blog-filament-shaped names, and the namespace column compounds it: §9 gives adapters two-segment namespaces, while a mechanical derivation from the package name gives three.

The deviation is recorded as ADR 0004 in ecommerce-laravel, which is why this issue exists — the ADR is a disagreement with §9, and a disagreement that lives only downstream becomes that repo's permanent problem.

Ask

Correct the five adapter rows to match what the fleet publishes, or state explicitly that the fleet's 40 packages are the ones that are wrong. Either answer is actionable; the current mismatch is not.

Found while auditing ecommerce-laravel against the standards.

Read architecture/MODULES.md §9 and compare its five presentation-adapter rows with the package names used by the 40 packages installed by boilerplate-laravel. Check the downstream ADR 0004 for the recorded disagreement. Done means the rows match the published naming convention, or the documentation explicitly states that the existing fleet is incorrect.