Module System

The Semantic module layer is intended to resolve multiple artifact kinds through one universal boundary.

Supported module inputs can include:

• source files;
• .se Semantic source;
• .sp / .spz semantic transport;
• assembly/native artifacts;
• PE/COFF artifacts.

Cache model

Semantic modules can be cached content-addressably. A trustworthy cache entry must bind together the semantic payload and the information that determines its meaning, such as source hash, schema/frontend version, semantic root, dependencies and contracts.

Windows module cache

The documented module cache location is conceptually below:

%LOCALAPPDATA%\Semantic\Modules

with artifacts such as:

module.spz
module.se
module.meta

Why module identity matters to native linking

Native selfhosting is not only a matter of producing bytes for individual functions. Cross-unit calls, globals, layouts and semantic identities must agree across modules. That is why the project-level semantic index and linker are part of the bootstrap pipeline.