The ~20 repos are not a portfolio of apps but a single Business OS read through the Viable System Model: S5 = founders + methodology canon + brand; S4 = Monitor/sensing + evidence graph; S3 = vv-ops + delivery + backlog; S2 = vv-standards + catalog + iam + design-system; S1 = client engagements tooled by Transform, Workshop, Engage. The same organs recur at three scopes — suite, market, client — which is VSM recursion, not metaphor.

The suite composes through exactly five contracts: (1) iam-JWT for identity, (2) catalog entity/slug for shared vocabulary, (3) "signal" for the sense→reason seam, (4) VVDOC for documents, (5) engagement-graph export for delivery data. Everything else is a repo-local decision. Contract (3) is the only one not yet built — it is the keystone gap, and its absence is what keeps sensing disconnected from reasoning.

The suite deliberately maintains three separate knowledge graphs: sensing (radar) for market signals, evidence (AIT) for the public evidence-claim graph, and reasoning (operate) for per-engagement strategy graphs. They connect via typed handoffs (the signal contract, read-only augmentation), never via a merged uber-graph. Merging would destroy provenance boundaries and couple client IP to public data.