Scheduling, Blocking and Structured Concurrency

Placeholder: This chapter is intentionally not complete yet. The scheduling, blocking and structured-concurrency material is still being synchronized. This page exists now so manual navigation through chapters 1–60 remains complete and does not lead to a missing page.

Current Status

Sec already has substantial rules for scheduling and blocking, but the complete structured-concurrency model is not yet ready to be presented as final manual documentation. These areas are tightly coupled to tasks, threads, cancellation, await, channels, select, mutexes and target-profile behavior.

The final chapter will be written when the relevant rulebooks have been updated and synchronized into one stable model.

Why This Page Is a Placeholder

Scheduling determines where and when execution may run. Blocking determines when a physical worker or thread may wait. Structured concurrency determines how spawned work remains tied to an owning lifecycle. These rules cannot be documented safely in isolation while one part of the model is still being finalized.

Rather than freeze an intermediate design into the manual, this page deliberately remains short until the normative source material is complete.

Expected Scope

The completed chapter is expected to cover scheduler-visible execution, suspension versus physical blocking, worker availability, starvation constraints, blocking policy, structured parent/child lifecycles, cleanup obligations, cancellation interaction and target-profile restrictions.

Exact public declarations, guarantees, diagnostics and examples will be added only after the scheduling, blocking and structured-concurrency rulebooks agree on the final Sec 0.1 model.

Next Step

This placeholder should be replaced as soon as the remaining structured-concurrency work is normative and synchronized with the current task, await and cancellation rules. The replacement should describe only the current language model, not the transition from older drafts.