17. Execution: ABI, host, and runtime
What happens after the compiler stops pretending—ABI contracts, host integration, fibers, and syscall bridges.
Execution: ABI, host, and runtime
Compilation is the part you can screenshot for LinkedIn. Execution is the part that actually runs—and panics, schedules fibers, and talks to the OS without asking your permission.
This chapter maps the Execution domain to beskid_abi, beskid_runtime, and the conformance evidence that keeps the reference platform honest.
What you will find here
Section titled “What you will find here”| Section | Topic |
|---|---|
| Execution domain | Domain map and where language law ends. |
| ABI and host | Versioning, extern dispatch, host integration. |
| Runtime fibers | Scheduler, stacks, cooperative model. |
| Panic, IO, syscalls | Process termination, IO surfaces, syscall policy. |
| Conformance evidence | Tests and spec traceability. |
flowchart TB codegen[beskid_codegen / engine] --> abi[beskid_abi] abi --> rt[beskid_runtime] rt --> os[OS / syscalls] lang[Language-meta evaluation] --> rt