Documentation
Architecture overview
Map the main crates and the runtime flow from configuration to supervision.
High-level flow
At a high level, Vectron:
- Parses
vectron.toml - Validates configuration and resolves paths
- Builds process and instance specifications
- Launches supervised child processes
- Collects and renders logs
- Exposes a local control endpoint
- Tracks runtime state under
.vectron/
Main crates
config: parsing and validation forvectron.tomlcore: domain model for processes, ports, readiness, and logsdaemon: CLI, TUI, supervision, lifecycle wiring, and control endpointprocess-host: process-group isolation and signal helpersstack: local stack scaffolding and provisioning
Support crates
The workspace also contains focused helper crates under libraries/, for example formatting, control protocol strings, JSONL helpers, filesystem utilities, and TUI helpers.
Why this split exists
The workspace decomposition keeps:
- parsing separate from runtime
- reusable helpers out of
daemon - platform-specific process behavior isolated
- stack-specific logic isolated from the main CLI path
Code-level reference
For crate and API-level details, use the published rustdoc under /rustdoc/.