Mapping the estate onto VSM, S1/S2/S4/S5 all have live or dev-stage tooling, but S3 — the organ that turns sensed opportunity and strategic intent into sequenced, resourced operations — is fragmented across stale vv-ops prose, a flat 72-row capability-ask registry, and a not-yet-built Engage. A viable system with a hollow S3 senses and reasons well but cannot manage itself; this is where the next build cycle must concentrate (ENGAGE + HR-SYS are the S3 frontier).

The suite graph (27 nodes / 112 edges) recovers a real B2C2B feedback loop as a strongly-connected component: public content attracts clients, client work generates evidence, evidence feeds public content. But the loop is broken in practice because RADAR is only proposed and the signal contract is unbuilt — sensed market signals cannot flow into reasoning or content. Shipping radar/signal is the single highest-leverage act for making the flywheel real; propagation cost across the graph is 20.8%.

operate's identity: strategy→analysis with live artifacts across four substrates — Graph (DSM/BDN/OST), Space (Wardley/AIR), Dynamics (stock-flow/ToC/diff-in-diff), Category (Cynefin). It is explicitly not a document generator (that is doc-studio's job). But as the REASON node it has no sensing input: nothing feeds it external signals, so all reasoning starts from manually-entered state. It reasons in the dark until the signal contract connects it to Monitor/radar.