Section 3
MVO Scope
What is included, what is explicitly excluded, and why. The exclusion list is as important as the inclusion list — it must appear verbatim in Whitepaper v0.1.
3.1 What is included
| Component | Description | Boundary |
|---|---|---|
| Artifact Model | Digest-addressed artifact with signature verification | Local storage only; no registry service |
| VYR Single-node Runtime | Wasm/WASI execution on a single node | No multi-node, no placement engine |
| Ephemeral State | Single class of state bound to task lifecycle | No eventual, no strong consistency |
| Control API v0 | submit_task, cancel_task, create_state, bind_state, stream_traces, stream_metrics |
No apply_policy, simulate_action, explain_decision |
| OTel Instrumentation | Traces and metrics on critical paths via OTLP | submit → execute → complete only |
| CLI / SDK alpha | Thin wrapper over Control API v0 | Sufficient for reference workloads; not production-grade |
| Reference Workloads | 2–3 workloads × 3 environments | event transform + disconnected collector |
| Comparative Benchmark | Same workloads on baseline stack | K8s + job runner |
| Whitepaper v0.1 | Technical document of what was built and measured | Includes explicit non-goals section |
3.2 What is explicitly excluded
The following are out of scope for MVO. Their exclusion is intentional and must be stated in Whitepaper v0.1.
| Excluded | Reason | Phase |
|---|---|---|
| KYX (all components) | Requires accumulated telemetry history that does not exist at MVO stage | 12–18 months |
| Multi-node fabric | Adds coordination complexity without new proof for the portability thesis | 6–12 months |
| Eventual and strong state | Require Raft and CRDT implementation; separate phase | 6–12 months |
| Service mesh functions | No sidecar proxies, no L7 routing, no inter-service mTLS | not planned |
| Kubernetes API compatibility | Dilutes positioning; increases surface without strategic gain | not planned |
| Production hardening | HA, automatic failover, SLA guarantees | 24–30 months |
| OCI runtime (full path) | Compatibility stub only; not a supported execution path at MVO | 6–12 months |
The exclusions above should not be evaluated as gaps. They are architectural decisions with explicit rationale. Any evaluator reading Whitepaper v0.1 should encounter this list before forming a judgment about completeness.
3.3 Control API v0 — surface definition
The API surface is fixed at this layer. Additions after the freeze point propagate across CLI, SDK, and test harnesses.
# Artifact put_artifact(digest, manifest, signature) # Execution submit_task(artifact_digest, input_ref, state_bindings[], resources) cancel_task(task_id) # State create_state(name, class=ephemeral) bind_state(task_id, state_id, mode=ro|rw) # Observation stream_traces(filter) stream_metrics(filter) # ─── NOT in MVO ──────────────────────────────── # apply_policy → KYX surface # simulate_action → KYX surface # explain_decision → KYX surface