100  Control Flow, Coordination, and Temporal Logic

101 Control Flow, Coordination, and Temporal Logic

Range: 0512-0608.

101.1 Completion

Status	Count
authored	97

Use the summary table for scanning. Each row links to the detailed anchored entry below.

Sigil	Term	Completion	Semantic	Summary
0512	abort	authored	generated_draft	abort is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the abort obligation named before work proceeds.
0513	acknowledge	authored	generated_draft	acknowledge is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the acknowledge obligation named before work proceeds.
0514	async	authored	reviewed	Work may proceed without immediate blocking at the call site.
0515	await	authored	reviewed	Pause until an asynchronous result becomes ready.
0516	backoff {Ctrl}	authored	reviewed	Wait longer between retries so recovery does not become attack.
0517	barrier {Ctrl}	authored	reviewed	A synchronization point no participant may cross early.
0518	block {Ctrl}	authored	generated_draft	block in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the block obligation named before work proceeds.
0519	branch {Ctrl}	authored	generated_draft	branch in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the branch obligation named before work proceeds.
0520	break	authored	generated_draft	break is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the break obligation named before work proceeds.
0521	callback	authored	generated_draft	callback is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the callback obligation named before work proceeds.
0522	cancel	authored	generated_draft	cancel is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the cancel obligation named before work proceeds.
0523	case	authored	generated_draft	case is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the case obligation named before work proceeds.
0524	catch	authored	generated_draft	catch is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the catch obligation named before work proceeds.
0525	chain	authored	generated_draft	chain is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the chain obligation named before work proceeds.
0526	choose	authored	generated_draft	choose is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the choose obligation named before work proceeds.
0527	circuit breaker	authored	reviewed	Trip open after repeated failure to prevent repeated harm.
0528	clause	authored	generated_draft	clause is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the clause obligation named before work proceeds.
0529	continue	authored	generated_draft	continue is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the continue obligation named before work proceeds.
0530	coroutine	authored	reviewed	A suspendable routine that can yield and later resume.
0531	countdown	authored	generated_draft	countdown is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the countdown obligation named before work proceeds.
0532	cycle	authored	generated_draft	cycle is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the cycle obligation named before work proceeds.
0533	debounce	authored	generated_draft	debounce is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the debounce obligation named before work proceeds.
0534	defer {Ctrl}	authored	generated_draft	defer in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the defer obligation named before work proceeds.
0535	delay	authored	generated_draft	delay is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the delay obligation named before work proceeds.
0536	dispatch {Ctrl}	authored	generated_draft	dispatch in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the dispatch obligation named before work proceeds.
0537	do	authored	generated_draft	do is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the do obligation named before work proceeds.
0538	else	authored	generated_draft	else is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the else obligation named before work proceeds.
0539	enqueue	authored	reviewed	Place work onto a queue for later handling.
0540	event loop	authored	reviewed	The scheduler that drives nonblocking tasks and callbacks.
0541	fallback {Ctrl}	authored	generated_draft	fallback in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fallback obligation named before work proceeds.
0542	fan-in	authored	generated_draft	fan-in is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fan-in obligation named before work proceeds.
0543	fan-out {Ctrl}	authored	generated_draft	fan-out in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fan-out obligation named before work proceeds.
0544	finally	authored	generated_draft	finally is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the finally obligation named before work proceeds.
0545	fire-and-forget	authored	generated_draft	fire-and-forget is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fire-and-forget obligation named before work proceeds.
0546	flow control	authored	reviewed	Mechanisms that keep producers from outrunning consumers.
0547	for	authored	generated_draft	for is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the for obligation named before work proceeds.
0548	fork {Ctrl}	authored	generated_draft	fork in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fork obligation named before work proceeds.
0549	future	authored	reviewed	A placeholder for a value that will exist later.
0550	gate	authored	generated_draft	gate is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the gate obligation named before work proceeds.
0551	guard	authored	generated_draft	guard is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the guard obligation named before work proceeds.
0552	halt	authored	generated_draft	halt is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the halt obligation named before work proceeds.
0553	heartbeat {Ctrl}	authored	generated_draft	heartbeat in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the heartbeat obligation named before work proceeds.
0554	if	authored	generated_draft	if is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the if obligation named before work proceeds.
0555	iterate	authored	generated_draft	iterate is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the iterate obligation named before work proceeds.
0556	join {Ctrl}	authored	generated_draft	join in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the join obligation named before work proceeds.
0557	jump	authored	generated_draft	jump is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the jump obligation named before work proceeds.
0558	latch	authored	generated_draft	latch is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the latch obligation named before work proceeds.
0559	loop	authored	generated_draft	loop is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the loop obligation named before work proceeds.
0560	match	authored	generated_draft	match is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the match obligation named before work proceeds.
0561	mutex	authored	reviewed	Mutual exclusion for one critical region at a time.
0562	notify	authored	generated_draft	notify is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the notify obligation named before work proceeds.
0563	once	authored	generated_draft	once is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the once obligation named before work proceeds.
0564	parallel {Ctrl}	authored	generated_draft	parallel in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the parallel obligation named before work proceeds.
0565	pause	authored	generated_draft	pause is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the pause obligation named before work proceeds.
0566	poll {Ctrl}	authored	generated_draft	poll in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the poll obligation named before work proceeds.
0567	preempt	authored	generated_draft	preempt is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the preempt obligation named before work proceeds.
0568	priority	authored	generated_draft	priority is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the priority obligation named before work proceeds.
0569	process {Ctrl}	authored	generated_draft	process in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the process obligation named before work proceeds.
0570	promise	authored	generated_draft	promise is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the promise obligation named before work proceeds.
0571	queue {Ctrl}	authored	reviewed	Ordered holding area that decouples production from consumption.
0572	race window	authored	generated_draft	race window is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the race window obligation named before work proceeds.
0573	recurse	authored	generated_draft	recurse is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the recurse obligation named before work proceeds.
0574	repeat	authored	generated_draft	repeat is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the repeat obligation named before work proceeds.
0575	reserve	authored	generated_draft	reserve is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the reserve obligation named before work proceeds.
0576	retry {Ctrl}	authored	reviewed	Failure does not necessarily end the ritual; policy may permit another attempt. Shadow: blind repetition against a broken precondition.
0577	return	authored	generated_draft	return is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the return obligation named before work proceeds.
0578	round-robin	authored	generated_draft	round-robin is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the round-robin obligation named before work proceeds.
0579	schedule {Ctrl}	authored	reviewed	Assign work to time, order, or execution slots.
0580	select {Ctrl}	authored	generated_draft	select in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the select obligation named before work proceeds.
0581	semaphore	authored	reviewed	A counted gate controlling concurrent access to limited capacity.
0582	sequence point	authored	generated_draft	sequence point is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the sequence point obligation named before work proceeds.
0583	serialize access	authored	generated_draft	serialize access is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the serialize access obligation named before work proceeds.
0584	signal {Ctrl}	authored	reviewed	Emit a condition change another task may respond to.
0585	sleep	authored	generated_draft	sleep is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the sleep obligation named before work proceeds.
0586	spawn {Ctrl}	authored	generated_draft	spawn in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the spawn obligation named before work proceeds.
0587	step	authored	generated_draft	step is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the step obligation named before work proceeds.
0588	stop	authored	generated_draft	stop is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the stop obligation named before work proceeds.
0589	suspend	authored	generated_draft	suspend is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the suspend obligation named before work proceeds.
0590	switch	authored	generated_draft	switch is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the switch obligation named before work proceeds.
0591	sync	authored	generated_draft	sync is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the sync obligation named before work proceeds.
0592	synchronize	authored	generated_draft	synchronize is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the synchronize obligation named before work proceeds.
0593	task	authored	generated_draft	task is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the task obligation named before work proceeds.
0594	terminate	authored	generated_draft	terminate is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the terminate obligation named before work proceeds.
0595	then	authored	generated_draft	then is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the then obligation named before work proceeds.
0596	throttle	authored	generated_draft	throttle is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the throttle obligation named before work proceeds.
0597	tick	authored	generated_draft	tick is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the tick obligation named before work proceeds.
0598	timeout {Ctrl}	authored	reviewed	Waiting is not free and patience must have a boundary. A timeout is a contract with reality about how long uncertainty is allowed to persist.
0599	timeslice	authored	generated_draft	timeslice is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the timeslice obligation named before work proceeds.
0600	trigger	authored	generated_draft	trigger is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the trigger obligation named before work proceeds.
0601	try	authored	generated_draft	try is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the try obligation named before work proceeds.
0602	unblock	authored	generated_draft	unblock is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the unblock obligation named before work proceeds.
0603	until	authored	generated_draft	until is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the until obligation named before work proceeds.
0604	wait	authored	generated_draft	wait is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the wait obligation named before work proceeds.
0605	wake	authored	generated_draft	wake is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the wake obligation named before work proceeds.
0606	when	authored	generated_draft	when is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the when obligation named before work proceeds.
0607	while	authored	generated_draft	while is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the while obligation named before work proceeds.
0608	yield	authored	reviewed	Give up control now so another act may proceed.

101.2 Entries

101.2.1 [0512] abort

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: abort is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the abort obligation named before work proceeds.

Shadow: misusing abort at rune 0512 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name abort when the prompt needs this obligation made explicit: abort is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the abort obligation named before work proceeds.
• Ask the assistant to state the abort shadow before proposing changes.

Example clause:

Before editing, state the abort obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.2 [0513] acknowledge

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: acknowledge is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the acknowledge obligation named before work proceeds.

Shadow: misusing acknowledge at rune 0513 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name acknowledge when the prompt needs this obligation made explicit: acknowledge is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the acknowledge obligation named before work proceeds.
• Ask the assistant to state the acknowledge shadow before proposing changes.

Example clause:

Before editing, state the acknowledge obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.3 [0514] async

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Work may proceed without immediate blocking at the call site.

Shadow: misusing async at rune 0514 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name async when the prompt needs this obligation made explicit: Work may proceed without immediate blocking at the call site.
• Ask the assistant to state the async shadow before proposing changes.

Example clause:

Before editing, state the async obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Work may proceed without immediate blocking at the call site.

101.2.4 [0515] await

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Pause until an asynchronous result becomes ready.

Shadow: misusing await at rune 0515 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name await when the prompt needs this obligation made explicit: Pause until an asynchronous result becomes ready.
• Ask the assistant to state the await shadow before proposing changes.

Example clause:

Before editing, state the await obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Pause until an asynchronous result becomes ready.

101.2.5 [0516] backoff {Ctrl}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Wait longer between retries so recovery does not become attack.

Shadow: misusing backoff at rune 0516 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name backoff when the prompt needs this obligation made explicit: Wait longer between retries so recovery does not become attack.
• Ask the assistant to state the backoff shadow before proposing changes.

Example clause:

Before editing, state the backoff obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Wait longer between retries so recovery does not become attack.

101.2.6 [0517] barrier {Ctrl}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A synchronization point no participant may cross early.

Shadow: misusing barrier at rune 0517 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name barrier when the prompt needs this obligation made explicit: A synchronization point no participant may cross early.
• Ask the assistant to state the barrier shadow before proposing changes.

Example clause:

Before editing, state the barrier obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A synchronization point no participant may cross early.

101.2.7 [0518] block {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: block in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the block obligation named before work proceeds.

Shadow: misusing block at rune 0518 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name block when the prompt needs this obligation made explicit: block in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the block obligation named before work proceeds.
• Ask the assistant to state the block shadow before proposing changes.

Example clause:

Before editing, state the block obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.8 [0519] branch {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: branch in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the branch obligation named before work proceeds.

Shadow: misusing branch at rune 0519 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name branch when the prompt needs this obligation made explicit: branch in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the branch obligation named before work proceeds.
• Ask the assistant to state the branch shadow before proposing changes.

Example clause:

Before editing, state the branch obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.9 [0520] break

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: break is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the break obligation named before work proceeds.

Shadow: misusing break at rune 0520 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name break when the prompt needs this obligation made explicit: break is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the break obligation named before work proceeds.
• Ask the assistant to state the break shadow before proposing changes.

Example clause:

Before editing, state the break obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.10 [0521] callback

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: callback is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the callback obligation named before work proceeds.

Shadow: misusing callback at rune 0521 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name callback when the prompt needs this obligation made explicit: callback is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the callback obligation named before work proceeds.
• Ask the assistant to state the callback shadow before proposing changes.

Example clause:

Before editing, state the callback obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.11 [0522] cancel

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cancel is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the cancel obligation named before work proceeds.

Shadow: misusing cancel at rune 0522 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name cancel when the prompt needs this obligation made explicit: cancel is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the cancel obligation named before work proceeds.
• Ask the assistant to state the cancel shadow before proposing changes.

Example clause:

Before editing, state the cancel obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.12 [0523] case

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: case is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the case obligation named before work proceeds.

Shadow: misusing case at rune 0523 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name case when the prompt needs this obligation made explicit: case is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the case obligation named before work proceeds.
• Ask the assistant to state the case shadow before proposing changes.

Example clause:

Before editing, state the case obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.13 [0524] catch

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: catch is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the catch obligation named before work proceeds.

Shadow: misusing catch at rune 0524 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name catch when the prompt needs this obligation made explicit: catch is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the catch obligation named before work proceeds.
• Ask the assistant to state the catch shadow before proposing changes.

Example clause:

Before editing, state the catch obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.14 [0525] chain

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: chain is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the chain obligation named before work proceeds.

Shadow: misusing chain at rune 0525 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name chain when the prompt needs this obligation made explicit: chain is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the chain obligation named before work proceeds.
• Ask the assistant to state the chain shadow before proposing changes.

Example clause:

Before editing, state the chain obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.15 [0526] choose

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: choose is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the choose obligation named before work proceeds.

Shadow: misusing choose at rune 0526 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name choose when the prompt needs this obligation made explicit: choose is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the choose obligation named before work proceeds.
• Ask the assistant to state the choose shadow before proposing changes.

Example clause:

Before editing, state the choose obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.16 [0527] circuit breaker

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Trip open after repeated failure to prevent repeated harm.

Shadow: misusing circuit breaker at rune 0527 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name circuit breaker when the prompt needs this obligation made explicit: Trip open after repeated failure to prevent repeated harm.
• Ask the assistant to state the circuit breaker shadow before proposing changes.

Example clause:

Before editing, state the circuit breaker obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Trip open after repeated failure to prevent repeated harm.

101.2.17 [0528] clause

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: clause is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the clause obligation named before work proceeds.

Shadow: misusing clause at rune 0528 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name clause when the prompt needs this obligation made explicit: clause is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the clause obligation named before work proceeds.
• Ask the assistant to state the clause shadow before proposing changes.

Example clause:

Before editing, state the clause obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.18 [0529] continue

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: continue is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the continue obligation named before work proceeds.

Shadow: misusing continue at rune 0529 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name continue when the prompt needs this obligation made explicit: continue is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the continue obligation named before work proceeds.
• Ask the assistant to state the continue shadow before proposing changes.

Example clause:

Before editing, state the continue obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.19 [0530] coroutine

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A suspendable routine that can yield and later resume.

Shadow: misusing coroutine at rune 0530 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name coroutine when the prompt needs this obligation made explicit: A suspendable routine that can yield and later resume.
• Ask the assistant to state the coroutine shadow before proposing changes.

Example clause:

Before editing, state the coroutine obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A suspendable routine that can yield and later resume.

101.2.20 [0531] countdown

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: countdown is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the countdown obligation named before work proceeds.

Shadow: misusing countdown at rune 0531 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name countdown when the prompt needs this obligation made explicit: countdown is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the countdown obligation named before work proceeds.
• Ask the assistant to state the countdown shadow before proposing changes.

Example clause:

Before editing, state the countdown obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.21 [0532] cycle

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cycle is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the cycle obligation named before work proceeds.

Shadow: misusing cycle at rune 0532 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name cycle when the prompt needs this obligation made explicit: cycle is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the cycle obligation named before work proceeds.
• Ask the assistant to state the cycle shadow before proposing changes.

Example clause:

Before editing, state the cycle obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.22 [0533] debounce

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: debounce is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the debounce obligation named before work proceeds.

Shadow: misusing debounce at rune 0533 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name debounce when the prompt needs this obligation made explicit: debounce is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the debounce obligation named before work proceeds.
• Ask the assistant to state the debounce shadow before proposing changes.

Example clause:

Before editing, state the debounce obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.23 [0534] defer {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: defer in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the defer obligation named before work proceeds.

Shadow: misusing defer at rune 0534 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name defer when the prompt needs this obligation made explicit: defer in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the defer obligation named before work proceeds.
• Ask the assistant to state the defer shadow before proposing changes.

Example clause:

Before editing, state the defer obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.24 [0535] delay

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: delay is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the delay obligation named before work proceeds.

Shadow: misusing delay at rune 0535 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name delay when the prompt needs this obligation made explicit: delay is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the delay obligation named before work proceeds.
• Ask the assistant to state the delay shadow before proposing changes.

Example clause:

Before editing, state the delay obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.25 [0536] dispatch {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: dispatch in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the dispatch obligation named before work proceeds.

Shadow: misusing dispatch at rune 0536 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name dispatch when the prompt needs this obligation made explicit: dispatch in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the dispatch obligation named before work proceeds.
• Ask the assistant to state the dispatch shadow before proposing changes.

Example clause:

Before editing, state the dispatch obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.26 [0537] do

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: do is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the do obligation named before work proceeds.

Shadow: misusing do at rune 0537 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name do when the prompt needs this obligation made explicit: do is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the do obligation named before work proceeds.
• Ask the assistant to state the do shadow before proposing changes.

Example clause:

Before editing, state the do obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.27 [0538] else

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: else is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the else obligation named before work proceeds.

Shadow: misusing else at rune 0538 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name else when the prompt needs this obligation made explicit: else is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the else obligation named before work proceeds.
• Ask the assistant to state the else shadow before proposing changes.

Example clause:

Before editing, state the else obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.28 [0539] enqueue

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Place work onto a queue for later handling.

Shadow: misusing enqueue at rune 0539 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name enqueue when the prompt needs this obligation made explicit: Place work onto a queue for later handling.
• Ask the assistant to state the enqueue shadow before proposing changes.

Example clause:

Before editing, state the enqueue obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Place work onto a queue for later handling.

101.2.29 [0540] event loop

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The scheduler that drives nonblocking tasks and callbacks.

Shadow: misusing event loop at rune 0540 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name event loop when the prompt needs this obligation made explicit: The scheduler that drives nonblocking tasks and callbacks.
• Ask the assistant to state the event loop shadow before proposing changes.

Example clause:

Before editing, state the event loop obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: The scheduler that drives nonblocking tasks and callbacks.

101.2.30 [0541] fallback {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fallback in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fallback obligation named before work proceeds.

Shadow: misusing fallback at rune 0541 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name fallback when the prompt needs this obligation made explicit: fallback in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fallback obligation named before work proceeds.
• Ask the assistant to state the fallback shadow before proposing changes.

Example clause:

Before editing, state the fallback obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.31 [0542] fan-in

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fan-in is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fan-in obligation named before work proceeds.

Shadow: misusing fan-in at rune 0542 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name fan-in when the prompt needs this obligation made explicit: fan-in is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fan-in obligation named before work proceeds.
• Ask the assistant to state the fan-in shadow before proposing changes.

Example clause:

Before editing, state the fan-in obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.32 [0543] fan-out {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fan-out in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fan-out obligation named before work proceeds.

Shadow: misusing fan-out at rune 0543 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name fan-out when the prompt needs this obligation made explicit: fan-out in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fan-out obligation named before work proceeds.
• Ask the assistant to state the fan-out shadow before proposing changes.

Example clause:

Before editing, state the fan-out obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.33 [0544] finally

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: finally is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the finally obligation named before work proceeds.

Shadow: misusing finally at rune 0544 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name finally when the prompt needs this obligation made explicit: finally is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the finally obligation named before work proceeds.
• Ask the assistant to state the finally shadow before proposing changes.

Example clause:

Before editing, state the finally obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.34 [0545] fire-and-forget

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fire-and-forget is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fire-and-forget obligation named before work proceeds.

Shadow: misusing fire-and-forget at rune 0545 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name fire-and-forget when the prompt needs this obligation made explicit: fire-and-forget is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fire-and-forget obligation named before work proceeds.
• Ask the assistant to state the fire-and-forget shadow before proposing changes.

Example clause:

Before editing, state the fire-and-forget obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.35 [0546] flow control

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Mechanisms that keep producers from outrunning consumers.

Shadow: misusing flow control at rune 0546 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name flow control when the prompt needs this obligation made explicit: Mechanisms that keep producers from outrunning consumers.
• Ask the assistant to state the flow control shadow before proposing changes.

Example clause:

Before editing, state the flow control obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Mechanisms that keep producers from outrunning consumers.

101.2.36 [0547] for

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: for is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the for obligation named before work proceeds.

Shadow: misusing for at rune 0547 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name for when the prompt needs this obligation made explicit: for is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the for obligation named before work proceeds.
• Ask the assistant to state the for shadow before proposing changes.

Example clause:

Before editing, state the for obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.37 [0548] fork {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fork in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fork obligation named before work proceeds.

Shadow: misusing fork at rune 0548 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name fork when the prompt needs this obligation made explicit: fork in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the fork obligation named before work proceeds.
• Ask the assistant to state the fork shadow before proposing changes.

Example clause:

Before editing, state the fork obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.38 [0549] future

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A placeholder for a value that will exist later.

Shadow: misusing future at rune 0549 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name future when the prompt needs this obligation made explicit: A placeholder for a value that will exist later.
• Ask the assistant to state the future shadow before proposing changes.

Example clause:

Before editing, state the future obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A placeholder for a value that will exist later.

101.2.39 [0550] gate

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: gate is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the gate obligation named before work proceeds.

Shadow: misusing gate at rune 0550 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name gate when the prompt needs this obligation made explicit: gate is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the gate obligation named before work proceeds.
• Ask the assistant to state the gate shadow before proposing changes.

Example clause:

Before editing, state the gate obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.40 [0551] guard

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: guard is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the guard obligation named before work proceeds.

Shadow: misusing guard at rune 0551 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name guard when the prompt needs this obligation made explicit: guard is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the guard obligation named before work proceeds.
• Ask the assistant to state the guard shadow before proposing changes.

Example clause:

Before editing, state the guard obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.41 [0552] halt

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: halt is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the halt obligation named before work proceeds.

Shadow: misusing halt at rune 0552 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name halt when the prompt needs this obligation made explicit: halt is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the halt obligation named before work proceeds.
• Ask the assistant to state the halt shadow before proposing changes.

Example clause:

Before editing, state the halt obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.42 [0553] heartbeat {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: heartbeat in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the heartbeat obligation named before work proceeds.

Shadow: misusing heartbeat at rune 0553 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name heartbeat when the prompt needs this obligation made explicit: heartbeat in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the heartbeat obligation named before work proceeds.
• Ask the assistant to state the heartbeat shadow before proposing changes.

Example clause:

Before editing, state the heartbeat obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.43 [0554] if

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: if is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the if obligation named before work proceeds.

Shadow: misusing if at rune 0554 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name if when the prompt needs this obligation made explicit: if is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the if obligation named before work proceeds.
• Ask the assistant to state the if shadow before proposing changes.

Example clause:

Before editing, state the if obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.44 [0555] iterate

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: iterate is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the iterate obligation named before work proceeds.

Shadow: misusing iterate at rune 0555 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name iterate when the prompt needs this obligation made explicit: iterate is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the iterate obligation named before work proceeds.
• Ask the assistant to state the iterate shadow before proposing changes.

Example clause:

Before editing, state the iterate obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.45 [0556] join {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: join in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the join obligation named before work proceeds.

Shadow: misusing join at rune 0556 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name join when the prompt needs this obligation made explicit: join in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the join obligation named before work proceeds.
• Ask the assistant to state the join shadow before proposing changes.

Example clause:

Before editing, state the join obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.46 [0557] jump

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: jump is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the jump obligation named before work proceeds.

Shadow: misusing jump at rune 0557 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name jump when the prompt needs this obligation made explicit: jump is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the jump obligation named before work proceeds.
• Ask the assistant to state the jump shadow before proposing changes.

Example clause:

Before editing, state the jump obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.47 [0558] latch

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: latch is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the latch obligation named before work proceeds.

Shadow: misusing latch at rune 0558 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name latch when the prompt needs this obligation made explicit: latch is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the latch obligation named before work proceeds.
• Ask the assistant to state the latch shadow before proposing changes.

Example clause:

Before editing, state the latch obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.48 [0559] loop

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: loop is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the loop obligation named before work proceeds.

Shadow: misusing loop at rune 0559 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name loop when the prompt needs this obligation made explicit: loop is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the loop obligation named before work proceeds.
• Ask the assistant to state the loop shadow before proposing changes.

Example clause:

Before editing, state the loop obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.49 [0560] match

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: match is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the match obligation named before work proceeds.

Shadow: misusing match at rune 0560 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name match when the prompt needs this obligation made explicit: match is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the match obligation named before work proceeds.
• Ask the assistant to state the match shadow before proposing changes.

Example clause:

Before editing, state the match obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.50 [0561] mutex

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Mutual exclusion for one critical region at a time.

Shadow: misusing mutex at rune 0561 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name mutex when the prompt needs this obligation made explicit: Mutual exclusion for one critical region at a time.
• Ask the assistant to state the mutex shadow before proposing changes.

Example clause:

Before editing, state the mutex obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Mutual exclusion for one critical region at a time.

101.2.51 [0562] notify

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: notify is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the notify obligation named before work proceeds.

Shadow: misusing notify at rune 0562 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name notify when the prompt needs this obligation made explicit: notify is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the notify obligation named before work proceeds.
• Ask the assistant to state the notify shadow before proposing changes.

Example clause:

Before editing, state the notify obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.52 [0563] once

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: once is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the once obligation named before work proceeds.

Shadow: misusing once at rune 0563 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name once when the prompt needs this obligation made explicit: once is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the once obligation named before work proceeds.
• Ask the assistant to state the once shadow before proposing changes.

Example clause:

Before editing, state the once obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.53 [0564] parallel {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: parallel in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the parallel obligation named before work proceeds.

Shadow: misusing parallel at rune 0564 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name parallel when the prompt needs this obligation made explicit: parallel in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the parallel obligation named before work proceeds.
• Ask the assistant to state the parallel shadow before proposing changes.

Example clause:

Before editing, state the parallel obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.54 [0565] pause

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: pause is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the pause obligation named before work proceeds.

Shadow: misusing pause at rune 0565 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name pause when the prompt needs this obligation made explicit: pause is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the pause obligation named before work proceeds.
• Ask the assistant to state the pause shadow before proposing changes.

Example clause:

Before editing, state the pause obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.55 [0566] poll {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: poll in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the poll obligation named before work proceeds.

Shadow: misusing poll at rune 0566 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name poll when the prompt needs this obligation made explicit: poll in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the poll obligation named before work proceeds.
• Ask the assistant to state the poll shadow before proposing changes.

Example clause:

Before editing, state the poll obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.56 [0567] preempt

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: preempt is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the preempt obligation named before work proceeds.

Shadow: misusing preempt at rune 0567 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name preempt when the prompt needs this obligation made explicit: preempt is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the preempt obligation named before work proceeds.
• Ask the assistant to state the preempt shadow before proposing changes.

Example clause:

Before editing, state the preempt obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.57 [0568] priority

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: priority is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the priority obligation named before work proceeds.

Shadow: misusing priority at rune 0568 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name priority when the prompt needs this obligation made explicit: priority is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the priority obligation named before work proceeds.
• Ask the assistant to state the priority shadow before proposing changes.

Example clause:

Before editing, state the priority obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.58 [0569] process {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: process in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the process obligation named before work proceeds.

Shadow: misusing process at rune 0569 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name process when the prompt needs this obligation made explicit: process in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the process obligation named before work proceeds.
• Ask the assistant to state the process shadow before proposing changes.

Example clause:

Before editing, state the process obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.59 [0570] promise

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: promise is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the promise obligation named before work proceeds.

Shadow: misusing promise at rune 0570 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name promise when the prompt needs this obligation made explicit: promise is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the promise obligation named before work proceeds.
• Ask the assistant to state the promise shadow before proposing changes.

Example clause:

Before editing, state the promise obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.60 [0571] queue {Ctrl}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Ordered holding area that decouples production from consumption.

Shadow: misusing queue at rune 0571 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name queue when the prompt needs this obligation made explicit: Ordered holding area that decouples production from consumption.
• Ask the assistant to state the queue shadow before proposing changes.

Example clause:

Before editing, state the queue obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Ordered holding area that decouples production from consumption.

101.2.61 [0572] race window

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: race window is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the race window obligation named before work proceeds.

Shadow: misusing race window at rune 0572 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name race window when the prompt needs this obligation made explicit: race window is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the race window obligation named before work proceeds.
• Ask the assistant to state the race window shadow before proposing changes.

Example clause:

Before editing, state the race window obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.62 [0573] recurse

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: recurse is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the recurse obligation named before work proceeds.

Shadow: misusing recurse at rune 0573 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name recurse when the prompt needs this obligation made explicit: recurse is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the recurse obligation named before work proceeds.
• Ask the assistant to state the recurse shadow before proposing changes.

Example clause:

Before editing, state the recurse obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.63 [0574] repeat

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: repeat is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the repeat obligation named before work proceeds.

Shadow: misusing repeat at rune 0574 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name repeat when the prompt needs this obligation made explicit: repeat is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the repeat obligation named before work proceeds.
• Ask the assistant to state the repeat shadow before proposing changes.

Example clause:

Before editing, state the repeat obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.64 [0575] reserve

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: reserve is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the reserve obligation named before work proceeds.

Shadow: misusing reserve at rune 0575 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name reserve when the prompt needs this obligation made explicit: reserve is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the reserve obligation named before work proceeds.
• Ask the assistant to state the reserve shadow before proposing changes.

Example clause:

Before editing, state the reserve obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.65 [0576] retry {Ctrl}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Failure does not necessarily end the ritual; policy may permit another attempt.

Shadow: blind repetition against a broken precondition.

Prompt uses:

• Name retry when the prompt needs this obligation made explicit: Failure does not necessarily end the ritual; policy may permit another attempt.
• Ask the assistant to state the retry shadow before proposing changes.

Example clause:

Before editing, state the retry obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Try again under policy rather than treating one failure as final.

101.2.66 [0577] return

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: return is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the return obligation named before work proceeds.

Shadow: misusing return at rune 0577 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name return when the prompt needs this obligation made explicit: return is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the return obligation named before work proceeds.
• Ask the assistant to state the return shadow before proposing changes.

Example clause:

Before editing, state the return obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.67 [0578] round-robin

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: round-robin is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the round-robin obligation named before work proceeds.

Shadow: misusing round-robin at rune 0578 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name round-robin when the prompt needs this obligation made explicit: round-robin is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the round-robin obligation named before work proceeds.
• Ask the assistant to state the round-robin shadow before proposing changes.

Example clause:

Before editing, state the round-robin obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.68 [0579] schedule {Ctrl}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Assign work to time, order, or execution slots.

Shadow: misusing schedule at rune 0579 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name schedule when the prompt needs this obligation made explicit: Assign work to time, order, or execution slots.
• Ask the assistant to state the schedule shadow before proposing changes.

Example clause:

Before editing, state the schedule obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Assign work to time, order, or execution slots.

101.2.69 [0580] select {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: select in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the select obligation named before work proceeds.

Shadow: misusing select at rune 0580 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name select when the prompt needs this obligation made explicit: select in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the select obligation named before work proceeds.
• Ask the assistant to state the select shadow before proposing changes.

Example clause:

Before editing, state the select obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.70 [0581] semaphore

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A counted gate controlling concurrent access to limited capacity.

Shadow: misusing semaphore at rune 0581 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name semaphore when the prompt needs this obligation made explicit: A counted gate controlling concurrent access to limited capacity.
• Ask the assistant to state the semaphore shadow before proposing changes.

Example clause:

Before editing, state the semaphore obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A counted gate controlling concurrent access to limited capacity.

101.2.71 [0582] sequence point

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sequence point is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the sequence point obligation named before work proceeds.

Shadow: misusing sequence point at rune 0582 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name sequence point when the prompt needs this obligation made explicit: sequence point is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the sequence point obligation named before work proceeds.
• Ask the assistant to state the sequence point shadow before proposing changes.

Example clause:

Before editing, state the sequence point obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.72 [0583] serialize access

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: serialize access is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the serialize access obligation named before work proceeds.

Shadow: misusing serialize access at rune 0583 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name serialize access when the prompt needs this obligation made explicit: serialize access is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the serialize access obligation named before work proceeds.
• Ask the assistant to state the serialize access shadow before proposing changes.

Example clause:

Before editing, state the serialize access obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.73 [0584] signal {Ctrl}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Emit a condition change another task may respond to.

Shadow: misusing signal at rune 0584 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name signal when the prompt needs this obligation made explicit: Emit a condition change another task may respond to.
• Ask the assistant to state the signal shadow before proposing changes.

Example clause:

Before editing, state the signal obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Emit a condition change another task may respond to.

101.2.74 [0585] sleep

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sleep is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the sleep obligation named before work proceeds.

Shadow: misusing sleep at rune 0585 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name sleep when the prompt needs this obligation made explicit: sleep is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the sleep obligation named before work proceeds.
• Ask the assistant to state the sleep shadow before proposing changes.

Example clause:

Before editing, state the sleep obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.75 [0586] spawn {Ctrl}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: spawn in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the spawn obligation named before work proceeds.

Shadow: misusing spawn at rune 0586 in the Ctrl lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name spawn when the prompt needs this obligation made explicit: spawn in its Ctrl sense is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the spawn obligation named before work proceeds.
• Ask the assistant to state the spawn shadow before proposing changes.

Example clause:

Before editing, state the spawn obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.76 [0587] step

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: step is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the step obligation named before work proceeds.

Shadow: misusing step at rune 0587 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name step when the prompt needs this obligation made explicit: step is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the step obligation named before work proceeds.
• Ask the assistant to state the step shadow before proposing changes.

Example clause:

Before editing, state the step obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.77 [0588] stop

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stop is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the stop obligation named before work proceeds.

Shadow: misusing stop at rune 0588 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name stop when the prompt needs this obligation made explicit: stop is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the stop obligation named before work proceeds.
• Ask the assistant to state the stop shadow before proposing changes.

Example clause:

Before editing, state the stop obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.78 [0589] suspend

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: suspend is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the suspend obligation named before work proceeds.

Shadow: misusing suspend at rune 0589 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name suspend when the prompt needs this obligation made explicit: suspend is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the suspend obligation named before work proceeds.
• Ask the assistant to state the suspend shadow before proposing changes.

Example clause:

Before editing, state the suspend obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.79 [0590] switch

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: switch is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the switch obligation named before work proceeds.

Shadow: misusing switch at rune 0590 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name switch when the prompt needs this obligation made explicit: switch is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the switch obligation named before work proceeds.
• Ask the assistant to state the switch shadow before proposing changes.

Example clause:

Before editing, state the switch obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.80 [0591] sync

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sync is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the sync obligation named before work proceeds.

Shadow: misusing sync at rune 0591 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name sync when the prompt needs this obligation made explicit: sync is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the sync obligation named before work proceeds.
• Ask the assistant to state the sync shadow before proposing changes.

Example clause:

Before editing, state the sync obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.81 [0592] synchronize

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: synchronize is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the synchronize obligation named before work proceeds.

Shadow: misusing synchronize at rune 0592 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name synchronize when the prompt needs this obligation made explicit: synchronize is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the synchronize obligation named before work proceeds.
• Ask the assistant to state the synchronize shadow before proposing changes.

Example clause:

Before editing, state the synchronize obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.82 [0593] task

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: task is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the task obligation named before work proceeds.

Shadow: misusing task at rune 0593 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name task when the prompt needs this obligation made explicit: task is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the task obligation named before work proceeds.
• Ask the assistant to state the task shadow before proposing changes.

Example clause:

Before editing, state the task obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.83 [0594] terminate

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: terminate is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the terminate obligation named before work proceeds.

Shadow: misusing terminate at rune 0594 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name terminate when the prompt needs this obligation made explicit: terminate is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the terminate obligation named before work proceeds.
• Ask the assistant to state the terminate shadow before proposing changes.

Example clause:

Before editing, state the terminate obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.84 [0595] then

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: then is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the then obligation named before work proceeds.

Shadow: misusing then at rune 0595 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name then when the prompt needs this obligation made explicit: then is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the then obligation named before work proceeds.
• Ask the assistant to state the then shadow before proposing changes.

Example clause:

Before editing, state the then obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.85 [0596] throttle

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: throttle is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the throttle obligation named before work proceeds.

Shadow: misusing throttle at rune 0596 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name throttle when the prompt needs this obligation made explicit: throttle is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the throttle obligation named before work proceeds.
• Ask the assistant to state the throttle shadow before proposing changes.

Example clause:

Before editing, state the throttle obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.86 [0597] tick

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: tick is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the tick obligation named before work proceeds.

Shadow: misusing tick at rune 0597 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name tick when the prompt needs this obligation made explicit: tick is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the tick obligation named before work proceeds.
• Ask the assistant to state the tick shadow before proposing changes.

Example clause:

Before editing, state the tick obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.87 [0598] timeout {Ctrl}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Waiting is not free and patience must have a boundary. A timeout is a contract with reality about how long uncertainty is allowed to persist.

Shadow: when a timeout hides whether the operation failed, succeeded late, or is still running.

Prompt uses:

• Name timeout when the prompt needs this obligation made explicit: Waiting is not free and patience must have a boundary. A timeout is a contract with reality about how long uncertainty is allowed to persist.
• Ask the assistant to state the timeout shadow before proposing changes.

Example clause:

Before editing, state the timeout obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A declared limit on how long uncertainty may persist.

101.2.88 [0599] timeslice

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: timeslice is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the timeslice obligation named before work proceeds.

Shadow: misusing timeslice at rune 0599 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name timeslice when the prompt needs this obligation made explicit: timeslice is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the timeslice obligation named before work proceeds.
• Ask the assistant to state the timeslice shadow before proposing changes.

Example clause:

Before editing, state the timeslice obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.89 [0600] trigger

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: trigger is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the trigger obligation named before work proceeds.

Shadow: misusing trigger at rune 0600 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name trigger when the prompt needs this obligation made explicit: trigger is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the trigger obligation named before work proceeds.
• Ask the assistant to state the trigger shadow before proposing changes.

Example clause:

Before editing, state the trigger obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.90 [0601] try

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: try is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the try obligation named before work proceeds.

Shadow: misusing try at rune 0601 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name try when the prompt needs this obligation made explicit: try is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the try obligation named before work proceeds.
• Ask the assistant to state the try shadow before proposing changes.

Example clause:

Before editing, state the try obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.91 [0602] unblock

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: unblock is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the unblock obligation named before work proceeds.

Shadow: misusing unblock at rune 0602 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name unblock when the prompt needs this obligation made explicit: unblock is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the unblock obligation named before work proceeds.
• Ask the assistant to state the unblock shadow before proposing changes.

Example clause:

Before editing, state the unblock obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.92 [0603] until

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: until is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the until obligation named before work proceeds.

Shadow: misusing until at rune 0603 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name until when the prompt needs this obligation made explicit: until is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the until obligation named before work proceeds.
• Ask the assistant to state the until shadow before proposing changes.

Example clause:

Before editing, state the until obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.93 [0604] wait

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: wait is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the wait obligation named before work proceeds.

Shadow: misusing wait at rune 0604 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name wait when the prompt needs this obligation made explicit: wait is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the wait obligation named before work proceeds.
• Ask the assistant to state the wait shadow before proposing changes.

Example clause:

Before editing, state the wait obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.94 [0605] wake

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: wake is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the wake obligation named before work proceeds.

Shadow: misusing wake at rune 0605 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name wake when the prompt needs this obligation made explicit: wake is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the wake obligation named before work proceeds.
• Ask the assistant to state the wake shadow before proposing changes.

Example clause:

Before editing, state the wake obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.95 [0606] when

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: when is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the when obligation named before work proceeds.

Shadow: misusing when at rune 0606 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name when when the prompt needs this obligation made explicit: when is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the when obligation named before work proceeds.
• Ask the assistant to state the when shadow before proposing changes.

Example clause:

Before editing, state the when obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.96 [0607] while

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: while is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the while obligation named before work proceeds.

Shadow: misusing while at rune 0607 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name while when the prompt needs this obligation made explicit: while is a control flow and coordination rune for make ordering, waiting, retry, and termination rules explicit; use it when the artifact needs the while obligation named before work proceeds.
• Ask the assistant to state the while shadow before proposing changes.

Example clause:

Before editing, state the while obligation, the evidence that satisfies it, and the failure mode if it is missing.

101.2.97 [0608] yield

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Give up control now so another act may proceed.

Shadow: misusing yield at rune 0608 in the control lane can let timing assumptions can turn coordination into stalls or races; verify by requiring the caster to state progress, timeout, retry, and cancellation rules.

Prompt uses:

• Name yield when the prompt needs this obligation made explicit: Give up control now so another act may proceed.
• Ask the assistant to state the yield shadow before proposing changes.

Example clause:

Before editing, state the yield obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Give up control now so another act may proceed.