How dderyldowney/vde-system works
VDE is a Docker-based development environment for creating and operating isolated “Spoke” workspaces, with a companion Forge governance system. The documented user path is to bootstrap or invoke the CLI, manage a Spoke through its lifecycle, and work as devuser with workspace files persisted back to the Hub. The graph preserves documented health, service, USB, and schema-validation capabilities. Source excerpts cover only the JSON validator and a tagging utility, so most runtime links below are documented in the README rather than verified from implementation.
Main entry points: vde VDE CLI · projects Persistent workspace · config SSH bridge · .gemini Forge governance
Components 15
User entry
- Bootstrap
scripts/bootstrap.sh - VDE CLI
bin/vde - Hub health
bin/vde-health - Spoke inspection
bin/vde-info
Spoke environment
- Spoke lifecycle
bin/vde - Language Spokes
configs/docker/languages - Service Spokes
configs/docker/services - VM type registry
data/vm-types.json
Workspace and access
- Persistent workspace
projects - SSH bridge
configs/ssh/config - USB mapping
scripts/vde-usb-map.zsh
Governance and validation
- Forge governance
.gemini - File tagging
conductor/mass_tagger.py - JSON schema validation
lib/vde-json-validate.py
Other components
- Developer
Connections 13
- Developer → Bootstrap: starts setup
README.md - Developer → VDE CLI: runs commands
README.md - VDE CLI → Spoke lifecycle: manages lifecycle
README.md - Spoke lifecycle → Language Spokes: uses Spokes
- Spoke lifecycle → Service Spokes: uses services
- VDE CLI → Hub health: checks health
README.md - VDE CLI → Spoke inspection: inspects Spoke
README.md - Developer → Persistent workspace: saves work
README.md - Persistent workspace → SSH bridge: syncs to Hub
README.md - SSH bridge → Developer: connects Hub
README.md - Developer → USB mapping: uses hardware
README.md - Developer → Forge governance: uses governance
README.md - Forge governance → File tagging: tags files