Mutation Applied
The approved mutation executed against its vendor system; the applier's result (e.g.
Overview
The approved mutation executed against its vendor system; the applier’s result (e.g. the created QBO Bill) is recorded on the proposal. Terminal status applied.
Implementation note: today this “event” is a state transition on the proposal row in the Proposal StoreProposal StoreContainerv0.1.0The shared CQRS database: every proposal, its payload, status transitions, decisions, results and per-card widget token....Ownervisionary-engineeringMapView docs (status enum
pending → approved/rejected → applied/failed), observed by hosts via tool results and the card refresh — there is no broker. If a real consumer appears (webhooks, portal inbox, audit sink), emitting these as first-class events is the natural seam — and their payloads are directly derivable from theProposalTypeScript model (an Atlas/code-generation candidate).