Home /Modules/impl/EVENTS_OS.md

EVENTS_OS.md

impl/EVENTS_OS.md · 34 line(s) · markdown

SLeeLa Signals / Events — OS Facility Contract

Purpose

SLeeLa needs one runtime-facing event contract so signal notifications and application events do not require platform-specific code in the VM.

Backends

Contract

impl/core/sleela_events.h provides:

The queue is deliberately bounded. Producers receive EAGAIN when it is full rather than silently losing an event.

Portability boundary

Runtime code should use sleela_events.h rather than directly calling Win32 event APIs or POSIX signal/event primitives. This keeps platform decisions in one implementation boundary and complements the existing threading, I/O, networking, path, terminal, native-library, and memory facilities.

Security

Signals and events are notification mechanisms, not trust mechanisms. Existing SLeeLa SHA-256 verification remains the authoritative pre-build and pre-execution integrity gate.

Smoke test

core/events_platform_smoke.c verifies event lifecycle, timeout behavior, queue delivery, and (where supported) signal notification.