flow

Cash Flow Tracker — tool-call lifecycle

One cash_flow_tracker call end to end: the query hits CashFlowService, which fans into QBO + Fishbowl + ClaritySoft in parallel and assembles the unified cash view. No events — reads are direct.

Flow

Overview

The answer to “what is it querying specifically”: three parallel vendor reads, one assembled view. A query never touches the event system — that is the CQRS split; contrast with any command flow (e.g. Propose Vendor Bill — command lifecyclePropose Vendor Bill — command lifecycleFlowv0.1.0One propose_vendor_bill call end to end: queue → ProposalCreated → human approve → ProposalApproved → applier routes by ...Ownervisionary-engineeringView flowView docs).

While Fishbowl is absent (the connector long pole), the inventory branch degrades: openOrders omitted, unavailableSources: ['fishbowl'], divergence alert suppressed — never a failed tool call.

The flow

How it works

  1. Max (agent) on claude.ai → MCP tool call
  2. Cash Flow Tracker → direct request/response — no events
  3. CashFlowService → cash position + AR/AP aging / open SO/PO / weighted pipeline
  4. Accounting Read → vendor API
  5. Inventory Read → vendor API
  6. CRM Read → vendor API
  7. QuickBooks Online → results fold in
  8. Fishbowl Inventory → absent → degraded: openOrders omitted, marked unavailable
  9. ClaritySoft CRM → results fold in
  10. CashFlowView assembled → returned in the tool result (divergence + runway alerts; direct response — no event lifecycle on reads)