Study Lab
local appVango

Learn Vango and Rhone Cloud

Start with guided lessons, then use labs and reference pages to test the model under failure.

Guided lessons

9

teach-first path

Modules

11

reference areas

Labs

8

interactive decisions

Failure drills

34

scenario prompts

The core thesis

Vango/Rhone is a platform for making state explicit: who owns it, who can mutate it, how durable it is, and what happens during deploy, scale, wake, rollback, region failure, and host maintenance.

Authority

Control-plane records beat logs, caches, and late worker reports.

Continuity

Live sessions stay pinned unless durable resume proves otherwise.

Honesty

Cold deploys, unsafe replay, data risk, and blocked readiness are product facts.

How To Use This

Use it like a course, not a wiki.

1

Learn one model

Open Guided Mode and finish one lesson end to end.

2

Run the matching lab

Flip inputs until you can predict the platform decision before it changes.

3

Explain it back

Use the quiz prompt and say the answer out loud in terms of owner, writer, durability, and failure.

4

Use references only after

Taxonomy, objects, traces, events, and runbooks are lookup tools once the lesson gives you the frame.

Architecture Map

The app teaches three connected loops: Vango runtime authority, Rhone deploy authority, and runtime scaling authority.

Vango runtime loop

The app-authoring model

loop
Browser sends events and receives patches.
Session loop is the single writer for UI/session state.
Resources read async data; Actions mutate through explicit gates.
Render remains pure so state changes are explainable.
Hooks and JS islands own browser-only behavior or subtrees.
Study this loop

Rhone deploy loop

The release-safety model

loop
Import repo and analyze setup/rhone.toml.
Build immutable artifact plus Vango manifest.
Classify generated freshness, state impact, and migration impact.
Validate preview, then promote exact artifact with route-owner CAS.
Propagate route epochs to edge by snapshot plus events.
Study this loop

Runtime scaling loop

The operations model

loop
Route owner decides deployment authority.
Allocation selection picks ready runtime capacity.
Live sessions stay pinned unless durable resume is proven.
Scale-to-zero, wake, drain, and host upgrades are lifecycle operations.
Horizontal and multi-region scale require explicit runtime/data topology.
Study this loop

Guided Path

Each lesson teaches the concept, walks a trace, gives you an exercise, and then shows what a strong answer includes.