Design notes
These are forward-looking proposals and historical design notes — the record of what was explored, what shipped, and why. They are not part of the stable contract.
- Adversarial audit — vx terminal output layer
- Architecture north star — the unified vision
- Architecture Overhaul — June 2026 Implementation Plan
- Architecture review — sharpening the five proposals
- Architecture review — simplify, DX, develop further (2026-07)
- Cache trust scopes — design
- Concurrent index migrations — design
- Config lock — vx lock / vx-lock.json (2026-06)
- Consulting review — full-system audit (2026-07)
- Core / cloud split + plugin-based extension points — design
- Cross-machine fingerprint diff (—verify Phase 4) — design
- Dashboard competitive analysis + improvement plan (2026-06)
- Dashboard Tier 3 — schema, recording, and the input-fingerprint moat (2026-06)
- Dashboard UX v3 — journey-driven IA (2026-07)
- Dev flows, CI integration, and vx agents — design
- Developer scenarios — one dev inside a huge monorepo (2026-07)
- Distributed execution (vx agents) — design
- Distributed execution on CI — the killer-feature roadmap
- Distributed runs in Runs — the controller records like a local run
- Execution as a backend — vx serve and the client/service split
- Extension protocol — third-party tooling on top of vx
- Full audit — cycle 1 (2026-07-12)
- How Claude Code does its TUI
- Integrity & robustness audit — May 2026
- Local cache — v10 → v13
- Lookahead / critical-path-aware admission — design
- Module isolation — design
- Monorepo structure — design
- Observability + integration architecture — design
- Per-task logs + artifacts in the dashboard — design
- Pre-signed artifact URLs — design
- Predictive execution — using history to win the perf war
- project analytics view — design
- Provable cache correctness — design
- Remote cache — protocol design
- Resource-aware scheduling — design
- Run event stream + devframe surfaces
- Runtime inputs — design (2026-06)
- S3-compatible blob backend — no artifact bytes at rest on the controller
- Security review — 2026-07
- stable-key local cache short-circuit — design
- The vx-native cache wire — plugin-driven remote cache, Turbo compat dropped
- Turbo / Nx parity: behavioural contracts vx does not pin (2026-07)
- Turbo + Nx test gap analysis
- Turbo vs Nx vs vx — full scenario matrix + test-coverage gaps
- Turbo vs Nx vs vx — operation-by-operation breakdown
- Universal agents & pools — design
- Validity-filtered caching (replaces output-fold early cutoff)
- vx as a CI platform — competitive positioning + the standing shared-pool scheduler
- vx Cloud — hosted observability, cache, and execution
- vx run —tui — architect’s design
- vx run —tui — interactive full-screen dashboard
- vx-cloud as an independent self-hosted CI platform — design
- vx-cloud client/server model — environments, connect, auth — design
- vx-cloud data-first entity model — design
- Wire protocol — JSON-RPC 2.0 + OTel LogRecord payload