108  Hardware, Embedded, and Performance-Near Words

109 Hardware, Embedded, and Performance-Near Words

Range: 1211-1290.

109.1 Completion

Status	Count
authored	80

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

Sigil	Term	Completion	Semantic	Summary
1211	accelerator	authored	generated_draft	accelerator is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the accelerator obligation named before work proceeds.
1212	alignment {HW}	authored	generated_draft	alignment in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the alignment obligation named before work proceeds.
1213	ASIC	authored	generated_draft	ASIC is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the ASIC obligation named before work proceeds.
1214	assembly instruction	authored	generated_draft	assembly instruction is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the assembly instruction obligation named before work proceeds.
1215	atomic instruction	authored	reviewed	An indivisible machine operation at instruction level.
1216	bandwidth {HW}	authored	generated_draft	bandwidth in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the bandwidth obligation named before work proceeds.
1217	barrier {HW}	authored	generated_draft	barrier in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the barrier obligation named before work proceeds.
1218	bit width	authored	generated_draft	bit width is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the bit width obligation named before work proceeds.
1219	boot ROM	authored	generated_draft	boot ROM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the boot ROM obligation named before work proceeds.
1220	branch predictor	authored	generated_draft	branch predictor is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the branch predictor obligation named before work proceeds.
1221	bus {HW}	authored	generated_draft	bus in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the bus obligation named before work proceeds.
1222	cache {HW}	authored	generated_draft	cache in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the cache obligation named before work proceeds.
1223	cache coherence	authored	generated_draft	cache coherence is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the cache coherence obligation named before work proceeds.
1224	cache line {HW}	authored	reviewed	The coherence-sized chunk of cached memory; too much sharing here hurts.
1225	clock	authored	generated_draft	clock is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the clock obligation named before work proceeds.
1226	clock cycle	authored	generated_draft	clock cycle is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the clock cycle obligation named before work proceeds.
1227	co-processor	authored	generated_draft	co-processor is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the co-processor obligation named before work proceeds.
1228	core {HW}	authored	generated_draft	core in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the core obligation named before work proceeds.
1229	CPU	authored	generated_draft	CPU is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the CPU obligation named before work proceeds.
1230	cycle budget	authored	generated_draft	cycle budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the cycle budget obligation named before work proceeds.
1231	DMA	authored	reviewed	Direct memory access: device moves bytes without making the CPU do every step.
1232	DRAM	authored	generated_draft	DRAM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the DRAM obligation named before work proceeds.
1233	driver interrupt	authored	generated_draft	driver interrupt is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the driver interrupt obligation named before work proceeds.
1234	EEPROM	authored	generated_draft	EEPROM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the EEPROM obligation named before work proceeds.
1235	endianness	authored	reviewed	The byte order in which multi-byte values are laid out.
1236	fence	authored	generated_draft	fence is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the fence obligation named before work proceeds.
1237	firmware {HW}	authored	reviewed	Software that is closer to the board than the application.
1238	flash	authored	generated_draft	flash is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the flash obligation named before work proceeds.
1239	FPGA	authored	generated_draft	FPGA is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the FPGA obligation named before work proceeds.
1240	frame budget	authored	generated_draft	frame budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the frame budget obligation named before work proceeds.
1241	frequency	authored	generated_draft	frequency is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the frequency obligation named before work proceeds.
1242	GPIO	authored	generated_draft	GPIO is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the GPIO obligation named before work proceeds.
1243	GPU	authored	reviewed	A massively parallel processor built for throughput-heavy workloads.
1244	heat budget	authored	generated_draft	heat budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the heat budget obligation named before work proceeds.
1245	I2C	authored	generated_draft	I2C is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the I2C obligation named before work proceeds.
1246	instruction cache	authored	generated_draft	instruction cache is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the instruction cache obligation named before work proceeds.
1247	instruction pointer	authored	generated_draft	instruction pointer is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the instruction pointer obligation named before work proceeds.
1248	interrupt service routine	authored	generated_draft	interrupt service routine is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the interrupt service routine obligation named before work proceeds.
1249	ioctl boundary	authored	generated_draft	ioctl boundary is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the ioctl boundary obligation named before work proceeds.
1250	IPC cost	authored	generated_draft	IPC cost is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the IPC cost obligation named before work proceeds.
1251	ISA	authored	reviewed	Instruction set architecture: the machine contract visible to software.
1252	jitter {HW}	authored	generated_draft	jitter in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the jitter obligation named before work proceeds.
1253	JTAG	authored	generated_draft	JTAG is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the JTAG obligation named before work proceeds.
1254	kernel bypass	authored	generated_draft	kernel bypass is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the kernel bypass obligation named before work proceeds.
1255	latency budget	authored	reviewed	The maximum delay the system is allowed to spend and still remain acceptable.
1256	memory channel	authored	generated_draft	memory channel is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the memory channel obligation named before work proceeds.
1257	memory-mapped I/O	authored	generated_draft	memory-mapped I/O is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the memory-mapped I/O obligation named before work proceeds.
1258	microcode	authored	generated_draft	microcode is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the microcode obligation named before work proceeds.
1259	MMIO	authored	generated_draft	MMIO is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the MMIO obligation named before work proceeds.
1260	NUMA	authored	generated_draft	NUMA is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the NUMA obligation named before work proceeds.
1261	NVRAM	authored	generated_draft	NVRAM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the NVRAM obligation named before work proceeds.
1262	opcode {HW}	authored	generated_draft	opcode in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the opcode obligation named before work proceeds.
1263	out-of-order execution	authored	generated_draft	out-of-order execution is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the out-of-order execution obligation named before work proceeds.
1264	PCIe	authored	generated_draft	PCIe is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the PCIe obligation named before work proceeds.
1265	pipeline {HW}	authored	generated_draft	pipeline in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the pipeline obligation named before work proceeds.
1266	power budget	authored	generated_draft	power budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the power budget obligation named before work proceeds.
1267	prefetcher	authored	generated_draft	prefetcher is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the prefetcher obligation named before work proceeds.
1268	real-time {HW}	authored	generated_draft	real-time in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the real-time obligation named before work proceeds.
1269	register	authored	reviewed	A tiny named storage cell inside the processor.
1270	register file	authored	generated_draft	register file is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the register file obligation named before work proceeds.
1271	reset vector	authored	generated_draft	reset vector is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the reset vector obligation named before work proceeds.
1272	ROM	authored	generated_draft	ROM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the ROM obligation named before work proceeds.
1273	RTOS	authored	generated_draft	RTOS is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the RTOS obligation named before work proceeds.
1274	runtime budget	authored	generated_draft	runtime budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the runtime budget obligation named before work proceeds.
1275	sensor loop	authored	generated_draft	sensor loop is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the sensor loop obligation named before work proceeds.
1276	SIMD	authored	reviewed	One instruction operating across many data lanes at once.
1277	SPI	authored	generated_draft	SPI is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the SPI obligation named before work proceeds.
1278	SRAM	authored	generated_draft	SRAM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the SRAM obligation named before work proceeds.
1279	superscalar	authored	generated_draft	superscalar is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the superscalar obligation named before work proceeds.
1280	thermal throttling	authored	generated_draft	thermal throttling is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the thermal throttling obligation named before work proceeds.
1281	throughput	authored	reviewed	How much useful work the system can push through a narrow world in bounded time. Shadow: chasing bulk capacity while tail latency burns the user.
1282	timing window	authored	generated_draft	timing window is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the timing window obligation named before work proceeds.
1283	TPU	authored	generated_draft	TPU is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the TPU obligation named before work proceeds.
1284	UART	authored	generated_draft	UART is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the UART obligation named before work proceeds.
1285	utilization	authored	reviewed	The fraction of available capacity actually being used.
1286	vector unit	authored	generated_draft	vector unit is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the vector unit obligation named before work proceeds.
1287	volatile	authored	reviewed	A promise to the compiler that this value may change through unusual means.
1288	watchdog timer	authored	generated_draft	watchdog timer is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the watchdog timer obligation named before work proceeds.
1289	wire speed	authored	generated_draft	wire speed is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the wire speed obligation named before work proceeds.
1290	zero-copy {HW}	authored	reviewed	Near-metal data movement without redundant duplication.

109.2 Entries

109.2.1 [1211] accelerator

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: accelerator is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the accelerator obligation named before work proceeds.

Shadow: misusing accelerator at rune 1211 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name accelerator when the prompt needs this obligation made explicit: accelerator is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the accelerator obligation named before work proceeds.
• Ask the assistant to state the accelerator shadow before proposing changes.

Example clause:

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

109.2.2 [1212] alignment {HW}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: alignment in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the alignment obligation named before work proceeds.

Shadow: misusing alignment at rune 1212 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name alignment when the prompt needs this obligation made explicit: alignment in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the alignment obligation named before work proceeds.
• Ask the assistant to state the alignment shadow before proposing changes.

Example clause:

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

109.2.3 [1213] ASIC

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: ASIC is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the ASIC obligation named before work proceeds.

Shadow: misusing ASIC at rune 1213 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name ASIC when the prompt needs this obligation made explicit: ASIC is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the ASIC obligation named before work proceeds.
• Ask the assistant to state the ASIC shadow before proposing changes.

Example clause:

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

109.2.4 [1214] assembly instruction

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: assembly instruction is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the assembly instruction obligation named before work proceeds.

Shadow: misusing assembly instruction at rune 1214 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name assembly instruction when the prompt needs this obligation made explicit: assembly instruction is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the assembly instruction obligation named before work proceeds.
• Ask the assistant to state the assembly instruction shadow before proposing changes.

Example clause:

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

109.2.5 [1215] atomic instruction

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: An indivisible machine operation at instruction level.

Shadow: misusing atomic instruction at rune 1215 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name atomic instruction when the prompt needs this obligation made explicit: An indivisible machine operation at instruction level.
• Ask the assistant to state the atomic instruction shadow before proposing changes.

Example clause:

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

Pocket gloss: An indivisible machine operation at instruction level.

109.2.6 [1216] bandwidth {HW}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: bandwidth in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the bandwidth obligation named before work proceeds.

Shadow: misusing bandwidth at rune 1216 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name bandwidth when the prompt needs this obligation made explicit: bandwidth in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the bandwidth obligation named before work proceeds.
• Ask the assistant to state the bandwidth shadow before proposing changes.

Example clause:

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

109.2.7 [1217] barrier {HW}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: barrier in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the barrier obligation named before work proceeds.

Shadow: misusing barrier at rune 1217 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name barrier when the prompt needs this obligation made explicit: barrier in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the barrier obligation named before work proceeds.
• Ask the assistant to state the barrier shadow before proposing changes.

Example clause:

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

109.2.8 [1218] bit width

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: bit width is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the bit width obligation named before work proceeds.

Shadow: misusing bit width at rune 1218 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name bit width when the prompt needs this obligation made explicit: bit width is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the bit width obligation named before work proceeds.
• Ask the assistant to state the bit width shadow before proposing changes.

Example clause:

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

109.2.9 [1219] boot ROM

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: boot ROM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the boot ROM obligation named before work proceeds.

Shadow: misusing boot ROM at rune 1219 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name boot ROM when the prompt needs this obligation made explicit: boot ROM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the boot ROM obligation named before work proceeds.
• Ask the assistant to state the boot ROM shadow before proposing changes.

Example clause:

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

109.2.10 [1220] branch predictor

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: branch predictor is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the branch predictor obligation named before work proceeds.

Shadow: misusing branch predictor at rune 1220 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name branch predictor when the prompt needs this obligation made explicit: branch predictor is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the branch predictor obligation named before work proceeds.
• Ask the assistant to state the branch predictor shadow before proposing changes.

Example clause:

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

109.2.11 [1221] bus {HW}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: bus in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the bus obligation named before work proceeds.

Shadow: misusing bus at rune 1221 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name bus when the prompt needs this obligation made explicit: bus in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the bus obligation named before work proceeds.
• Ask the assistant to state the bus shadow before proposing changes.

Example clause:

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

109.2.12 [1222] cache {HW}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cache in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the cache obligation named before work proceeds.

Shadow: misusing cache at rune 1222 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name cache when the prompt needs this obligation made explicit: cache in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the cache obligation named before work proceeds.
• 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.

109.2.13 [1223] cache coherence

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cache coherence is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the cache coherence obligation named before work proceeds.

Shadow: misusing cache coherence at rune 1223 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name cache coherence when the prompt needs this obligation made explicit: cache coherence is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the cache coherence obligation named before work proceeds.
• Ask the assistant to state the cache coherence shadow before proposing changes.

Example clause:

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

109.2.14 [1224] cache line {HW}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The coherence-sized chunk of cached memory; too much sharing here hurts.

Shadow: misusing cache line at rune 1224 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name cache line when the prompt needs this obligation made explicit: The coherence-sized chunk of cached memory; too much sharing here hurts.
• 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.

Pocket gloss: The coherence-sized chunk of cached memory; too much sharing here hurts.

109.2.15 [1225] clock

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: clock is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the clock obligation named before work proceeds.

Shadow: misusing clock at rune 1225 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name clock when the prompt needs this obligation made explicit: clock is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the clock obligation named before work proceeds.
• Ask the assistant to state the clock shadow before proposing changes.

Example clause:

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

109.2.16 [1226] clock cycle

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: clock cycle is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the clock cycle obligation named before work proceeds.

Shadow: misusing clock cycle at rune 1226 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name clock cycle when the prompt needs this obligation made explicit: clock cycle is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the clock cycle obligation named before work proceeds.
• Ask the assistant to state the clock cycle shadow before proposing changes.

Example clause:

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

109.2.17 [1227] co-processor

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: co-processor is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the co-processor obligation named before work proceeds.

Shadow: misusing co-processor at rune 1227 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name co-processor when the prompt needs this obligation made explicit: co-processor is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the co-processor obligation named before work proceeds.
• Ask the assistant to state the co-processor shadow before proposing changes.

Example clause:

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

109.2.18 [1228] core {HW}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: core in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the core obligation named before work proceeds.

Shadow: misusing core at rune 1228 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name core when the prompt needs this obligation made explicit: core in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the core obligation named before work proceeds.
• Ask the assistant to state the core shadow before proposing changes.

Example clause:

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

109.2.19 [1229] CPU

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: CPU is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the CPU obligation named before work proceeds.

Shadow: misusing CPU at rune 1229 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name CPU when the prompt needs this obligation made explicit: CPU is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the CPU obligation named before work proceeds.
• Ask the assistant to state the CPU shadow before proposing changes.

Example clause:

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

109.2.20 [1230] cycle budget

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cycle budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the cycle budget obligation named before work proceeds.

Shadow: misusing cycle budget at rune 1230 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name cycle budget when the prompt needs this obligation made explicit: cycle budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the cycle budget obligation named before work proceeds.
• Ask the assistant to state the cycle budget shadow before proposing changes.

Example clause:

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

109.2.21 [1231] DMA

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Direct memory access: device moves bytes without making the CPU do every step.

Shadow: misusing DMA at rune 1231 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name DMA when the prompt needs this obligation made explicit: Direct memory access: device moves bytes without making the CPU do every step.
• Ask the assistant to state the DMA shadow before proposing changes.

Example clause:

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

Pocket gloss: Direct memory access: device moves bytes without making the CPU do every step.

109.2.22 [1232] DRAM

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: DRAM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the DRAM obligation named before work proceeds.

Shadow: misusing DRAM at rune 1232 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name DRAM when the prompt needs this obligation made explicit: DRAM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the DRAM obligation named before work proceeds.
• Ask the assistant to state the DRAM shadow before proposing changes.

Example clause:

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

109.2.23 [1233] driver interrupt

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: driver interrupt is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the driver interrupt obligation named before work proceeds.

Shadow: misusing driver interrupt at rune 1233 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name driver interrupt when the prompt needs this obligation made explicit: driver interrupt is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the driver interrupt obligation named before work proceeds.
• Ask the assistant to state the driver interrupt shadow before proposing changes.

Example clause:

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

109.2.24 [1234] EEPROM

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: EEPROM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the EEPROM obligation named before work proceeds.

Shadow: misusing EEPROM at rune 1234 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name EEPROM when the prompt needs this obligation made explicit: EEPROM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the EEPROM obligation named before work proceeds.
• Ask the assistant to state the EEPROM shadow before proposing changes.

Example clause:

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

109.2.25 [1235] endianness

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The byte order in which multi-byte values are laid out.

Shadow: misusing endianness at rune 1235 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name endianness when the prompt needs this obligation made explicit: The byte order in which multi-byte values are laid out.
• Ask the assistant to state the endianness shadow before proposing changes.

Example clause:

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

Pocket gloss: The byte order in which multi-byte values are laid out.

109.2.26 [1236] fence

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fence is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the fence obligation named before work proceeds.

Shadow: misusing fence at rune 1236 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name fence when the prompt needs this obligation made explicit: fence is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the fence obligation named before work proceeds.
• Ask the assistant to state the fence shadow before proposing changes.

Example clause:

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

109.2.27 [1237] firmware {HW}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Software that is closer to the board than the application.

Shadow: misusing firmware at rune 1237 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name firmware when the prompt needs this obligation made explicit: Software that is closer to the board than the application.
• Ask the assistant to state the firmware shadow before proposing changes.

Example clause:

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

Pocket gloss: Software that is closer to the board than the application.

109.2.28 [1238] flash

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: flash is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the flash obligation named before work proceeds.

Shadow: misusing flash at rune 1238 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name flash when the prompt needs this obligation made explicit: flash is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the flash obligation named before work proceeds.
• Ask the assistant to state the flash shadow before proposing changes.

Example clause:

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

109.2.29 [1239] FPGA

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: FPGA is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the FPGA obligation named before work proceeds.

Shadow: misusing FPGA at rune 1239 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name FPGA when the prompt needs this obligation made explicit: FPGA is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the FPGA obligation named before work proceeds.
• Ask the assistant to state the FPGA shadow before proposing changes.

Example clause:

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

109.2.30 [1240] frame budget

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: frame budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the frame budget obligation named before work proceeds.

Shadow: misusing frame budget at rune 1240 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name frame budget when the prompt needs this obligation made explicit: frame budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the frame budget obligation named before work proceeds.
• Ask the assistant to state the frame budget shadow before proposing changes.

Example clause:

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

109.2.31 [1241] frequency

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: frequency is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the frequency obligation named before work proceeds.

Shadow: misusing frequency at rune 1241 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name frequency when the prompt needs this obligation made explicit: frequency is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the frequency obligation named before work proceeds.
• Ask the assistant to state the frequency shadow before proposing changes.

Example clause:

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

109.2.32 [1242] GPIO

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: GPIO is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the GPIO obligation named before work proceeds.

Shadow: misusing GPIO at rune 1242 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name GPIO when the prompt needs this obligation made explicit: GPIO is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the GPIO obligation named before work proceeds.
• Ask the assistant to state the GPIO shadow before proposing changes.

Example clause:

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

109.2.33 [1243] GPU

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A massively parallel processor built for throughput-heavy workloads.

Shadow: misusing GPU at rune 1243 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name GPU when the prompt needs this obligation made explicit: A massively parallel processor built for throughput-heavy workloads.
• Ask the assistant to state the GPU shadow before proposing changes.

Example clause:

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

Pocket gloss: A massively parallel processor built for throughput-heavy workloads.

109.2.34 [1244] heat budget

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: heat budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the heat budget obligation named before work proceeds.

Shadow: misusing heat budget at rune 1244 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name heat budget when the prompt needs this obligation made explicit: heat budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the heat budget obligation named before work proceeds.
• Ask the assistant to state the heat budget shadow before proposing changes.

Example clause:

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

109.2.35 [1245] I2C

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: I2C is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the I2C obligation named before work proceeds.

Shadow: misusing I2C at rune 1245 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name I2C when the prompt needs this obligation made explicit: I2C is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the I2C obligation named before work proceeds.
• Ask the assistant to state the I2C shadow before proposing changes.

Example clause:

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

109.2.36 [1246] instruction cache

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: instruction cache is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the instruction cache obligation named before work proceeds.

Shadow: misusing instruction cache at rune 1246 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name instruction cache when the prompt needs this obligation made explicit: instruction cache is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the instruction cache obligation named before work proceeds.
• Ask the assistant to state the instruction cache shadow before proposing changes.

Example clause:

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

109.2.37 [1247] instruction pointer

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: instruction pointer is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the instruction pointer obligation named before work proceeds.

Shadow: misusing instruction pointer at rune 1247 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name instruction pointer when the prompt needs this obligation made explicit: instruction pointer is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the instruction pointer obligation named before work proceeds.
• Ask the assistant to state the instruction pointer shadow before proposing changes.

Example clause:

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

109.2.38 [1248] interrupt service routine

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: interrupt service routine is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the interrupt service routine obligation named before work proceeds.

Shadow: misusing interrupt service routine at rune 1248 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name interrupt service routine when the prompt needs this obligation made explicit: interrupt service routine is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the interrupt service routine obligation named before work proceeds.
• Ask the assistant to state the interrupt service routine shadow before proposing changes.

Example clause:

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

109.2.39 [1249] ioctl boundary

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: ioctl boundary is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the ioctl boundary obligation named before work proceeds.

Shadow: misusing ioctl boundary at rune 1249 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name ioctl boundary when the prompt needs this obligation made explicit: ioctl boundary is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the ioctl boundary obligation named before work proceeds.
• Ask the assistant to state the ioctl boundary shadow before proposing changes.

Example clause:

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

109.2.40 [1250] IPC cost

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: IPC cost is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the IPC cost obligation named before work proceeds.

Shadow: misusing IPC cost at rune 1250 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name IPC cost when the prompt needs this obligation made explicit: IPC cost is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the IPC cost obligation named before work proceeds.
• Ask the assistant to state the IPC cost shadow before proposing changes.

Example clause:

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

109.2.41 [1251] ISA

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Instruction set architecture: the machine contract visible to software.

Shadow: misusing ISA at rune 1251 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name ISA when the prompt needs this obligation made explicit: Instruction set architecture: the machine contract visible to software.
• Ask the assistant to state the ISA shadow before proposing changes.

Example clause:

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

Pocket gloss: Instruction set architecture: the machine contract visible to software.

109.2.42 [1252] jitter {HW}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: jitter in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the jitter obligation named before work proceeds.

Shadow: misusing jitter at rune 1252 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name jitter when the prompt needs this obligation made explicit: jitter in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the jitter obligation named before work proceeds.
• Ask the assistant to state the jitter shadow before proposing changes.

Example clause:

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

109.2.43 [1253] JTAG

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: JTAG is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the JTAG obligation named before work proceeds.

Shadow: misusing JTAG at rune 1253 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name JTAG when the prompt needs this obligation made explicit: JTAG is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the JTAG obligation named before work proceeds.
• Ask the assistant to state the JTAG shadow before proposing changes.

Example clause:

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

109.2.44 [1254] kernel bypass

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: kernel bypass is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the kernel bypass obligation named before work proceeds.

Shadow: misusing kernel bypass at rune 1254 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name kernel bypass when the prompt needs this obligation made explicit: kernel bypass is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the kernel bypass obligation named before work proceeds.
• Ask the assistant to state the kernel bypass shadow before proposing changes.

Example clause:

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

109.2.45 [1255] latency budget

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The maximum delay the system is allowed to spend and still remain acceptable.

Shadow: misusing latency budget at rune 1255 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name latency budget when the prompt needs this obligation made explicit: The maximum delay the system is allowed to spend and still remain acceptable.
• Ask the assistant to state the latency budget shadow before proposing changes.

Example clause:

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

Pocket gloss: The maximum delay the system is allowed to spend and still remain acceptable.

109.2.46 [1256] memory channel

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: memory channel is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the memory channel obligation named before work proceeds.

Shadow: misusing memory channel at rune 1256 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name memory channel when the prompt needs this obligation made explicit: memory channel is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the memory channel obligation named before work proceeds.
• Ask the assistant to state the memory channel shadow before proposing changes.

Example clause:

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

109.2.47 [1257] memory-mapped I/O

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: memory-mapped I/O is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the memory-mapped I/O obligation named before work proceeds.

Shadow: misusing memory-mapped I/O at rune 1257 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name memory-mapped I/O when the prompt needs this obligation made explicit: memory-mapped I/O is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the memory-mapped I/O obligation named before work proceeds.
• Ask the assistant to state the memory-mapped I/O shadow before proposing changes.

Example clause:

Before editing, state the memory-mapped I/O obligation, the evidence that satisfies it, and the failure mode if it is missing.

109.2.48 [1258] microcode

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: microcode is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the microcode obligation named before work proceeds.

Shadow: misusing microcode at rune 1258 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name microcode when the prompt needs this obligation made explicit: microcode is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the microcode obligation named before work proceeds.
• Ask the assistant to state the microcode shadow before proposing changes.

Example clause:

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

109.2.49 [1259] MMIO

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: MMIO is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the MMIO obligation named before work proceeds.

Shadow: misusing MMIO at rune 1259 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name MMIO when the prompt needs this obligation made explicit: MMIO is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the MMIO obligation named before work proceeds.
• Ask the assistant to state the MMIO shadow before proposing changes.

Example clause:

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

109.2.50 [1260] NUMA

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: NUMA is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the NUMA obligation named before work proceeds.

Shadow: misusing NUMA at rune 1260 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name NUMA when the prompt needs this obligation made explicit: NUMA is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the NUMA obligation named before work proceeds.
• Ask the assistant to state the NUMA shadow before proposing changes.

Example clause:

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

109.2.51 [1261] NVRAM

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: NVRAM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the NVRAM obligation named before work proceeds.

Shadow: misusing NVRAM at rune 1261 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name NVRAM when the prompt needs this obligation made explicit: NVRAM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the NVRAM obligation named before work proceeds.
• Ask the assistant to state the NVRAM shadow before proposing changes.

Example clause:

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

109.2.52 [1262] opcode {HW}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: opcode in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the opcode obligation named before work proceeds.

Shadow: misusing opcode at rune 1262 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name opcode when the prompt needs this obligation made explicit: opcode in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the opcode obligation named before work proceeds.
• Ask the assistant to state the opcode shadow before proposing changes.

Example clause:

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

109.2.53 [1263] out-of-order execution

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: out-of-order execution is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the out-of-order execution obligation named before work proceeds.

Shadow: misusing out-of-order execution at rune 1263 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name out-of-order execution when the prompt needs this obligation made explicit: out-of-order execution is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the out-of-order execution obligation named before work proceeds.
• Ask the assistant to state the out-of-order execution shadow before proposing changes.

Example clause:

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

109.2.54 [1264] PCIe

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: PCIe is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the PCIe obligation named before work proceeds.

Shadow: misusing PCIe at rune 1264 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name PCIe when the prompt needs this obligation made explicit: PCIe is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the PCIe obligation named before work proceeds.
• Ask the assistant to state the PCIe shadow before proposing changes.

Example clause:

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

109.2.55 [1265] pipeline {HW}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: pipeline in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the pipeline obligation named before work proceeds.

Shadow: misusing pipeline at rune 1265 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name pipeline when the prompt needs this obligation made explicit: pipeline in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the pipeline obligation named before work proceeds.
• Ask the assistant to state the pipeline shadow before proposing changes.

Example clause:

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

109.2.56 [1266] power budget

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: power budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the power budget obligation named before work proceeds.

Shadow: misusing power budget at rune 1266 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name power budget when the prompt needs this obligation made explicit: power budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the power budget obligation named before work proceeds.
• Ask the assistant to state the power budget shadow before proposing changes.

Example clause:

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

109.2.57 [1267] prefetcher

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: prefetcher is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the prefetcher obligation named before work proceeds.

Shadow: misusing prefetcher at rune 1267 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name prefetcher when the prompt needs this obligation made explicit: prefetcher is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the prefetcher obligation named before work proceeds.
• Ask the assistant to state the prefetcher shadow before proposing changes.

Example clause:

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

109.2.58 [1268] real-time {HW}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: real-time in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the real-time obligation named before work proceeds.

Shadow: misusing real-time at rune 1268 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name real-time when the prompt needs this obligation made explicit: real-time in its HW sense is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the real-time obligation named before work proceeds.
• Ask the assistant to state the real-time shadow before proposing changes.

Example clause:

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

109.2.59 [1269] register

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A tiny named storage cell inside the processor.

Shadow: misusing register at rune 1269 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name register when the prompt needs this obligation made explicit: A tiny named storage cell inside the processor.
• Ask the assistant to state the register shadow before proposing changes.

Example clause:

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

Pocket gloss: A tiny named storage cell inside the processor.

109.2.60 [1270] register file

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: register file is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the register file obligation named before work proceeds.

Shadow: misusing register file at rune 1270 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name register file when the prompt needs this obligation made explicit: register file is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the register file obligation named before work proceeds.
• Ask the assistant to state the register file shadow before proposing changes.

Example clause:

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

109.2.61 [1271] reset vector

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: reset vector is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the reset vector obligation named before work proceeds.

Shadow: misusing reset vector at rune 1271 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name reset vector when the prompt needs this obligation made explicit: reset vector is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the reset vector obligation named before work proceeds.
• Ask the assistant to state the reset vector shadow before proposing changes.

Example clause:

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

109.2.62 [1272] ROM

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: ROM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the ROM obligation named before work proceeds.

Shadow: misusing ROM at rune 1272 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name ROM when the prompt needs this obligation made explicit: ROM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the ROM obligation named before work proceeds.
• Ask the assistant to state the ROM shadow before proposing changes.

Example clause:

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

109.2.63 [1273] RTOS

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: RTOS is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the RTOS obligation named before work proceeds.

Shadow: misusing RTOS at rune 1273 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name RTOS when the prompt needs this obligation made explicit: RTOS is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the RTOS obligation named before work proceeds.
• Ask the assistant to state the RTOS shadow before proposing changes.

Example clause:

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

109.2.64 [1274] runtime budget

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: runtime budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the runtime budget obligation named before work proceeds.

Shadow: misusing runtime budget at rune 1274 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name runtime budget when the prompt needs this obligation made explicit: runtime budget is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the runtime budget obligation named before work proceeds.
• Ask the assistant to state the runtime budget shadow before proposing changes.

Example clause:

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

109.2.65 [1275] sensor loop

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sensor loop is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the sensor loop obligation named before work proceeds.

Shadow: misusing sensor loop at rune 1275 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name sensor loop when the prompt needs this obligation made explicit: sensor loop is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the sensor loop obligation named before work proceeds.
• Ask the assistant to state the sensor loop shadow before proposing changes.

Example clause:

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

109.2.66 [1276] SIMD

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: One instruction operating across many data lanes at once.

Shadow: misusing SIMD at rune 1276 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name SIMD when the prompt needs this obligation made explicit: One instruction operating across many data lanes at once.
• Ask the assistant to state the SIMD shadow before proposing changes.

Example clause:

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

Pocket gloss: One instruction operating across many data lanes at once.

109.2.67 [1277] SPI

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: SPI is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the SPI obligation named before work proceeds.

Shadow: misusing SPI at rune 1277 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name SPI when the prompt needs this obligation made explicit: SPI is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the SPI obligation named before work proceeds.
• Ask the assistant to state the SPI shadow before proposing changes.

Example clause:

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

109.2.68 [1278] SRAM

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: SRAM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the SRAM obligation named before work proceeds.

Shadow: misusing SRAM at rune 1278 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name SRAM when the prompt needs this obligation made explicit: SRAM is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the SRAM obligation named before work proceeds.
• Ask the assistant to state the SRAM shadow before proposing changes.

Example clause:

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

109.2.69 [1279] superscalar

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: superscalar is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the superscalar obligation named before work proceeds.

Shadow: misusing superscalar at rune 1279 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name superscalar when the prompt needs this obligation made explicit: superscalar is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the superscalar obligation named before work proceeds.
• Ask the assistant to state the superscalar shadow before proposing changes.

Example clause:

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

109.2.70 [1280] thermal throttling

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: thermal throttling is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the thermal throttling obligation named before work proceeds.

Shadow: misusing thermal throttling at rune 1280 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name thermal throttling when the prompt needs this obligation made explicit: thermal throttling is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the thermal throttling obligation named before work proceeds.
• Ask the assistant to state the thermal throttling shadow before proposing changes.

Example clause:

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

109.2.71 [1281] throughput

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: How much useful work the system can push through a narrow world in bounded time.

Shadow: chasing bulk capacity while tail latency burns the user.

Prompt uses:

• Name throughput when the prompt needs this obligation made explicit: How much useful work the system can push through a narrow world in bounded time.
• Ask the assistant to state the throughput shadow before proposing changes.

Example clause:

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

Pocket gloss: How much useful work passes through in bounded time.

109.2.72 [1282] timing window

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: timing window is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the timing window obligation named before work proceeds.

Shadow: misusing timing window at rune 1282 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name timing window when the prompt needs this obligation made explicit: timing window is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the timing window obligation named before work proceeds.
• Ask the assistant to state the timing window shadow before proposing changes.

Example clause:

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

109.2.73 [1283] TPU

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: TPU is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the TPU obligation named before work proceeds.

Shadow: misusing TPU at rune 1283 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name TPU when the prompt needs this obligation made explicit: TPU is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the TPU obligation named before work proceeds.
• Ask the assistant to state the TPU shadow before proposing changes.

Example clause:

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

109.2.74 [1284] UART

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: UART is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the UART obligation named before work proceeds.

Shadow: misusing UART at rune 1284 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name UART when the prompt needs this obligation made explicit: UART is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the UART obligation named before work proceeds.
• Ask the assistant to state the UART shadow before proposing changes.

Example clause:

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

109.2.75 [1285] utilization

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The fraction of available capacity actually being used.

Shadow: misusing utilization at rune 1285 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name utilization when the prompt needs this obligation made explicit: The fraction of available capacity actually being used.
• Ask the assistant to state the utilization shadow before proposing changes.

Example clause:

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

Pocket gloss: The fraction of available capacity actually being used.

109.2.76 [1286] vector unit

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: vector unit is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the vector unit obligation named before work proceeds.

Shadow: misusing vector unit at rune 1286 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name vector unit when the prompt needs this obligation made explicit: vector unit is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the vector unit obligation named before work proceeds.
• Ask the assistant to state the vector unit shadow before proposing changes.

Example clause:

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

109.2.77 [1287] volatile

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A promise to the compiler that this value may change through unusual means.

Shadow: misusing volatile at rune 1287 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name volatile when the prompt needs this obligation made explicit: A promise to the compiler that this value may change through unusual means.
• Ask the assistant to state the volatile shadow before proposing changes.

Example clause:

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

Pocket gloss: A promise to the compiler that this value may change through unusual means.

109.2.78 [1288] watchdog timer

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: watchdog timer is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the watchdog timer obligation named before work proceeds.

Shadow: misusing watchdog timer at rune 1288 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name watchdog timer when the prompt needs this obligation made explicit: watchdog timer is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the watchdog timer obligation named before work proceeds.
• Ask the assistant to state the watchdog timer shadow before proposing changes.

Example clause:

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

109.2.79 [1289] wire speed

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: wire speed is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the wire speed obligation named before work proceeds.

Shadow: misusing wire speed at rune 1289 in the hardware lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name wire speed when the prompt needs this obligation made explicit: wire speed is a hardware and performance-near systems rune for connect software choices to physical capacity, latency, and bandwidth; use it when the artifact needs the wire speed obligation named before work proceeds.
• Ask the assistant to state the wire speed shadow before proposing changes.

Example clause:

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

109.2.80 [1290] zero-copy {HW}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Near-metal data movement without redundant duplication.

Shadow: misusing zero-copy at rune 1290 in the HW lane can let clean abstractions can break under physical timing or capacity limits; verify by requiring the caster to state the measured budget, device boundary, and operating envelope.

Prompt uses:

• Name zero-copy when the prompt needs this obligation made explicit: Near-metal data movement without redundant duplication.
• 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: Near-metal data movement without redundant duplication.