Compiler architecture

Program flow on the left. Trust evidence on the right.

The diagram separates transformations from the checks that authorize them. A stage existing in research does not mean every surface program reaches it today.

Semantic authority
Typed Core
Native target
x86-64
LLVM in path
None
  1. 01

    .nx source surface

    Available

    Span-aware lexing, parsing, diagnostics, and the learner execution surface.

    Open contract
    OutputParsed surface program
    GateSource positions · deterministic diagnostics
  2. 02

    Canonical Typed Core

    Bounded

    Typed ANF makes effects, regions, ownership obligations, and observations explicit.

    Open contract
    OutputVerified Typed Core
    GateType · effect · region · ownership evidence
  3. 03

    Specialization

    Research

    Binding-time analysis, static evaluation, and residualization remove admitted static work.

    Open contract
    OutputResidual Typed Core
    GateSealed certificate · independent replay
  4. 04

    Canonical residual SSA

    Bounded

    A deterministic control/data-flow form becomes the boundary for native lowering.

    Open contract
    OutputValidated SSA image
    GateTranslation validation · correspondence roots
  5. 05

    Machine IR + x86-64

    Experimental

    Target planning selects an admitted instruction plan and checked encoding emits bytes.

    Open contract
    OutputOwned machine-byte capsule
    GateMachine verifier · independent decoder
  6. 06

    Native artifact

    Experimental

    W^X execution and direct ELF64 experiments run admitted images without LLVM or libc startup.

    Open contract
    OutputRunner / standalone ELF
    GateGate B · containment · dependency inventory

Non-negotiable boundaries

What the diagram means

01 · Authority
Executable typed semantics define meaning. Fast engines are implementations, not alternative semantics.
02 · Admission
Unsupported states fail closed. Optimization does not erase a proof obligation merely because the result is faster.
03 · Independence
Certificates are useful only when a smaller, independent path can replay or validate them.
04 · Dependency truth
The compiler is currently Rust/Cargo-seeded and retains acknowledged egg bridge debt. Sovereignty remains a gated target.