VYR MVO — Roadmap

Full roadmap 2026–2029

0–6 mo
2026-05
2026-10

Phase 1 · This document

MVO — Single-node runtime

VYR runtime kernel, artifact model, ephemeral state, Control API v0, OTel instrumentation, CLI/SDK alpha, reference workloads × 3 environments, comparative benchmark.

MVO scope whitepaper v0.1 H1 portability H2 simplicity

6–12 mo
2026-10
2027-04

Phase 2

Multi-node fabric + state kernel

3-node fabric, eventual and strong state (CRDT + Raft), OCI runtime path, fault harness, partition resilience experiments.

engineering report v0.2 H3 partition resilience H4 state continuity

12–18 mo
2027-04
2027-10

Phase 3 · KYX begins

KYX context graph + advisory mode

Topology model from accumulated VYR telemetry, event replay, decision explanations. KYX starts in advisory-only mode — no automation.

systems preprint on VYR context graph v0 causal engine advisory

18–24 mo
2027-10
2028-04

Phase 4

Simulator + controlled action loop

simulate/apply API, rollback logic, audit trail, fault injection. Intervention precision measurement. H5 and H6 validation begins.

paper on causal orchestration H5 decision quality H6 safety

24–30 mo
2028-04
2028-10

Phase 5

Air-gapped + production hardening

Disconnected sync policies, offline benchmark suite, air-gapped packaging, HA, automated failover.

benchmark report offline benchmark suite

30–36 mo
2028-10
2029-04

Phase 6

Spec v1 + conformance suite

Spec freeze, conformance suite, partner/operator nodes, external validation. This is the point at which VYR moves from internal system to standard surface.

whitepaper v1 conformance paper spec v1.0 certification tests operator handbook

Publication stack

Publication	Content	Phase
Whitepaper v0.1	Execution fabric model, consistency classes, policy model, security model, MVO results	Phase 1 · MVO
Systems paper	Why not another orchestrator — latency, operability, portability results against baseline	Phase 3
Causality / orchestration paper	Advisory causal control, intervention safety, replay and counterfactual selection	Phase 4
Spec and conformance report	Standard surface definition; enables third-party operators and external certification	Phase 6

Explicit non-goals (MVO scope)

ℹ The following will not be addressed in Phase 1 and should not be evaluated as gaps.

Multi-environment cluster coordination · Automated failure recovery · Policy enforcement and audit · Causal analysis and intervention · Production SLA guarantees · Kubernetes API surface compatibility · Full service mesh capability · External registry or artifact distribution

✓ This document is the authoritative reference for MVO scope. Changes to scope require a version increment and explicit changelog entry.

Roadmap & Phases

Full roadmap 2026–2029

Publication stack

Explicit non-goals (MVO scope)