List Pending Approvals
The approval inbox: every proposed mutation still awaiting a human decision.
Overview
MCP tool list_pending_approvals — agent-callable, read-only. Handled by Approval Bus (command service — owns the queue)Approval Bus (command service — owns the queue)Servicev0.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 — its page shows the exact vendor fan-out.
Returns the public view of each pending proposal — the per-proposal widgetToken (the human-only execute secret) is stripped before anything reaches model-visible output.
This is the query side of the approval bus: it reads the same Proposal StoreProposal StoreContainerv0.1.0The shared CQRS database: every proposal, its payload, status transitions, decisions, results and per-card widget token....Ownervisionary-engineeringMapView docs the command side writes — Jesh’s shared-database CQRS, not a separate read store.
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.