Architecture: Multi-vertical module registry & composition engine

[khaira777]

Multi-Vertical Modular Architecture Proposal

Extracted from fork codewithsharma/FloCafe (branch: modular-verticles):

Overview

Evaluate adding a formal module catalog, registry, and composition engine ("Opervia Platform" design pattern) to decouple restaurant features from core POS capabilities, enabling multi-vertical deployments (such as retail POS).

Proposed Changes

1. Module Registry & Composition Engine:
   • Module catalog, capability definition, and composition snapshot engine (main/modules/catalog.ts, main/modules/registry.ts, main/modules/composition.ts).
2. Frontend Composition Hooks & Settings Gating:
   • Expose platform composition API hook (usePlatformComposition) to dynamically gate UI components and settings tab panels based on active modules.
3. Reference Architecture Docs:
   • docs/14-decisions/ADR-010-opervia-platform.md and docs/modules/README.md.

[khaira777]

Verdict: NOT APPLICABLE TO FLOCAFE as proposed — needs maintainer decision if a platform direction is ever considered

Findings:

• FloCafe is a single-vertical, local-first POS. There is no module catalog/registry/composition engine on main, and other verticals (FloRetail, FloSalon, …) are separate repositories — a multi-vertical composition engine inside FloCafe would duplicate the product boundary instead of serving FloCafe.
• Repo guidance (AGENTS.md) explicitly says not to expand the project just because another product or project has a feature.

No conflicting code exists (it's purely additive), but as filed this is not actionable for FloCafe. If maintainers are exploring a platform/registry direction, that should be a separate decision with an ADR before any issue work. Suggested action: close as not-applicable or hold behind the platform decision.