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, panics, schedules fibers, and talks to the OS without asking your permission.
This chapter maps the Execution domain to beskid_abi, beskid_engine, 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. |
architecture-beta accTitle: Execution layers accDescr: Generated code from the codegen and engine crates calls through the beskid_abi contract into runtime services, which reach the operating system through syscalls. group gen(server)[Generated code] service codegen(server)[beskid_codegen and beskid_engine] in gen group contract(server)[Execution contract] service abi(server)[beskid_abi] in contract service rt(server)[Runtime services] in contract service os(internet)[OS and syscalls] codegen:R --> L:abi abi:R --> L:rt rt:R --> L:os
Text equivalent: Code produced by beskid_codegen and beskid_engine crosses the beskid_abi contract into runtime services, which call the operating system.