Project Boundaries

Area	Owner	Notes
Storefront, checkout, catalog, customer account	Menzzo Magento	Customer-facing ecommerce behavior.
Orders, stock, shipments, refunds, marketplace sync	Logidav	Operational orchestration and integration jobs.
Support assistant, Dify workflows, chat wrapper	Menzzo Chatbot	Automates support flows through owned systems.

When a feature crosses boundaries, document both the owner and the integration contract.

How to use the boundary table

1. Identify the user or operator outcome, then locate the system that owns the behavior in the table.
2. Treat neighboring systems as collaborators only where a project page or shared flow documents a relationship.
3. Check whether the relationship is source-verified, documented, partial, or unknown before depending on a route, queue, file, or status transition.
4. For a change that crosses owners, ask each owner to confirm the contract and failure behavior. Keep one source of truth for the business decision.

For current evidence, follow the flow pages and documentation coverage. The shared map does not establish environment configuration, deployment state, or operational acceptance.