Ved Tooling
The Terminal
is the Platform
A philosophical alignment of speed, clarity, and structural honesty.
Design Precepts
We believe the CLI is the highest-leverage developer interface. It must respect time, attention, and cognitive capacity.
- Zero chrome: No extraneous banners or ASCII art. Data over styling.
- Sub-second responses: Parsing, linting, and compiling must feel instantaneous.
- Structural output: Everything emits structured diagnostics if needed (`--json`).
- Actionability: Never report an error without a path to resolution.
Diagnostic Formatting
Every failure must clearly separate: Context (where), Evidence (what happened), Consequence (what broke), and Remedy (how to fix).
Error[E0042] Type mismatch in state transition
12 | transition.apply(State::Pending, State::Active)
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| Expected TerminalState, found TransientState
= Help: ensure `State::Active` implements `TerminalTransition`
12 | transition.apply(State::Pending, State::Active)
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| Expected TerminalState, found TransientState
= Help: ensure `State::Active` implements `TerminalTransition`
Unified Workflow
One binary. No plugins to configure. No disjointed toolchain environments.
ved buildCompile to bytecode
ved runExecute locally
ved checkStatic analysis & lints
ved testRun formal simulations
Shape the Toolchain
Ved is actively in development. If you share our philosophy on diagnostics and developer experience, we'd love your help building the core runtime and CLI.