Memory and representation

Ordinary source retains a manual/raw contract. The compiler does not introduce ownership, general bounds checks, automatic pointer-lifetime validation or hidden release. Type properties must be distinguished from memory-safety guarantees.

Representation covers size, alignment, offsets, padding and ABI. An aggregate may have a valid in-memory layout while requiring additional rules for argument passing or return values. Data layout and calling convention must be checked together.

V81 materializes alignments above 16 bytes on the documented native Windows and Linux/WSL x86-64 profiles. Evidence covers powers of two from 32 bytes to 1 MiB. COFF section alignment is limited to 8192 bytes in this work; direct PE and ELF paths support larger alignments within the documented profile.

A request that the format cannot represent must be rejected. Silent truncation changes the actual address while reporting apparent success. Material verification checks ranges, powers of two and offsets before consuming the artifact.

The stack is also a material constraint. Large Windows tests declare a 16 MiB reserve; Linux ABI tests adjust the stack limit according to the reproduction recipe. The emitter touches stack pages in the documented profile. This does not add an implicit heap or remove system limits.

Layout checks across ten profiles are representation calculations. V81 physical execution evidence applies to the stated x86-64 hosts. These establish different kinds of support and should be reported separately.