Overview

MCP tool propose_vendor_bill — agent-callable, but it only queues: it creates a pending proposal (Proposal CreatedProposal CreatedEvent•v0.1.0A propose_* command queued a mutation: a Proposal now exists in status `pending` with a freshly-minted per-card widget t...Ownervisionary-engineeringMapView docs) on the Approval Bus (command service — owns the queue)Approval Bus (command service — owns the queue)Service•v0.1.0The command side: owns the proposal queue. propose_* only queue; a cleared human approves in the card; only then does th...Publishesproposal-created, proposal-approved +3Subscribespropose-vendor-bill, propose-bill-date-correction +6Ownervisionary-engineeringMapRepoView docs and returns the approval card. No vendor write happens here. Watch the full lifecycle: Propose Vendor Bill — command lifecyclePropose Vendor Bill — command lifecycleFlow•v0.1.0One propose_vendor_bill call end to end: queue → ProposalCreated → human approve → ProposalApproved → applier routes by ...Ownervisionary-engineeringView flowView docs.

On approval VendorBillApplier — AP intake (workflow #1)VendorBillApplier — AP intake (workflow #1)Service•v0.1.0Applies an approved vendor bill by PO linkage: PO-linked bills import into Fishbowl (auto-pushes to QBO); non-PO bills p...Publishesqbo-create-bill, fishbowl-import-billSubscribesproposal-approvedOwnervisionary-engineeringMapRepoView docs routes by PO linkage (the two-path rule from vendor discovery): PO-linked bills import into Fishbowl (Fishbowl Import BillFishbowl Import BillCommand•v0.1.0Enters a PO-linked vendor bill in Fishbowl (dated with the warehouse receipt date), which auto-pushes to QBO.Ownervisionary-engineeringMapView docs, auto-pushes to QBO); non-PO bills post directly to QBO (QBO Create BillQBO Create BillCommand•v0.1.0Creates a vendor bill in QuickBooks (the non-PO path of vendor-bill intake).Ownervisionary-engineeringMapView docs).

Response shape note (CQRS): the tool returns the public pending proposal (id, kind, summary, status) so the host can render the approval card — the command’s real “return” is the proposal id; the mutation result only ever exists on the proposal record after a human approves.

Reading this page: a message page renders its contract and its one hop — who sends it, who receives it (that is EventCatalog’s grain: message = contract). The service page shows this workflow’s full fan-out (its sends); the flow shows the lifecycle step by step.

Input schema

Architecture diagram