Loment 0.1.4 Pre

A pre-release of main at 0.1.4 — now installable. Tagged so that "the repo has
versions" is visible; 0.1.4 final is not finished yet (see What it is not below).

Install

Platform	File	How
Linux / WSL	loment-0.1.4-linux-x64.tar.gz	unpack → sh install.sh
Windows	loment-0.1.4-windows-x64.zip	unpack → powershell -File install.ps1
Windows	loment-0.1.4-windows-x64-setup.exe	double-click (self-extracting)
any agent	loment-skill.zip	the language guide on its own, for agents

SHA256SUMS covers the three archives and the skill zip; the install scripts check it first.
Both install routes put down the same thing: the bootstrap artifacts, the launcher, and the
seed — the package contains no Python. To build from a checkout instead, see
QUICKSTART.md.

The Windows installer is unsigned, so SmartScreen will warn once.

Which commit these are built from: main at 557fd26 (2026-09-22) — that is the commit
the archives were built from, and share/loment/version inside them says so. The tag
v0.1.4-pre itself points at an earlier commit, so GitHub's auto-generated Source code
archives follow the tag and are the earlier tree — if you want the source that matches these
binaries, check out 557fd26.

Verified after upload: SHA256SUMS checks out for all four files; the Windows zip
installs (install.ps1 -Prefix … -NoPath -NoFileType -NoSkill) and the installed toolchain
compiles and runs a program natively on Windows (no clang, no WSL, no Python); the Linux
tarball installs in a POSIX shell and its toolchain does the same in WSL.

What is here

• A systems programming language that compiles to native x86-64 — Linux ELF, Windows PE,
  or a freestanding object for bare metal — with no runtime and no libc.
• A toolchain written in Loment: compiling and running needs no Python (the bootstrap
  starts from a genesis ELF committed to the repo).
• Six more surface syntaxes on top of the base one: C, C++, Java, C#, Go, Python —
  the same program, written in any of them.
• Potato formal objects (the cross-line contract) exported by the compiler, plus a
  capability domain model (capability / guard / excluded / revocable).
• The static gate runs on GitHub Actions for every pull request and push to main
  (ci.py --static-only). It is a real gate: a measured baseline of reds is committed, and
  a pull request fails if it introduces a new one.
• A generated manual,
  a language guide,
  an editor extension,
  and examples.

What it is not

• Not 0.1.4 final. The language surface is frozen for this line
  (docs/158),
  but the tree is still moving every day.
• Not fully self-hosted yet. The toolchain runs without Python, but the repo still
  carries non-Loment development-time code (the criteria are being ported to Loment —
  docs/189).
• Not all checks are green. The gate's baseline still contains reds — four of them need
  a private sibling repository (FujoJTOP/LinuxFUAI) that a public runner cannot read.
  "Everything green" is therefore not literally attainable today; the gate's rule is
  "no new reds".
• 0.1.4's own prerequisites are not all closed — the audited checklist is
  docs/202.

Pointers

• Version source of truth: tools/loment_release.py (RELEASE)
• Direction / what 0.1.4 means: docs/175
• Release prerequisites, item by item: docs/202
• Freeze surface: docs/158
• Contributing (including how to read a red gate): CONTRIBUTING.md