Consolidate methodology v0.1 (~25K words) to v0.2 (~16K), turning the un-versioned methodology IP into a versioned, meta-layered asset with Delphi validation queued toward v1.0. Sequenced first because everything downstream depends on it: authoring-MCP scope (M3), cohort curricula stabilization, and the IAM migration window (M2) all key off a frozen v0.2. In VSM terms it hardens S2 (standards/canon) and closes the 'methodology IP un-versioned' live gap, giving the VVDOC contract a stable payload. Big-4 archetype-methodology productization makes the v1.0 timeline pressure real. Horizon: 90 days; in flight.

Migrate the self-built Node IAM to a commodity provider (Auth0/Clerk), porting the federated permission model and re-issuing tokens across operate, workshop, and AIT. It is the classic Wardley anti-pattern — Custom where Commodity exists — and buying it back frees scarce senior-operator hours for the moat work. Deliberately deferred until M1 closes to avoid paying migration cost twice; it stabilizes the iam-JWT contract (one of the five suite contracts) and, as a co-benefit, forces retirement of operate's presence-gated auth. This is S2 hygiene that de-risks every S1 tool. Horizon: ~6 months, gated on M1.

Ship the 7-verb authoring MCP (generate / insert / edit / apply_brand / render / validate / publish) on top of the brand-emitting design system and format adapters; GUI editor deferred to v2. Sequenced after M1 because the MCP authors against versioned methodology IP — without v0.2 frozen, the orchestrator has no stable canon to compose from. It stands up the second moat and operationalizes the VVDOC contract, effectively giving S3/S4 a production arm: sensed insight becomes branded, multi-format client artifact without senior hours per artifact. No obvious commercial equivalent exists for the MCP + brand-emitting-DS + multi-format combination. Horizon: ~12 months.

Standardize the 4–8 week diagnostic into a fixed-price, repeatable-scope productized intake — the map's cleanest Custom → Product transition (engagement-shape-flexibility drifting right). It sits last because it consumes everything upstream: versioned methodology (M1), reclaimed operator capacity (M2), and MCP-authored deliverables (M3) are what make a diagnostic repeatable without diluting quality. Strategically it is the S1 mouth of the B2C2B loop — a low-friction entry product that converts radar/cohort-sensed prospects into engagements and reduces sales-cycle variability. Explicit trigger: after two Lighthouse engagements close with a repeatable diagnostic shape. Horizon: 12–18 months.

Product naming moves to plain product names: operate becomes Transform (working name), sensing becomes Monitor. The internal SENSE/REASON/EXPRESS verb taxonomy stays an architecture concept but is dropped from user-facing UI — clients buy tools, not epistemology. Repo and infrastructure renames are deferred to a cleanup pass, as with the earlier engege→operate rename.

Each client engagement gets its own isolated reasoning graph, optionally augmented with read-only market-intel overlays — never merged into a shared graph across clients. This preserves confidentiality by construction, makes client offboarding a delete/export, and keeps the market-intel layer reusable without contaminating it with client IP. Validated by the Dr Max engagement structure and the three-KG architecture.

v1 integration between Workshop and delivery tooling is a manual JSON/CSV export/import cycle, not a live service-to-service API. Workshop has no formal external auth model today, and a real S2S contract is a cross-repo project that would stall v1. The proper API integration is specced as a v1.5 deliverable; accepting the manual bridge is a deliberate ecosystem-light trade.