Architecture index

The docs/src/architecture/ section contains several different kinds of documents. This page is the map.

Current architecture and authority docs

Use these when you need current policy and behavior. The canonical cross-domain map is contracts/documentation/canonical-map.v1.yaml; this page is navigation, not the source of behavioral truth.

• Feature growth boundaries
• Interop tier policy
• MCP exposure from the Vox language
• Capability registry authority — contracts/capability, vox ci capability-sync, model manifest
• Capability visualization views
• Vox bell-curve strategy
• Doc-to-code acceptance checklist
• Orphan surface inventory
• Legacy retirement roadmap 2026 — LLM guard: deprecated surfaces, frozen files, safe-to-extend surfaces
• Language surface authority — keywords / decorators / manifests
• OpenAPI contract authority — committed YAML, validation, optional codegen
• AI CLI generation standard — AST/JSON schema constraints for MENS command generation
• Outbound HTTP policy — vox-reqwest-defaults and migration order
• Compiler diagnostics ergonomics — miette vs custom errors, quote pilot
• Vox shell operations boundaries — host pwsh vs vox shell vs .vox std.* (no shell emulator product)
• Plan adequacy (thin plans & telemetry) — external limits, shared heuristics, expansion policy
• CodeRabbit review coverage SSOT — full-repo review scope, persistence, and lane hardening
• Telemetry trust boundary map — telemetry surfaces, trust planes, and canonical links
• Telemetry taxonomy and contracts — roadmap event taxonomy and contracts
• Telemetry retention and sensitivity — roadmap retention and S0–S3 classes
• Telemetry client disclosure — VS Code / MCP host disclosure
• Telemetry implementation blueprint 2026 — phased rollout plan
• Telemetry implementation backlog 2026 — executable checklist
• Telemetry remote sink specification — optional vox telemetry upload wire contract
• Cryptography Policy SSOT — cryptographic algorithms and vox-crypto architecture
• Operations catalog authority
• Completion policy authority
• HITL doubt loop
• Cross-repo query observability
• Vox organization
• Session management
• Security model
• News syndication security
• News syndication incident patterns
• Memory system
• Vox web stack SSOT
• Compiler IR pipeline
• IR emission SSOT (check vs build, VoxIrModule vs WebIR)
• Vox source → Mens pipeline SSOT — lexer/compiler → goldens → corpus → HF tokenizer
• Populi data pipeline — mesh control plane vs Mens training sources
• RAG and research architecture 2026

MENS System

For MENS architecture and training details, refer to:

• Populi data pipeline
• GUI, v0/islands, vision, and Mens Qwen — virtuous-cycle implementation plan (2026) — GUI verification loop, vision rubrics, fine-tuned Qwen3.5 vs optional VL lane

Research and synthesis

Use these when the question is exploratory, comparative, or evidence-gathering:

• Research index
• AI IDE feature research findings 2026
• Terminal execution policy research findings 2026
• Telemetry unification research findings 2026
• Context management research findings 2026
• Protocol convergence research 2026
• ASR speech-to-code scouting 2026 — model WER comparison, Canary/Qwen/Whisper/Moonshine/Parakeet overview
• ASR speech-to-code full architecture 2026 — preprocessing stack, Rust crate design, WER estimates by adaptation tier, MENS integration, training pathway
• *-research-2026.md
• *-findings-2026.md
• synthesis pages that are explicitly labeled as research

Planning and roadmap

Use these when a page describes intended implementation rather than current behavior:

• Qwen 3.6 integration research (groundwork) — pre-implementation checklist vs Qwen 3.5 SSOT; native vs API paths
• Qwen3.5 multimodal Phase 2 backlog — vision/video tokens after text-only 3.5 is green
• Context management implementation blueprint
• Context management phase 1 backlog
• *-implementation-plan-2026.md
• React / v0 interop migration charter 2026 — governance, KPIs, cutover checkpoints
• React / v0 interop backlog 2026 — granular WS01–WS26 checklist index
• React / v0 interop research findings 2026
• React / v0 interop implementation plan 2026
• React / v0 hybrid adapter cookbook (SPA + SSR)
• Populi GPU mesh implementation plan 2026
• Populi GPU truth probe specification (NVML Layer A) — optional nvml-wrapper build path for NodeRecord inventory
• Populi node lifecycle, drain, and GPU hotplug — lifecycle model and backlog vs shipped gates
• Normative decision docs for Populi GPU / mesh placement: ADR 017: Populi lease-based remote execution, ADR 018: Populi GPU truth layering, ADR 020: Populi mesh scaling — default transport posture, work-type placement matrix — aspirational batch/K8s notes remain in Populi GPU mesh implementation plan 2026 until dedicated ADRs are filed
• ADR 022: Orchestrator bootstrap factory and daemon boundaries — shared build_repo_scoped_orchestrator, MCP/CLI identity parity, vox-dei-d boundary
• *-implementation-blueprint.md
• *-roadmap.md
• planning-meta documents under planning-meta/

How to read this section

• If you need shipped behavior, prefer pages labeled status: current or pages that mirror code and contract surfaces.
• If you need rationale, open the matching ADR or architecture authority page.
• If you need future direction, read roadmap and planning documents as plans, not as claims of current capability.