Expand description
Closed-program bytecode artifact and program-scoped module repository.
Ordinary module artifacts are caller-independent and therefore retain their complete export surface. A linked program is different: its graph and every namespace use are closed at build time, so the linker may specialize module exports without weakening generic cache correctness. The runtime installs the decoded module templates for one VM execution tree; it never inserts them into the ordinary source-keyed cache.
Structs§
- Link
Module Report - Link
Report - Link
Symbol Reason - Linked
Program Artifact - Linked
Program Error - Linked
Program Identity - Linked
Program Runtime
Enums§
Constants§
Functions§
- graph_
digest_ from_ sources - Digest the exact normalized source graph compiled into a linked program. The pack verifier reconstructs this independently from verified archive sources plus the current embedded stdlib modules before installation.
- link_
program - Compile and specialize one closed source graph into the runtime’s single linked-program artifact. Package policy, signing, and source inclusion stay with the archive caller; graph discovery and bytecode reachability live here.
- verify_
graph_ binding - Reconstruct and verify a linked graph from independently verified user sources plus the runtime’s embedded stdlib. Archive verification and direct execution share this boundary so neither can accept a self-consistent but manifest-detached artifact.