An OS where authority is explicit
and nothing is ambient.

Most companies talk about security only after something goes wrong. We commissioned an independent red-team / blue-team review of the entire stack — language, kernel, drivers, filesystem, build pipeline — while we're still pre-1.0, and published what it found: real strengths, honest gaps, and a public remediation plan. No exploit details; full plain-language brief on GitHub. Read the security posture brief →

Forge v0.1 native downloads are live for macOS, Linux, and Windows — one Sigil source, compiled per platform by cc0, each with a published SHA-256 (get it). A real CHIP-8 core runs a ROM natively on the new mem_map keystone. And @grio's newest flagship kicked off: the agnostic self-healing bootloader — if the machine lacks a driver, boot fetches it, verified before load.

First non-ARM Lumen boot: the full desktop on x86-64 bare-metal QEMU · SRDX remote display end-to-end (Ed25519 one-use invite, relay mesh, SRDX-NET-RT-PASS) · mouse + audio integrated · Lumen-working capstone.

The headline of the 0.7.0 cycle: the x86 login screen renders on @grio's real x86-64 box (VER=12 — titlebar, user cards with avatars, password field, all correct), and the Pi 4B renders + talks serial on metal (the cached-MMIO + GPIO-ALT0 mux fix). And as of June 29 the last mile is done: the VL805 USB keyboard types on Pi 4B metal — characters on screen at the login, after ~100 build-iterations. The full saga is in the changelog and the build journal.

Native all-Sigil build harness (Python + keystone retired from the emit path) · the font subsystem (composite glyphs + full-Unicode cmap + bounded rasterizer — a 1.0 gate) · the Lumen dock + Doom Pile window pile (Apps past 200 modules) · the unified Pi image (one SD, board-detects Pi 3B→4B→5 and scales from the floor) · WASM-4 carts run cap-sandboxed as EL0 apps (Forge system #75) · real TLS 1.3, SigDB, CAS dedup all live · a capability-architected browser.