Ved Diagnostics

Structured failure semantics.

Ved defines a formal error taxonomy grounded in deterministic execution, authority boundaries, and convergence guarantees.

Errors are not incidental messages. They are manifestations of violated system invariants.

Design Philosophy

Why Ved Needs a Formal Error Model

  • Distributed orchestration failures are often architectural.
  • Deterministic systems require invariant enforcement.
  • Clear failure classification enables reproducible debugging.

Invariant-centric diagnostics • Compile-time safety • Runtime contract enforcement

Diagnostic Code System

Canonical Error Identifiers

NamespaceVED
—
Domain Area<CATEGORY>
—
Identifier<NUMBER>

By enforcing a strict taxonomy, Ved ensures category stability, machine-readable semantics, and seamless tooling integration.

Error Categories

Details: Attempts to mutate state across domain boundaries.

Details: Non-deterministic calls inside strict execution slices.

Details: Target semantics cannot be reached within bounds.

Details: Infinite loops or queue starvation detected.

Details: Schema mismatches on snapshot restoration.

Details: Unauthorized side effects outside effect types.

Details: Structural invalidity at compile time.

Design Feedback

Errors are treated as structural design feedback, not just execution blockers.

Explore Warning System