FreedomLang | Native Tools, Explicit State

CI green across native targets

FreedomLang builds

native tools with

explicit state.

"Model the world as data. Treat bugs as fatal."

FreedomLang is an auditable AOT-compiled native systems language for high-integrity tools.<br>The compiler is ordinary JavaScript you run with Node.js, lowering source through a compact IR<br>into x86-64 artifacts with explicit world-state handling and fail-fast invariant checks.

View on GitHub<br>See the Code

Linux ELF

macOS x86-64

Windows PE/COFF

No more magic &rarr;

Small Trusted Base

No LLVM, VM, JIT, or project-specific compiler binary in the normal path. The compiler is Node-run JavaScript source.

Fail-Fast

Bugs terminate immediately via fall. No silent partial failures. No exception soup.

Chaos Tags

World state modeled as data. Missing files and network timeouts are handled explicitly, not thrown as exceptions.

Native Artifacts

Linux ELF, macOS assembly linked by clang, and Windows x86-64 assembly linked into PE/COFF through LLVM/lld.

Explicit Jobs

Fork blocks, handles, wait, and FSABI inbox/outbox paths make process boundaries visible in source.

UTF-8 & Bytes

First-class byte arrays and UTF-8 string conversion. Handle binary protocols naturally.

Byline

Auditable native tools with explicit world state and fatal bugs.

Three Sentences

FreedomLang is an AOT compiled language that compiles .flx source through a compact JavaScript compiler and IR into native x86-64 artifacts. External uncertainty is modeled as explicit data, while broken invariants terminate immediately. The project is pre-1.0, but the compiler, runtime model, backends, and behavior tests are real enough to evaluate from code.

One Paragraph

FreedomLang is a small AOT compiled systems language for people who care about native tools, auditability, and failure semantics more than optimizer sophistication or ecosystem size. Programs use user-defined operators, object-shaped calls, tagged runtime values, explicit job/fork concurrency, and a growing chaos/world-state model for files, sockets, and other outside conditions. The compiler does not rely on LLVM, a VM, or a JIT; it is JavaScript source run with Node.js, and the repo contains the frontend, IR lowering, platform backends, runtime helpers, stdlib, and behavior suite.

Feature Domains

FreedomLang is early, but its core claims are implementation-backed. The table separates what is solid today from surfaces that are still being hardened.

Domain<br>Status<br>What exists now<br>Honest note

Native compiler pipeline<br>✅ covered<br>Parser, IR lowering, and x86-64 backends live in the repo.<br>No serious optimizer yet; the compiler is pre-1.0.

Node-readable compiler<br>✅ covered<br>The compiler is JavaScript source run with Node.js, not a sealed project-specific compiler binary.<br>Node.js is still a binary dependency; the claim is about the FreedomLang compiler distribution.

Native targets<br>✅ covered<br>Linux ELF, macOS Mach-O via clang, and Windows PE/COFF via native x86-64 assembly.<br>Windows is native assembly for the Microsoft ABI, not a VM or transpiler path.

Small binaries, no libc/CRT default<br>🟡 bounded<br>Generated programs avoid libc/CRT in current paths and emit helper code only as needed.<br>Smaller dependency surface is not a security proof; OS APIs and runtime helpers still matter.

Bounds, shape, and fast-fail checks<br>✅ covered<br>Array/object access checks, fatal invalid-state paths, fall, assert, and expect_eq.<br>Runtime checking, not static memory safety or formal verification.

Custom operators<br>✅ covered<br>Positional, object-shaped, infix, shaped infix, and value-shape operator forms.<br>The syntax is unusual and will need careful examples and restraint.

FSABI concurrency<br>✅ covered<br>Fork blocks, handles, wait, blocking fork sugar, job directories, and inbox/outbox paths.<br>Favors explicit process/job semantics over lightweight in-process concurrency.

Chaos/world-state modeling<br>🟡 hardening<br>with chaos and chaos tags model external outcomes as explicit data.<br>Strongest on macOS today; Linux and Windows parity are still moving.

Heap and GC<br>🟡 hardening<br>Heap allocation exists across targets; macOS has the strongest generated GC path today.<br>No-heap/no-GC mode is an aspiration, not a stable flag yet.

AI-agent ergonomics<br>🟡 thesis<br>Small compiler, explicit jobs, behavior tests, and visible failure boundaries.<br>Promising design direction, not a benchmarked claim.

Language Genealogy

FreedomLang is not a direct descendant of one language. It combines older ideas in a small AOT compiler: native-output systems languages, Unix job control, tagged result values, object-shaped calls, and agent-readable implementation practice.

FreedomLang<br>├─ C / Zig / Go family<br>│ ├─ AOT compilation to native artifacts<br>│ ├─ operational tools as a serious target<br>│ └─ explicit release binaries instead of a VM or JIT<br>├─ Unix process model and shell job control<br>│ ├─ fork blocks<br>│ ├─ wait points<br>│ └─ filesystem-visible job inbox/outbox state through FSABI<br>├─ ML...