Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Skip to content vxedge docs GitHub

Roadmap

Where vxedge stands, phase by phase. The full phase definitions are in ARCHITECTURE.md §15, and the measured results are in RESULTS.md. Per-repo work items live in each repository's own TASKS.md.

References elsewhere in this repository to numbered program-board items (#14, #28, …) and dated state snapshots point to the maintainers' internal working board. This page is the public summary of that board.

Phase status

The phase, track and delivery states below are registered in FACTS.md; change them there first.

PhaseGateStatus
1 — slicing core, API-firstReproducible H1/H3/H4 numbersGate passed. All three hold and were independently reproduced. See RESULTS.md
2 — real slices & workloadsH2: S-NSSAI vs static VLANGate passed. H2 holds and was reproduced. OVS data plane, per-link harness impairments, SONiC-VS NOS twin, and the full Open5GS/UERANSIM lifecycle are delivered
3 — production SDV alignmentvxedge vehicle up boots a full vehicle end to endIn progress. Content is landing ahead of the gate: 5G core/RAN, Kuksa signal-plane and OTA parts in vxparts, plus the vxmcp MCP server
4 — hardware in the loop (optional)Jetson / DRIVE / BlueField / V2X radioSpecified, not started
5 — remote / multi-user deploymentnone yetBacklog: mTLS + OIDC for vxAPI's TCP transport, role model, actor-aware audit

Cross-cutting tracks:

  • M — SysML v2 model governance (vxmodels): M0–M3 are closed. M4 (scenario models, fidelity ledger) is waiting on a GPU host for CARLA.
  • C — containerization: complete through C3.2. The 5G stack and platform services run in containers, and the measured path stays on the host.
  • P — vxparts unification: complete. The earlier zone and compute repositories are merged into the unified OCI/ORAS loadable registry.

Open work

Phase 2 carry-overs

  • exp-004, exp-012 and exp-020 are each blocked on a real prerequisite: a compute-timing agent, the TSN gateway variant, and CARLA respectively.
  • vxagents: DSCP marking, clock-sync probing, and PCAP helpers.
  • SO_TIMESTAMPING (kernel timestamps) in place of userspace-monotonic probing.

Phase 3

  • vxedge vehicle up end to end (the gate).
  • exp-011: real ADAS traffic, CARLA → ROS 2 → Autoware closed loop. It needs a Tier 2 GPU host (TESTBED-SETUP.md).
  • QNX SDP 8 and Android Automotive zones, and an embedded Qt/QML IVI loadable.
  • vxmcp: the remaining read tools, and mutating tools gated by confirmation.
  • On-demand reproduction pipeline for published experiments.

Release engineering

  • A tag-triggered GitHub Release per repository.
  • cargo-dist binaries for vxedge/vxedged.
  • GHCR images with recorded digests.
  • A cross-repository compatibility matrix.

Publication

  • Paper #1 (the phase-1 dataset: H1/H3/H4) is in preparation for arXiv.
  • A citable, archived reproducibility bundle (Zenodo DOI) will accompany it.

Contributing to the roadmap

Open an issue on the repository the work belongs to. For anything that spans repositories, open it in vxedge/docs.

Cite this page

Djaafri, F. (2026). vxedge: Roadmap. Documentation, version 0.2.0, commit 33ede87. https://vxedge.dev/docs/ROADMAP.html

@misc{djaafrivxedgeroadmap2026,
  author = {Djaafri, Fouzi},
  title  = {vxedge: Roadmap},
  year   = {2026},
  url    = {https://vxedge.dev/docs/ROADMAP.html},
  note   = {Documentation, version 0.2.0, source commit 33ede87}
}