Overview

A propose_* command queued a mutation: a Proposal now exists in status pending with a freshly-minted per-card widget token. The approval card renders from this.

Implementation note: today this “event” is a state transition on the proposal row in the Proposal StoreProposal StoreContainer•v0.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 the Proposal TypeScript model (an Atlas/code-generation candidate).

Architecture diagram