Minimum Viable Offering
This document formalises the MVO for the VYR execution fabric. It defines what is included, what is explicitly excluded, the dependency order of assembly, and the deliverable that confirms the offering is complete.
1. Purpose of this document
MVO is not a product release. It is a technically verifiable substrate: sufficient for a first adopter to run reference workloads, inspect telemetry, and evaluate the portability claim without access to internal source.
Every component in the MVO either directly proves the central thesis or is a precondition for proving it. Anything else is out of scope.
2. Central thesis
One artifact, without code changes, executes across different environments with predictable state and observable telemetry.
The thesis is falsifiable. It maps directly to two measurable hypotheses — H1 (portability) and H2 (simplicity) — which are validated by the reference workloads and comparative benchmark.
3. What VYR is not
Not another orchestrator
Kubernetes organises clusters as control plane + worker nodes. VYR claims the execution fabric layer below orchestration — portable, vendor-neutral, offline-tolerant.
category: execution fabricNot a service mesh
Istio decomposes systems into control plane and data plane via proxies. VYR provides only the minimum secure transport required — no sidecar tax.
category: transportNot a cloud control plane
AWS Outposts, Azure Arc, and Google Distributed Cloud extend vendor control planes. VYR is the vendor-neutral substrate that runs across all of them.
category: substrateNot an agent framework
LangGraph and ADK orchestrate stateful agent workflows. KYX manages policy and causality over agent workloads — VYR provides the execution layer beneath.
category: infra layer4. Brand roles
| Brand | Role | Layer |
|---|---|---|
| VYR | Lightweight, portable execution fabric for distributed workloads | execution fabric |
| KYX | Systemic intelligence and control layer — models context, causality, and interventions over VYR | intelligence plane |