Keep unsuitable work native.
Flyology Runtime is experimental. If a task requires kernel real-time scheduling, forced preemption, native CPU affinity, or unpredictable foreign blocking, keep it native. Also keep it native on a host and compiler combination outside the verified patch matrix.
- Use lightweight
- High I/O concurrency with cooperative work, explicit task-aware waits, and ordinary Ada task semantics.
- Use native
- Blocking foreign libraries, kernel scheduling policies, independent OS-thread execution, or unmodified compatibility behavior.
- Use dedicated
- A lightweight continuation must temporarily own a stable event-loop thread exclusively.