Star on GitHub ⭐ Home Install Documentation & Book Playground IDE Tutorials & Learn Standard Library & Python Interop Community & Governance About & Governance Engineering Blog Brand Identity Kit Direct .exe Download
Global Ecosystem & Governance

Community, RFC Governance & Roadmap

Transparent engineering milestones, working groups, democratic RFC proposals, and local contributor onboarding for the next decade of sovereign language design.

The 20-Phase Sovereign Execution Roadmap

Every milestone in Enlangg represents a verifiable engineering target towards self-hosting compilation, formal verification, and zero third-party dependencies.

Phases 01 - 05: The Grammar Core & Slot Memory

Completed

Formalization of spoken English syntax, replacement of symbol glyphs with unambiguous English clauses, deterministic stack slot parser, zero-GC lifetime analysis, and canonical ISO C99 emission engine.

Phases 06 - 10: Multi-Domain Isolation Architecture

Completed

Architectural separation of system tiers into dedicated formal domain extensions (.enlng, .enlngf, .enlngs, .enlngd, .enlngm, .enlngdb). Universal full-stack compilation pipeline.

Phases 11 - 15: C-ABI Python Bridge & Distribution Toolchain

Stable Release

Zero-overhead C-ABI Python God Call, standalone 1-click Windows installer (enlangg-setup.exe), 193-page canonical specification book, and sovereign Vercel self-hosted binary mirrors.

Phases 16 - 20: LLVM IR Core, Formal Verification & Self-Hosting

Active Workstream

Direct LLVM backend emitting native machine code without C compiler middleman, Hoare-logic formal verification proving memory safety at compile time, and 100% self-hosting compiler written in Enlangg.

Working Groups (WGs)

Similar to the Python Steering Council and Node.js Technical Steering Committee (TSC), Enlangg is stewarded by specialized working groups:

Core Compiler WG

Maintains the lexical tokenizer, slot allocator, and C99 emission pipeline. Oversees performance benchmarks and LLVM integration.

Standard Library WG

Maintains built-in modules (I/O, Math, String, Collections, Network, Crypto) and expands Python C-ABI foreign call bridges.

Toolchain & IDE WG

Builds developer ergonomics: VS Code syntax highlighter extension, Language Server Protocol (LSP), and the in-browser sandbox.

Documentation & Book WG

Authors tutorials, curriculum tracks, language specification chapters, and the canonical 193-page PDF reference book.

Developer Contribution Guide

Want to contribute to the compiler or standard library? The codebase has zero external build dependencies:

Local Compiler Setup & Test Suite Execution
# 1. Clone repository git clone https://github.com/enlangg/enlangg.git cd enlangg # 2. Build local compiler binary with GCC or Clang gcc -O3 website/enlng.c -o enlng # 3. Run built-in regression test suite ./enlng run enlang-core/tests/fibonacci.enlng ./enlng run enlang-core/tests/mew.enlng

The RFC (Request for Comments) Proposal Process

Any modification to language grammar or standard library signatures must follow the RFC lifecycle:

  1. Draft Stage: Author an RFC markdown document outlining motivation, grammar BNF, memory impact, and example Enlangg code.
  2. Working Group Review: The Core Compiler WG reviews the proposal against the Sovereign Invariants (zero cryptic symbols, zero GC).
  3. Experimental Implementation: Implement syntax parsing behind an experimental CLI flag (--experimental-rfc-N).
  4. Formal Standardization: Merge into the official specification and release in next minor version.