Documentation

Architecture overview

Map the main crates and the runtime flow from configuration to supervision.

High-level flow

At a high level, Vectron:

  1. Parses vectron.toml
  2. Validates configuration and resolves paths
  3. Builds process and instance specifications
  4. Launches supervised child processes
  5. Collects and renders logs
  6. Exposes a local control endpoint
  7. Tracks runtime state under .vectron/

Main crates

  • config: parsing and validation for vectron.toml
  • core: domain model for processes, ports, readiness, and logs
  • daemon: CLI, TUI, supervision, lifecycle wiring, and control endpoint
  • process-host: process-group isolation and signal helpers
  • stack: 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/.