101  Runtime, Memory, and Execution

102 Runtime, Memory, and Execution

Range: 0609-0684.

102.1 Completion

Status	Count
authored	76

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

Sigil	Term	Completion	Semantic	Summary
0609	address space	authored	generated_draft	address space is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the address space obligation named before work proceeds.
0610	aliasing	authored	generated_draft	aliasing is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the aliasing obligation named before work proceeds.
0611	allocation	authored	reviewed	Reserve memory for something that is about to live.
0612	allocator	authored	generated_draft	allocator is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the allocator obligation named before work proceeds.
0613	arena	authored	generated_draft	arena is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the arena obligation named before work proceeds.
0614	borrow {Run}	authored	generated_draft	borrow in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the borrow obligation named before work proceeds.
0615	cache {Run}	authored	reviewed	Keep likely things close so future cost falls. Shadow: stale truth delivered at machine speed.
0616	cache line {Run}	authored	generated_draft	cache line in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the cache line obligation named before work proceeds.
0617	call frame	authored	generated_draft	call frame is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the call frame obligation named before work proceeds.
0618	call stack	authored	generated_draft	call stack is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the call stack obligation named before work proceeds.
0619	closure environment	authored	generated_draft	closure environment is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the closure environment obligation named before work proceeds.
0620	compaction {Run}	authored	generated_draft	compaction in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the compaction obligation named before work proceeds.
0621	copy-on-write {Run}	authored	reviewed	Share until mutation forces a real duplicate.
0622	core dump {Run}	authored	generated_draft	core dump in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the core dump obligation named before work proceeds.
0623	deallocation	authored	generated_draft	deallocation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the deallocation obligation named before work proceeds.
0624	destructor {Run}	authored	generated_draft	destructor in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the destructor obligation named before work proceeds.
0625	dynamic allocation	authored	generated_draft	dynamic allocation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the dynamic allocation obligation named before work proceeds.
0626	eager evaluation	authored	generated_draft	eager evaluation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the eager evaluation obligation named before work proceeds.
0627	escape analysis	authored	generated_draft	escape analysis is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the escape analysis obligation named before work proceeds.
0628	execution context	authored	generated_draft	execution context is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the execution context obligation named before work proceeds.
0629	finalizer	authored	generated_draft	finalizer is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the finalizer obligation named before work proceeds.
0630	frame pointer	authored	generated_draft	frame pointer is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the frame pointer obligation named before work proceeds.
0631	garbage collection	authored	reviewed	Automatic reclamation of memory no longer reachable.
0632	generation	authored	generated_draft	generation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the generation obligation named before work proceeds.
0633	handle {Run}	authored	generated_draft	handle in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the handle obligation named before work proceeds.
0634	heap	authored	reviewed	Region for dynamically allocated objects.
0635	heap object	authored	generated_draft	heap object is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the heap object obligation named before work proceeds.
0636	hot path {Run}	authored	reviewed	The path where small inefficiencies burn real time.
0637	inline cache	authored	generated_draft	inline cache is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the inline cache obligation named before work proceeds.
0638	interpreter loop	authored	generated_draft	interpreter loop is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the interpreter loop obligation named before work proceeds.
0639	JIT	authored	generated_draft	JIT is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the JIT obligation named before work proceeds.
0640	layout {Run}	authored	generated_draft	layout in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the layout obligation named before work proceeds.
0641	lazy evaluation	authored	generated_draft	lazy evaluation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the lazy evaluation obligation named before work proceeds.
0642	leak {Run}	authored	generated_draft	leak in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the leak obligation named before work proceeds.
0643	lifetime {Run}	authored	reviewed	How long a value may legally remain alive.
0644	live set	authored	generated_draft	live set is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the live set obligation named before work proceeds.
0645	locality	authored	reviewed	The performance dividend from keeping related data physically close.
0646	lock-free {Run}	authored	generated_draft	lock-free in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the lock-free obligation named before work proceeds.
0647	mark phase	authored	generated_draft	mark phase is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the mark phase obligation named before work proceeds.
0648	memory {Run}	authored	generated_draft	memory in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the memory obligation named before work proceeds.
0649	memory barrier	authored	reviewed	An ordering fence for memory effects across threads or cores.
0650	memory map	authored	generated_draft	memory map is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the memory map obligation named before work proceeds.
0651	memory pool	authored	generated_draft	memory pool is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the memory pool obligation named before work proceeds.
0652	memory safety	authored	reviewed	Protection against illegal memory access and corruption.
0653	move semantics	authored	generated_draft	move semantics is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the move semantics obligation named before work proceeds.
0654	object header	authored	generated_draft	object header is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the object header obligation named before work proceeds.
0655	page {Run}	authored	generated_draft	page in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the page obligation named before work proceeds.
0656	page fault	authored	generated_draft	page fault is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the page fault obligation named before work proceeds.
0657	pinning	authored	reviewed	Keep an object fixed in place so other machinery can safely refer to it.
0658	pointer {Run}	authored	generated_draft	pointer in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the pointer obligation named before work proceeds.
0659	pool allocator	authored	generated_draft	pool allocator is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the pool allocator obligation named before work proceeds.
0660	prefetch	authored	generated_draft	prefetch is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the prefetch obligation named before work proceeds.
0661	quiescence	authored	generated_draft	quiescence is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the quiescence obligation named before work proceeds.
0662	reclaim	authored	generated_draft	reclaim is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the reclaim obligation named before work proceeds.
0663	reference count	authored	reviewed	Ownership tracked by counting how many references remain.
0664	register allocation	authored	generated_draft	register allocation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the register allocation obligation named before work proceeds.
0665	root set	authored	generated_draft	root set is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the root set obligation named before work proceeds.
0666	runtime	authored	generated_draft	runtime is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the runtime obligation named before work proceeds.
0667	sandbox {Run}	authored	generated_draft	sandbox in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the sandbox obligation named before work proceeds.
0668	shadow stack	authored	generated_draft	shadow stack is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the shadow stack obligation named before work proceeds.
0669	slab allocator	authored	generated_draft	slab allocator is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the slab allocator obligation named before work proceeds.
0670	stack {Run}	authored	reviewed	Region for call frames and short-lived local state.
0671	stack frame	authored	generated_draft	stack frame is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the stack frame obligation named before work proceeds.
0672	stop-the-world	authored	generated_draft	stop-the-world is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the stop-the-world obligation named before work proceeds.
0673	sweep phase	authored	generated_draft	sweep phase is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the sweep phase obligation named before work proceeds.
0674	tail call	authored	generated_draft	tail call is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the tail call obligation named before work proceeds.
0675	thread-local storage	authored	generated_draft	thread-local storage is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the thread-local storage obligation named before work proceeds.
0676	TLB	authored	generated_draft	TLB is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the TLB obligation named before work proceeds.
0677	tracing collector	authored	generated_draft	tracing collector is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the tracing collector obligation named before work proceeds.
0678	unbox	authored	generated_draft	unbox is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the unbox obligation named before work proceeds.
0679	user heap	authored	generated_draft	user heap is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the user heap obligation named before work proceeds.
0680	virtual memory	authored	generated_draft	virtual memory is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the virtual memory obligation named before work proceeds.
0681	VM	authored	generated_draft	VM is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the VM obligation named before work proceeds.
0682	wait-free {Run}	authored	generated_draft	wait-free in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the wait-free obligation named before work proceeds.
0683	write barrier	authored	generated_draft	write barrier is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the write barrier obligation named before work proceeds.
0684	zero-copy {Run}	authored	reviewed	Data movement stripped down to the minimum number of duplications. Use it when the bottleneck is physical movement rather than arithmetic.

102.2 Entries

102.2.1 [0609] address space

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: address space is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the address space obligation named before work proceeds.

Shadow: misusing address space at rune 0609 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name address space when the prompt needs this obligation made explicit: address space is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the address space obligation named before work proceeds.
• Ask the assistant to state the address space shadow before proposing changes.

Example clause:

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

102.2.2 [0610] aliasing

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: aliasing is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the aliasing obligation named before work proceeds.

Shadow: misusing aliasing at rune 0610 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name aliasing when the prompt needs this obligation made explicit: aliasing is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the aliasing obligation named before work proceeds.
• Ask the assistant to state the aliasing shadow before proposing changes.

Example clause:

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

102.2.3 [0611] allocation

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Reserve memory for something that is about to live.

Shadow: misusing allocation at rune 0611 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name allocation when the prompt needs this obligation made explicit: Reserve memory for something that is about to live.
• Ask the assistant to state the allocation shadow before proposing changes.

Example clause:

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

Pocket gloss: Reserve memory for something that is about to live.

102.2.4 [0612] allocator

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: allocator is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the allocator obligation named before work proceeds.

Shadow: misusing allocator at rune 0612 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name allocator when the prompt needs this obligation made explicit: allocator is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the allocator obligation named before work proceeds.
• Ask the assistant to state the allocator shadow before proposing changes.

Example clause:

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

102.2.5 [0613] arena

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: arena is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the arena obligation named before work proceeds.

Shadow: misusing arena at rune 0613 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name arena when the prompt needs this obligation made explicit: arena is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the arena obligation named before work proceeds.
• Ask the assistant to state the arena shadow before proposing changes.

Example clause:

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

102.2.6 [0614] borrow {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: borrow in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the borrow obligation named before work proceeds.

Shadow: misusing borrow at rune 0614 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name borrow when the prompt needs this obligation made explicit: borrow in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the borrow obligation named before work proceeds.
• Ask the assistant to state the borrow shadow before proposing changes.

Example clause:

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

102.2.7 [0615] cache {Run}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Keep likely things close so future cost falls.

Shadow: stale truth delivered at machine speed.

Prompt uses:

• Name cache when the prompt needs this obligation made explicit: Keep likely things close so future cost falls.
• Ask the assistant to state the cache shadow before proposing changes.

Example clause:

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

Pocket gloss: Keep likely things close so repeated access costs less.

102.2.8 [0616] cache line {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cache line in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the cache line obligation named before work proceeds.

Shadow: misusing cache line at rune 0616 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name cache line when the prompt needs this obligation made explicit: cache line in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the cache line obligation named before work proceeds.
• Ask the assistant to state the cache line shadow before proposing changes.

Example clause:

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

102.2.9 [0617] call frame

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: call frame is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the call frame obligation named before work proceeds.

Shadow: misusing call frame at rune 0617 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name call frame when the prompt needs this obligation made explicit: call frame is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the call frame obligation named before work proceeds.
• Ask the assistant to state the call frame shadow before proposing changes.

Example clause:

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

102.2.10 [0618] call stack

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: call stack is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the call stack obligation named before work proceeds.

Shadow: misusing call stack at rune 0618 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name call stack when the prompt needs this obligation made explicit: call stack is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the call stack obligation named before work proceeds.
• Ask the assistant to state the call stack shadow before proposing changes.

Example clause:

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

102.2.11 [0619] closure environment

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: closure environment is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the closure environment obligation named before work proceeds.

Shadow: misusing closure environment at rune 0619 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name closure environment when the prompt needs this obligation made explicit: closure environment is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the closure environment obligation named before work proceeds.
• Ask the assistant to state the closure environment shadow before proposing changes.

Example clause:

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

102.2.12 [0620] compaction {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: compaction in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the compaction obligation named before work proceeds.

Shadow: misusing compaction at rune 0620 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name compaction when the prompt needs this obligation made explicit: compaction in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the compaction obligation named before work proceeds.
• Ask the assistant to state the compaction shadow before proposing changes.

Example clause:

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

102.2.13 [0621] copy-on-write {Run}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Share until mutation forces a real duplicate.

Shadow: misusing copy-on-write at rune 0621 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name copy-on-write when the prompt needs this obligation made explicit: Share until mutation forces a real duplicate.
• Ask the assistant to state the copy-on-write shadow before proposing changes.

Example clause:

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

Pocket gloss: Share until mutation forces a real duplicate.

102.2.14 [0622] core dump {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: core dump in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the core dump obligation named before work proceeds.

Shadow: misusing core dump at rune 0622 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name core dump when the prompt needs this obligation made explicit: core dump in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the core dump obligation named before work proceeds.
• Ask the assistant to state the core dump shadow before proposing changes.

Example clause:

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

102.2.15 [0623] deallocation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: deallocation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the deallocation obligation named before work proceeds.

Shadow: misusing deallocation at rune 0623 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name deallocation when the prompt needs this obligation made explicit: deallocation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the deallocation obligation named before work proceeds.
• Ask the assistant to state the deallocation shadow before proposing changes.

Example clause:

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

102.2.16 [0624] destructor {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: destructor in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the destructor obligation named before work proceeds.

Shadow: misusing destructor at rune 0624 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name destructor when the prompt needs this obligation made explicit: destructor in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the destructor obligation named before work proceeds.
• Ask the assistant to state the destructor shadow before proposing changes.

Example clause:

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

102.2.17 [0625] dynamic allocation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: dynamic allocation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the dynamic allocation obligation named before work proceeds.

Shadow: misusing dynamic allocation at rune 0625 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name dynamic allocation when the prompt needs this obligation made explicit: dynamic allocation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the dynamic allocation obligation named before work proceeds.
• Ask the assistant to state the dynamic allocation shadow before proposing changes.

Example clause:

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

102.2.18 [0626] eager evaluation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: eager evaluation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the eager evaluation obligation named before work proceeds.

Shadow: misusing eager evaluation at rune 0626 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name eager evaluation when the prompt needs this obligation made explicit: eager evaluation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the eager evaluation obligation named before work proceeds.
• Ask the assistant to state the eager evaluation shadow before proposing changes.

Example clause:

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

102.2.19 [0627] escape analysis

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: escape analysis is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the escape analysis obligation named before work proceeds.

Shadow: misusing escape analysis at rune 0627 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name escape analysis when the prompt needs this obligation made explicit: escape analysis is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the escape analysis obligation named before work proceeds.
• Ask the assistant to state the escape analysis shadow before proposing changes.

Example clause:

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

102.2.20 [0628] execution context

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: execution context is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the execution context obligation named before work proceeds.

Shadow: misusing execution context at rune 0628 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name execution context when the prompt needs this obligation made explicit: execution context is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the execution context obligation named before work proceeds.
• Ask the assistant to state the execution context shadow before proposing changes.

Example clause:

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

102.2.21 [0629] finalizer

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: finalizer is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the finalizer obligation named before work proceeds.

Shadow: misusing finalizer at rune 0629 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name finalizer when the prompt needs this obligation made explicit: finalizer is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the finalizer obligation named before work proceeds.
• Ask the assistant to state the finalizer shadow before proposing changes.

Example clause:

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

102.2.22 [0630] frame pointer

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: frame pointer is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the frame pointer obligation named before work proceeds.

Shadow: misusing frame pointer at rune 0630 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name frame pointer when the prompt needs this obligation made explicit: frame pointer is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the frame pointer obligation named before work proceeds.
• Ask the assistant to state the frame pointer shadow before proposing changes.

Example clause:

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

102.2.23 [0631] garbage collection

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Automatic reclamation of memory no longer reachable.

Shadow: misusing garbage collection at rune 0631 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name garbage collection when the prompt needs this obligation made explicit: Automatic reclamation of memory no longer reachable.
• Ask the assistant to state the garbage collection shadow before proposing changes.

Example clause:

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

Pocket gloss: Automatic reclamation of memory no longer reachable.

102.2.24 [0632] generation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: generation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the generation obligation named before work proceeds.

Shadow: misusing generation at rune 0632 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name generation when the prompt needs this obligation made explicit: generation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the generation obligation named before work proceeds.
• Ask the assistant to state the generation shadow before proposing changes.

Example clause:

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

102.2.25 [0633] handle {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: handle in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the handle obligation named before work proceeds.

Shadow: misusing handle at rune 0633 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name handle when the prompt needs this obligation made explicit: handle in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the handle obligation named before work proceeds.
• Ask the assistant to state the handle shadow before proposing changes.

Example clause:

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

102.2.26 [0634] heap

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Region for dynamically allocated objects.

Shadow: misusing heap at rune 0634 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name heap when the prompt needs this obligation made explicit: Region for dynamically allocated objects.
• Ask the assistant to state the heap shadow before proposing changes.

Example clause:

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

Pocket gloss: Region for dynamically allocated objects.

102.2.27 [0635] heap object

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: heap object is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the heap object obligation named before work proceeds.

Shadow: misusing heap object at rune 0635 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name heap object when the prompt needs this obligation made explicit: heap object is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the heap object obligation named before work proceeds.
• Ask the assistant to state the heap object shadow before proposing changes.

Example clause:

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

102.2.28 [0636] hot path {Run}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The path where small inefficiencies burn real time.

Shadow: misusing hot path at rune 0636 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name hot path when the prompt needs this obligation made explicit: The path where small inefficiencies burn real time.
• Ask the assistant to state the hot path shadow before proposing changes.

Example clause:

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

Pocket gloss: The path where small inefficiencies burn real time.

102.2.29 [0637] inline cache

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: inline cache is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the inline cache obligation named before work proceeds.

Shadow: misusing inline cache at rune 0637 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name inline cache when the prompt needs this obligation made explicit: inline cache is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the inline cache obligation named before work proceeds.
• Ask the assistant to state the inline cache shadow before proposing changes.

Example clause:

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

102.2.30 [0638] interpreter loop

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: interpreter loop is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the interpreter loop obligation named before work proceeds.

Shadow: misusing interpreter loop at rune 0638 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name interpreter loop when the prompt needs this obligation made explicit: interpreter loop is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the interpreter loop obligation named before work proceeds.
• Ask the assistant to state the interpreter loop shadow before proposing changes.

Example clause:

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

102.2.31 [0639] JIT

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: JIT is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the JIT obligation named before work proceeds.

Shadow: misusing JIT at rune 0639 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name JIT when the prompt needs this obligation made explicit: JIT is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the JIT obligation named before work proceeds.
• Ask the assistant to state the JIT shadow before proposing changes.

Example clause:

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

102.2.32 [0640] layout {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: layout in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the layout obligation named before work proceeds.

Shadow: misusing layout at rune 0640 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name layout when the prompt needs this obligation made explicit: layout in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the layout obligation named before work proceeds.
• Ask the assistant to state the layout shadow before proposing changes.

Example clause:

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

102.2.33 [0641] lazy evaluation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: lazy evaluation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the lazy evaluation obligation named before work proceeds.

Shadow: misusing lazy evaluation at rune 0641 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name lazy evaluation when the prompt needs this obligation made explicit: lazy evaluation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the lazy evaluation obligation named before work proceeds.
• Ask the assistant to state the lazy evaluation shadow before proposing changes.

Example clause:

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

102.2.34 [0642] leak {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: leak in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the leak obligation named before work proceeds.

Shadow: misusing leak at rune 0642 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name leak when the prompt needs this obligation made explicit: leak in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the leak obligation named before work proceeds.
• Ask the assistant to state the leak shadow before proposing changes.

Example clause:

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

102.2.35 [0643] lifetime {Run}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: How long a value may legally remain alive.

Shadow: misusing lifetime at rune 0643 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name lifetime when the prompt needs this obligation made explicit: How long a value may legally remain alive.
• Ask the assistant to state the lifetime shadow before proposing changes.

Example clause:

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

Pocket gloss: How long a value may legally remain alive.

102.2.36 [0644] live set

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: live set is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the live set obligation named before work proceeds.

Shadow: misusing live set at rune 0644 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name live set when the prompt needs this obligation made explicit: live set is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the live set obligation named before work proceeds.
• Ask the assistant to state the live set shadow before proposing changes.

Example clause:

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

102.2.37 [0645] locality

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The performance dividend from keeping related data physically close.

Shadow: misusing locality at rune 0645 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name locality when the prompt needs this obligation made explicit: The performance dividend from keeping related data physically close.
• Ask the assistant to state the locality shadow before proposing changes.

Example clause:

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

Pocket gloss: The performance dividend from keeping related data physically close.

102.2.38 [0646] lock-free {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: lock-free in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the lock-free obligation named before work proceeds.

Shadow: misusing lock-free at rune 0646 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name lock-free when the prompt needs this obligation made explicit: lock-free in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the lock-free obligation named before work proceeds.
• Ask the assistant to state the lock-free shadow before proposing changes.

Example clause:

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

102.2.39 [0647] mark phase

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: mark phase is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the mark phase obligation named before work proceeds.

Shadow: misusing mark phase at rune 0647 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name mark phase when the prompt needs this obligation made explicit: mark phase is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the mark phase obligation named before work proceeds.
• Ask the assistant to state the mark phase shadow before proposing changes.

Example clause:

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

102.2.40 [0648] memory {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: memory in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the memory obligation named before work proceeds.

Shadow: misusing memory at rune 0648 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name memory when the prompt needs this obligation made explicit: memory in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the memory obligation named before work proceeds.
• Ask the assistant to state the memory shadow before proposing changes.

Example clause:

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

102.2.41 [0649] memory barrier

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: An ordering fence for memory effects across threads or cores.

Shadow: misusing memory barrier at rune 0649 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name memory barrier when the prompt needs this obligation made explicit: An ordering fence for memory effects across threads or cores.
• Ask the assistant to state the memory barrier shadow before proposing changes.

Example clause:

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

Pocket gloss: An ordering fence for memory effects across threads or cores.

102.2.42 [0650] memory map

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: memory map is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the memory map obligation named before work proceeds.

Shadow: misusing memory map at rune 0650 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name memory map when the prompt needs this obligation made explicit: memory map is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the memory map obligation named before work proceeds.
• Ask the assistant to state the memory map shadow before proposing changes.

Example clause:

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

102.2.43 [0651] memory pool

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: memory pool is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the memory pool obligation named before work proceeds.

Shadow: misusing memory pool at rune 0651 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name memory pool when the prompt needs this obligation made explicit: memory pool is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the memory pool obligation named before work proceeds.
• Ask the assistant to state the memory pool shadow before proposing changes.

Example clause:

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

102.2.44 [0652] memory safety

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Protection against illegal memory access and corruption.

Shadow: misusing memory safety at rune 0652 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name memory safety when the prompt needs this obligation made explicit: Protection against illegal memory access and corruption.
• Ask the assistant to state the memory safety shadow before proposing changes.

Example clause:

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

Pocket gloss: Protection against illegal memory access and corruption.

102.2.45 [0653] move semantics

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: move semantics is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the move semantics obligation named before work proceeds.

Shadow: misusing move semantics at rune 0653 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name move semantics when the prompt needs this obligation made explicit: move semantics is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the move semantics obligation named before work proceeds.
• Ask the assistant to state the move semantics shadow before proposing changes.

Example clause:

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

102.2.46 [0654] object header

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: object header is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the object header obligation named before work proceeds.

Shadow: misusing object header at rune 0654 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name object header when the prompt needs this obligation made explicit: object header is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the object header obligation named before work proceeds.
• Ask the assistant to state the object header shadow before proposing changes.

Example clause:

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

102.2.47 [0655] page {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: page in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the page obligation named before work proceeds.

Shadow: misusing page at rune 0655 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name page when the prompt needs this obligation made explicit: page in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the page obligation named before work proceeds.
• Ask the assistant to state the page shadow before proposing changes.

Example clause:

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

102.2.48 [0656] page fault

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: page fault is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the page fault obligation named before work proceeds.

Shadow: misusing page fault at rune 0656 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name page fault when the prompt needs this obligation made explicit: page fault is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the page fault obligation named before work proceeds.
• Ask the assistant to state the page fault shadow before proposing changes.

Example clause:

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

102.2.49 [0657] pinning

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Keep an object fixed in place so other machinery can safely refer to it.

Shadow: misusing pinning at rune 0657 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name pinning when the prompt needs this obligation made explicit: Keep an object fixed in place so other machinery can safely refer to it.
• Ask the assistant to state the pinning shadow before proposing changes.

Example clause:

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

Pocket gloss: Keep an object fixed in place so other machinery can safely refer to it.

102.2.50 [0658] pointer {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: pointer in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the pointer obligation named before work proceeds.

Shadow: misusing pointer at rune 0658 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name pointer when the prompt needs this obligation made explicit: pointer in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the pointer obligation named before work proceeds.
• Ask the assistant to state the pointer shadow before proposing changes.

Example clause:

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

102.2.51 [0659] pool allocator

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: pool allocator is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the pool allocator obligation named before work proceeds.

Shadow: misusing pool allocator at rune 0659 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name pool allocator when the prompt needs this obligation made explicit: pool allocator is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the pool allocator obligation named before work proceeds.
• Ask the assistant to state the pool allocator shadow before proposing changes.

Example clause:

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

102.2.52 [0660] prefetch

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: prefetch is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the prefetch obligation named before work proceeds.

Shadow: misusing prefetch at rune 0660 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name prefetch when the prompt needs this obligation made explicit: prefetch is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the prefetch obligation named before work proceeds.
• Ask the assistant to state the prefetch shadow before proposing changes.

Example clause:

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

102.2.53 [0661] quiescence

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: quiescence is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the quiescence obligation named before work proceeds.

Shadow: misusing quiescence at rune 0661 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name quiescence when the prompt needs this obligation made explicit: quiescence is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the quiescence obligation named before work proceeds.
• Ask the assistant to state the quiescence shadow before proposing changes.

Example clause:

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

102.2.54 [0662] reclaim

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: reclaim is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the reclaim obligation named before work proceeds.

Shadow: misusing reclaim at rune 0662 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name reclaim when the prompt needs this obligation made explicit: reclaim is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the reclaim obligation named before work proceeds.
• Ask the assistant to state the reclaim shadow before proposing changes.

Example clause:

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

102.2.55 [0663] reference count

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Ownership tracked by counting how many references remain.

Shadow: misusing reference count at rune 0663 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name reference count when the prompt needs this obligation made explicit: Ownership tracked by counting how many references remain.
• Ask the assistant to state the reference count shadow before proposing changes.

Example clause:

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

Pocket gloss: Ownership tracked by counting how many references remain.

102.2.56 [0664] register allocation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: register allocation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the register allocation obligation named before work proceeds.

Shadow: misusing register allocation at rune 0664 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name register allocation when the prompt needs this obligation made explicit: register allocation is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the register allocation obligation named before work proceeds.
• Ask the assistant to state the register allocation shadow before proposing changes.

Example clause:

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

102.2.57 [0665] root set

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: root set is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the root set obligation named before work proceeds.

Shadow: misusing root set at rune 0665 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name root set when the prompt needs this obligation made explicit: root set is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the root set obligation named before work proceeds.
• Ask the assistant to state the root set shadow before proposing changes.

Example clause:

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

102.2.58 [0666] runtime

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: runtime is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the runtime obligation named before work proceeds.

Shadow: misusing runtime at rune 0666 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name runtime when the prompt needs this obligation made explicit: runtime is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the runtime obligation named before work proceeds.
• Ask the assistant to state the runtime shadow before proposing changes.

Example clause:

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

102.2.59 [0667] sandbox {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sandbox in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the sandbox obligation named before work proceeds.

Shadow: misusing sandbox at rune 0667 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name sandbox when the prompt needs this obligation made explicit: sandbox in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the sandbox obligation named before work proceeds.
• Ask the assistant to state the sandbox shadow before proposing changes.

Example clause:

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

102.2.60 [0668] shadow stack

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: shadow stack is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the shadow stack obligation named before work proceeds.

Shadow: misusing shadow stack at rune 0668 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name shadow stack when the prompt needs this obligation made explicit: shadow stack is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the shadow stack obligation named before work proceeds.
• Ask the assistant to state the shadow stack shadow before proposing changes.

Example clause:

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

102.2.61 [0669] slab allocator

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: slab allocator is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the slab allocator obligation named before work proceeds.

Shadow: misusing slab allocator at rune 0669 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name slab allocator when the prompt needs this obligation made explicit: slab allocator is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the slab allocator obligation named before work proceeds.
• Ask the assistant to state the slab allocator shadow before proposing changes.

Example clause:

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

102.2.62 [0670] stack {Run}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Region for call frames and short-lived local state.

Shadow: misusing stack at rune 0670 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name stack when the prompt needs this obligation made explicit: Region for call frames and short-lived local state.
• Ask the assistant to state the stack shadow before proposing changes.

Example clause:

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

Pocket gloss: Region for call frames and short-lived local state.

102.2.63 [0671] stack frame

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stack frame is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the stack frame obligation named before work proceeds.

Shadow: misusing stack frame at rune 0671 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name stack frame when the prompt needs this obligation made explicit: stack frame is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the stack frame obligation named before work proceeds.
• Ask the assistant to state the stack frame shadow before proposing changes.

Example clause:

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

102.2.64 [0672] stop-the-world

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stop-the-world is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the stop-the-world obligation named before work proceeds.

Shadow: misusing stop-the-world at rune 0672 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name stop-the-world when the prompt needs this obligation made explicit: stop-the-world is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the stop-the-world obligation named before work proceeds.
• Ask the assistant to state the stop-the-world shadow before proposing changes.

Example clause:

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

102.2.65 [0673] sweep phase

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sweep phase is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the sweep phase obligation named before work proceeds.

Shadow: misusing sweep phase at rune 0673 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name sweep phase when the prompt needs this obligation made explicit: sweep phase is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the sweep phase obligation named before work proceeds.
• Ask the assistant to state the sweep phase shadow before proposing changes.

Example clause:

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

102.2.66 [0674] tail call

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: tail call is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the tail call obligation named before work proceeds.

Shadow: misusing tail call at rune 0674 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name tail call when the prompt needs this obligation made explicit: tail call is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the tail call obligation named before work proceeds.
• Ask the assistant to state the tail call shadow before proposing changes.

Example clause:

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

102.2.67 [0675] thread-local storage

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: thread-local storage is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the thread-local storage obligation named before work proceeds.

Shadow: misusing thread-local storage at rune 0675 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name thread-local storage when the prompt needs this obligation made explicit: thread-local storage is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the thread-local storage obligation named before work proceeds.
• Ask the assistant to state the thread-local storage shadow before proposing changes.

Example clause:

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

102.2.68 [0676] TLB

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: TLB is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the TLB obligation named before work proceeds.

Shadow: misusing TLB at rune 0676 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name TLB when the prompt needs this obligation made explicit: TLB is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the TLB obligation named before work proceeds.
• Ask the assistant to state the TLB shadow before proposing changes.

Example clause:

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

102.2.69 [0677] tracing collector

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: tracing collector is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the tracing collector obligation named before work proceeds.

Shadow: misusing tracing collector at rune 0677 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name tracing collector when the prompt needs this obligation made explicit: tracing collector is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the tracing collector obligation named before work proceeds.
• Ask the assistant to state the tracing collector shadow before proposing changes.

Example clause:

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

102.2.70 [0678] unbox

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: unbox is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the unbox obligation named before work proceeds.

Shadow: misusing unbox at rune 0678 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name unbox when the prompt needs this obligation made explicit: unbox is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the unbox obligation named before work proceeds.
• Ask the assistant to state the unbox shadow before proposing changes.

Example clause:

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

102.2.71 [0679] user heap

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: user heap is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the user heap obligation named before work proceeds.

Shadow: misusing user heap at rune 0679 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name user heap when the prompt needs this obligation made explicit: user heap is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the user heap obligation named before work proceeds.
• Ask the assistant to state the user heap shadow before proposing changes.

Example clause:

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

102.2.72 [0680] virtual memory

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: virtual memory is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the virtual memory obligation named before work proceeds.

Shadow: misusing virtual memory at rune 0680 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name virtual memory when the prompt needs this obligation made explicit: virtual memory is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the virtual memory obligation named before work proceeds.
• Ask the assistant to state the virtual memory shadow before proposing changes.

Example clause:

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

102.2.73 [0681] VM

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: VM is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the VM obligation named before work proceeds.

Shadow: misusing VM at rune 0681 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name VM when the prompt needs this obligation made explicit: VM is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the VM obligation named before work proceeds.
• Ask the assistant to state the VM shadow before proposing changes.

Example clause:

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

102.2.74 [0682] wait-free {Run}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: wait-free in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the wait-free obligation named before work proceeds.

Shadow: misusing wait-free at rune 0682 in the Run lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name wait-free when the prompt needs this obligation made explicit: wait-free in its Run sense is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the wait-free obligation named before work proceeds.
• Ask the assistant to state the wait-free shadow before proposing changes.

Example clause:

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

102.2.75 [0683] write barrier

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: write barrier is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the write barrier obligation named before work proceeds.

Shadow: misusing write barrier at rune 0683 in the runtime lane can let runtime convenience can hide contention, stale state, or leaks; verify by requiring the caster to state lifetime, ownership, concurrency, and resource boundaries.

Prompt uses:

• Name write barrier when the prompt needs this obligation made explicit: write barrier is a runtime and memory rune for expose allocation, lifetime, scheduling, and execution costs; use it when the artifact needs the write barrier obligation named before work proceeds.
• Ask the assistant to state the write barrier shadow before proposing changes.

Example clause:

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

102.2.76 [0684] zero-copy {Run}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Data movement stripped down to the minimum number of duplications. Use it when the bottleneck is physical movement rather than arithmetic.

Shadow: when avoiding copies transfers lifetime and mutation hazards to the caller.

Prompt uses:

• Name zero-copy when the prompt needs this obligation made explicit: Data movement stripped down to the minimum number of duplications. Use it when the bottleneck is physical movement rather than arithmetic.
• Ask the assistant to state the zero-copy shadow before proposing changes.

Example clause:

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

Pocket gloss: Move data without making redundant copies.