Self-Hosting Readiness

Self-Hosting Readiness means the compiler can reproduce itself through the

trusted compiler chain without relying on the stage -1 seed as the normal path.

Trusted Compiler

The default make path expects a trusted release compiler under

build/release/v0.1.0/bin/zero-elf-compiler. The seed is retained for recovery

and audit.

Gate

Run:

make selfhost-guard

The gate checks stage2/stage3 equivalence, ELF compiler equivalence, and smoke

tests. It is heavy and should be run by commit hooks or explicit release work,

not as a default public-docs gate.

Readiness Tracker

Self-hosting readiness requires:

• stage2/stage3 byte equality;
• ELF OISA compiler parity;
• self-replicating ELF compiler builder parity;
• smoke tests;
• release helper manifest synchronization;
• documentation impact review for behavior changes.