Ranvier
KR Start Tutorial

Typed Decision Engine

Execution you can read.
Structure you can trust.

Ranvier turns Rust control flow into a living circuit. Axon executes. Schematic explains. Outcome keeps every branch explicit.

Start Tutorial Read the Intro
Protocol-agnostic core HTTP lives in adapters No hidden middleware Bus stays explicit Schematic diff before runtime
Ranvier Code-as-Circuit
// src/ingress/auth.rs
let auth_flow = Axon::new()
    .then(validate_token)
    .branch(|ctx| {
        match ctx.role {
            Admin => admin_circuit,
            User  => user_circuit,
        }
    });
LIVE SCHEMATIC
Ingress
Validate
Admin
User

"You write the logic. Ranvier verifies the circuit."

01

Axon Execution

Build explicit decision flow with typed transitions. Every step is visible, inspectable, and deliberate.

02

Schematic Insight

Extract structure from code without running it. Diff and validate circuits before runtime surprises.

03

Outcome Clarity

Branches, jumps, emits, and faults stay visible as data. No hidden middleware chains.

04

Boundary Discipline

Ingress and egress adapters translate protocols. Core stays clean, resources stay explicit, and trust boundaries stay enforced.

Opinionated Core, Flexible Edges

🔒

Opinionated Core

Ranvier enforces Transition/Outcome/Bus/Schematic for internal architecture. This is what makes Ranvier, Ranvier — a schematic-first, visualizable framework with clear identity, one learning path, and consistent codebases.

  • Business logic → Ranvier way (Transition-based, visualized)
  • Complex workflows → Ranvier shines (multi-step, state machines)
🔓

Flexible Edges

At boundaries, use any Rust tool you want — Tower, actix, Axum, sqlx, diesel, redis. Integrate with the ecosystem, migrate gradually, choose your infrastructure.

  • Infrastructure (CORS, auth, DB) → Your choice (Tower, ecosystem libraries)
  • Simple CRUD → Ecosystem tools OK

This principle lets you keep Ranvier's schematic-first benefits while leveraging the Rust ecosystem you already know.

Read Full Philosophy

Foundation Guarantees

Bus is a typed container. You choose what enters and who can read it.
Ingress parses protocol requests into state. Egress maps Outcomes back to responses.
Schematic is static: diff, validate, visualize. It never executes runtime logic.
LLMs can propose structure, but they cannot mutate runtime without explicit review.

First-Time Path

1) Ranvier: Start with the Intro to understand Axon, Outcome, and adapter boundaries. Then follow the Tutorial to build your first circuit.
2) CLI: Use Manual commands to export schematic and projection artifacts from workspace examples.
3) VSCode: Check Status for current capabilities, then follow the deploy guide path to adopt diagnostics, source-jump, and release checks.

Documentation Path

Intro

Why Ranvier exists, what it replaces, and what it refuses to hide.

Tutorial

Build and run a minimal ingress circuit, then explore canonical examples.

Manual

Core concepts, layer boundaries, CLI tools, and trace/inspector workflow.

Status

See what ranvier, cli, and vscode can do now with verification commands.

No Magic. Just Physics.

Ranvier compiles to standard, high-performance Rust binaries. Core stays protocol-agnostic. Adapters handle transport. You keep control.

View the Source