FROM SOURCE TEXT TO OWNED MACHINE CODE.
v13 extends the compiler architecture instead of replacing it. Canonical semantics, Native MIR, target legalization, bounded optimization, deterministic allocation, instruction selection and DByte-owned object writers remain separate owners.
00 production native path
SOURCE -> PARSER / CANONICAL HIR -> SEMANTIC ANALYSIS -> NATIVE MIR -> TARGET LEGALIZATION -> O0 or BOUNDED O1 -> LINEAR-SCAN REGISTER ALLOCATION -> TARGET INSTRUCTION SELECTION -> DBYTE OBJECT / EXECUTABLE WRITER
Backends do not get to invent language semantics. If two targets disagree on target-independent behavior, the answer is not to document two dialects. Fix the semantic owner or classify the operation as target-specific.
10 canonical semantics
The HIR layer owns profiles, types, intrinsic legality and semantic fingerprints. Native compilation consumes analyzed meaning rather than re-parsing source-level intent. That separation is why later strict-portability work can analyze one project across multiple profile/layout combinations and compare one public interface fingerprint.
20 Native MIR
Native MIR is the explicit machine-oriented IR used before final instruction encoding. It carries operations and control flow through target legalization and deterministic register allocation. The 12.4 manual remains the detailed owner for Native MIR, O0/O1, allocation and inspection. v13 reuses that path for freestanding work instead of creating a second “kernel compiler.”
30 optimization without a mystery box
O1 is bounded. The value is not a magic “optimized” badge; the value is that MIR, allocation and emitted bytes remain inspectable. A transform that cannot preserve the named semantic contract does not belong merely because another compiler might perform it.
40 target boundaries
Hosted execution, VM execution, i686, x86_64 Linux, x86_64 Windows and freestanding x86_64 are different execution profiles. Sharing semantics does not erase ABI and hardware differences. Calling convention, relocation format, object writer, privileged operations and machine capability checks stay target-owned.