QMax Service Mesh — Architecture Catalog
The QMax platform as claude.ai sees it: queries direct, commands through the human-gated approval bus (CQRS, one shared store). One service per workflow, one flow per tool — every node below maps to a real code path inapps/service-mesh/src.
The mesh — QMax Operations
The MCP gateway, the per-workflow read services, and the approval bus + appliers over the shared proposal store. Click any node to drill in.
The outside world — External Systems
The claude.ai host, the Entra identity provider, and the five vendor platforms behind the connector layer.
Watch a tool call end to end
A read: Cash Flow Tracker
One query fanning into QBO + Fishbowl + ClaritySoft — direct request/response, no events (that's the CQRS point).
A command: Propose Vendor Bill
Queue → ProposalCreated → human approve → applier routes by PO linkage → vendor write → MutationApplied.
The generic gated write
The lifecycle every propose_* shares: nothing writes without a cleared human's click in the approval card.
Domain: QMax Operations
The CQRS split, how to read this catalog, and the code-generation (Atlas) mapping table.