GitHub

Public scope ladder

Six finish lines, one direction.

Each scope is independently useful and has its own evidence gate. The roadmap states public outcomes and claim boundaries—not dates or private implementation tickets.

Available
1
Active
1
Defined
4

Now

Usable surface and inspectable research artifact

  1. S1Available

    NAUX Learn

    A small language profile for programming and algorithm study.

    Exit evidence
    Prebuilt Linux binary, deterministic I/O, diagnostics, and a 30-exercise corpus.
    Claim boundary
    No production, sovereignty, or native-performance claim.
    Inspect this boundary
  2. S2Active

    Research Preview

    An inspectable compiler artifact for researchers and early evaluators.

    Exit evidence
    Reproducible semantic, specialization, evidence, and native-path experiments.
    Claim boundary
    LLVM-free and Rust-seeded while dependency debt remains explicit.
    Inspect this boundary

Next

A bounded thesis artifact and defensible performance evidence

  1. S3Defined

    Trusted Thesis Core

    A bounded end-to-end artifact suitable for independent evaluation.

    Exit evidence
    One frozen Typed Core profile reaches proof-gated native compilation.
    Claim boundary
    Claims apply only to the admitted profile and replayed evidence.
    Inspect this boundary
  2. S4Defined

    Performance Alpha

    Repeatable performance evidence on named workloads and hosts.

    Exit evidence
    Stable harness, disclosed environment, matched semantics, raw samples, and claim review.
    Claim boundary
    Measured workload claims only—never “NAUX beats C/C++” in general.
    Inspect this boundary

Horizon

Sovereign construction and the generative lifecycle

  1. S5Defined

    Sovereign NAUX

    Remove temporary compiler and runtime infrastructure from the normal trust path.

    Exit evidence
    Dependency, loader, runtime, object, linker, and target closure demonstrated explicitly.
    Claim boundary
    Sovereignty is proven per target; it is never inferred from intent.
    Inspect this boundary
  2. S6Defined

    Nauxogenesis

    A reproducible compiler-generating lifecycle derived from executable semantics.

    Exit evidence
    Every named semantic, generative, dependency, and reproducibility closure gate passes.
    Claim boundary
    A distinct generative lifecycle—not a conventional self-hosting claim.
    Inspect this boundary