Menzzo Chatbot

Purpose

Menzzo Chatbot spans the customer-facing UI, business API backend, and logs API. Dify provides conversation orchestration.

Components

Component	Repository	Documentation
Chat UI	axelites/menzzo-chatbot-ui	UI overview
Business API backend	axelites/menzzo-chatbot-backend	Backend overview
Logs API	axelites/menzzo-chatbot-logs	Logs overview

Connected Systems

Evidence is partial: the UI-to-Dify stream, conditional answer-cache request, backend SAV API, and backend service integration points below have source references at immutable commits. The workflow-failure client and logs API references were not re-read in the latest bounded audit. Active endpoints and enabled integrations depend on environment configuration.

Connection	Responsibility	Source
UI → Dify	Sends chat requests to the configured /chat-messages API.	Chat route
UI → backend	Stores general product-question answers through /api/v2/products/general-question-answers/store.	Cache client, backend routes
Backend → Logidav	Verifies order details through the configured Logidav client and creates SAV tickets through the configured /sav path.	Order detail client, SAV request path
Backend → Logidav SAV API	Posts SAV requests to the configured Logidav base URL plus /sav; caller/UI coverage is not established.	SAV client, Logidav endpoint
Backend → Magento	Calls the configured Magento REST API through MagentoApiService.	Magento client
Backend → logs API	The existing documentation links a /workflow-failures client; the client file was not re-read in the latest bounded audit.	Existing code reference — documented, not re-verified here
Logs API → PostgreSQL	Existing docs describe queries over Dify conversation, message, and workflow records; implementation and bounded-query behavior remain unverified in this audit.	Existing implementation reference, existing query reference — not re-read

Keep endpoint contracts in the owning repository's integration documentation. Start with the backend's Logidav integration guide and Magento integration guide.

For SAV responses, use the shared SAV status contract. It distinguishes SAV acceptance from final validation, separates case status from refund/payment status, and records the implementation and deployment boundary.

See the repository map for each project's documentation submodule path.

Dependencies

Connected Systems separates the checked UI/backend paths from logs relationships carried forward in documentation but not re-read by the current source audit. Environment configuration still determines active endpoints and integrations.

Setup

Application setup is not established by this page. Follow the owning repository's README and setup instructions, and request the approved local access or environment you need. The shared documentation submodule and docs-site commands are described in the repository map and local development guide; they do not start this application.

Flows

The Chatbot to business API page separates the Dify conversation path from the conditional product-question answer path. See Support and refunds for customer case ownership; that broader lifecycle remains partial.

Diagnosis

Use the source links in Connected Systems to identify the component responsible for the failing edge. A successful Dify response, backend response, or log query proves only that component's response; it does not prove completion of a downstream commerce action.

Evidence and gaps

The UI-to-Dify request, conditional product-answer cache path, backend-to-Logidav SAV path, and configured Magento/Logidav service integration points are source-verified at the pinned commits. The logs API and workflow-failure query are not re-verified by this source packet. The SAV request caller, environment-specific enablement, full end-to-end owner acceptance, common retry/idempotency behavior, and operational runbooks remain unverified.

Next evidence to add: source commit and file references for the owned boundary, then repository-specific setup and the relevant operations procedure. See the documentation coverage matrix for the system-wide gap record.