VNX is not a SKU you buy—it is how we subdivide responsibilities so engagements stay coherent. Clients touch AI Operations first; utilities and diagnostics roll up under Tools; customer-facing surfaces under Apps/marketplace; writing and narrative under Insights; speculative work stays labeled Labs until it earns a prod path.
If routing is blurry, engagements blur. Pillars exist so scopes, URLs, and subdomains trace back to named layers—rather than burying forty routes under one “Products” dropdown.