The runtime

A map of content for layer 1: the process model, the failure model, the two runtimes and the C backend, and every step that changed them under a program’s pressure. The runtime carries the thesis’s reliability claim, so this is where most of the measuring happened.

The model

The steps, in the order they landed

Current harness-driven work

The runtime’s own row

A crashed process with the service still answering, P6: control-run-8 (Mo’s outage, a wait hidden as a message pattern), control-run-10 (the BEAM restores service in under 600 ms, and exits on the fourth kill or on a full disk), erosion-round (generation two answers through a full disk in Mo, Go, and Python; Elixir does not), 10-language-after-the-rounds §1 and §2 (what the language should say about it).

Compilation