Mo Lang — Index

Start here. The state of the project is the whole picture, rewritten at every pause. The maps of content gather the pages behind it: the thesis and its evidence, the rounds and the measurements, the language, the runtime, the programs, for Robert, how we work. The roadmap board is the authority on order and status; the decision-log is what Robert reads.

Every wiki page, one line each. Read this after SCHEMA.md to find pages for any question. Last updated: 2026-09-19 | Total pages: 285

Directions we like

Questions and their answers

Decisions

  • Decision log — every choice in order, who made it, status, what first tests it

Syntax picks and examples

Deep dives

Plans

Sessions

Research

  • Mo vs Bend2 — protected law/proof workflow, release-matched learning, evidence status and selective ownership; pinned source inspection and local checks, with GPU/proof caveats

  • agent-native-research-synthesis — four reports reviewed with the oracle; selective source checks, four additional strategic reviews and the agreed calibration-to-useful-workload sequence; implementation paused

  • agent-native-independent-review-prompt — self-contained web-enabled review brief; challenge everything, including a new language/runtime; comparable independent responses

  • Mo vs Elixir — comparison: inference-first gradual types, OTP supervision shapes vs Q7, typed processes

  • Mo vs Go — comparison: simplicity by tooling, error-syntax post-mortem, goroutine bugs, module supply chain

  • Mo vs Rust — comparison: what Mo keeps (enums, matching, small traits) and drops (lifetimes); compile-time and LLM evidence

  • Mo vs Roc — comparison: how a platform is built, purity by arrow, static dispatch, Perceus, the Zig rewrite numbers

  • Mo vs Koka — comparison: effect types and handlers vs capabilities, the closure-capture gap in d15, Perceus, fip

  • Mo vs Austral — comparison: linear capabilities from a root, unsafe modules, crash-on-contract-violation, what linearity would buy Mo

  • Mo vs Hylo — comparison: mutable value semantics precisely, parameter conventions, projections, a coherence rule, colorless concurrency

  • Mo vs Unison — comparison: hash-identified definitions, never-invalidated caches, no dependency conflicts, the cost of dropping text

  • Mo vs MoonBit — comparison: the shipping AI-native toolchain (Pilot, sampler, SeekMoon), its language, and the no-resource LLM evidence

  • Mo vs Bosque — comparison: design by removal, no loops, escape-free lambdas, validation levels, small-model verification, why it slowed

  • Mo vs SPARK Ada and Dafny — comparison: contracts that run and prove, assurance levels, contract shapes LLMs discharge, loop invariants

  • Mo vs the agent-native cluster — comparison: 13 agent-first languages in short entries, and what 42 catalogued attempts converged on

  • Mo vs aube — comparison: the Node package manager’s security defaults (trust no-downgrade, age gates, reputation signals, jail) and the seven things Mo takes

  • Mo vs Verse — comparison: failure as control flow, transactional rollback, structured concurrency; transactions vs crash-and-restart

  • Comparison synthesis (draft) — ⚠️ tensions across the 13 comparisons, top ten steals, open questions for Robert; draft for Fable

  • Supply-chain defenses — Q17 input: defenses that exist, the 2024–26 incident record (20 of 47) with impact/trend ranking, Mo mapped against it, six package-system design options (no recommendation)

  • Landscape, second lane — what Robert’s three landscape research runs add or dispute vs Claude’s survey; shortlist arguments

  • Mo vs Motoko — comparison: actor isolation, trap-reverts-to-commit-point, upgrade-safe persistence, the ‘designed for AI agents’ claim (Caffeine)

  • The case against new languages — the null hypothesis the v0 design doc must answer: Quasar, CodeAct, SynCode, token sugar, cold start, ilo, Aether, BHC/hx

  • Capability module lineage — Newspeak, Joe-E, Wyvern, Limbo, E’s confused deputy, each mapped to pick 13 / Q16 / Q17

  • Language landscape: which languages deserve a deep comparison — 40+ languages in seven groups with the idea to steal from each, plus a 13-entry shortlist for the comparison pass

  • Research prompts: the language landscape — three prompts for Robert’s deep-research tools

  • Research prompts: Q17 supply-chain security and package management — three prompts for Robert’s deep-research tools

  • Research prompts: Mo’s three parallel research tracks — empirical validation, ecosystem depth, agent-authoring frontier; each brief paired with its Perplexity deep run

  • The PL landscape circa 2026 — what’s alive, growing, fading, and where the interesting design work is happening; extends language-landscape

Language surveys (history + design + Mo lesson)

Research monitoring

  • hermes-daily-2026-09-19 — OTP timeout/late-response semantics and the boundary between duplicate refusal and safe replay.

  • hermes-daily-2026-09-18 — TLS state-sequence coverage, harness limitations, and versioned EOF semantics.

  • hermes-research-monitoring — the plan of the Hermes lane: an independent daily evidence scan and Monday synthesis, wiki-only, reviewed through a research PR before merging

  • hermes-daily-2026-09-17 — Crash-consistency fault models, capability API confinement boundaries, and daily validation.

  • hermes-daily-2026-09-16 — Versioned restart-budget defaults, error-path coverage evidence, and daily scan validation.

  • 07b-redis-subset-revision-2 — program 7’s spec, revision 2: persistence out of Redis’s suite, expiries on rewrite, one size cap, the lead’s skip list, RC2’s core operation, R2 to R7 pinned, a package behind /metrics; sealed 18 Sep