Overview

src/workflows/vendor-bill/vendor-bill.applier.ts. Receives Proposal ApprovedProposal ApprovedEvent•v0.1.0A cleared human approved in the card (app-only commit path, RBAC-checked against the authenticated session).Ownervisionary-engineeringMapView docs dispatched by kind (vendor-bill-intake) from 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 — in code this is a synchronous by-kind dispatch inside the commit path, not a broker subscription (see the event’s implementation note). The two-path rule from vendor discovery, routed at apply time by routeVendorBill: PO-linked → 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 (dated with the warehouse receipt date; Fishbowl auto-pushes to QBO); non-PO → QBO Create BillQBO Create BillCommand•v0.1.0Creates a vendor bill in QuickBooks (the non-PO path of vendor-bill intake).Ownervisionary-engineeringMapView docs. The Fishbowl path degrades to a structured failed proposal while the connector is absent — never a crash.

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 (from Propose Vendor BillPropose Vendor BillCommand•v0.1.0Workflow #1 — AP intake. Queues a vendor bill as a PENDING proposal; nothing is written until a cleared human approves i...Ownervisionary-engineeringSchemaMapView docs to the vendor write).

Architecture diagram