112  Failure Words, Pathologies, and Counter-Spells

113 Failure Words, Pathologies, and Counter-Spells

Range: 1513-1582.

113.1 Completion

Status	Count
authored	70

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

Sigil	Term	Completion	Semantic	Summary
1513	anomaly	authored	generated_draft	anomaly is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the anomaly obligation named before work proceeds.
1514	backlog collapse	authored	generated_draft	backlog collapse is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the backlog collapse obligation named before work proceeds.
1515	broken pipe	authored	generated_draft	broken pipe is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the broken pipe obligation named before work proceeds.
1516	bug	authored	generated_draft	bug is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the bug obligation named before work proceeds.
1517	cascading failure	authored	reviewed	One failure fans out into many dependent failures.
1518	checksum mismatch	authored	generated_draft	checksum mismatch is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the checksum mismatch obligation named before work proceeds.
1519	collision	authored	generated_draft	collision is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the collision obligation named before work proceeds.
1520	contention	authored	reviewed	Too many actors fighting for the same scarce resource.
1521	corruption	authored	reviewed	Stored or transmitted truth damaged into falsehood.
1522	crash	authored	generated_draft	crash is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the crash obligation named before work proceeds.
1523	curse of shared state	authored	generated_draft	curse of shared state is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the curse of shared state obligation named before work proceeds.
1524	data drift	authored	generated_draft	data drift is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the data drift obligation named before work proceeds.
1525	deadlock {Curse}	authored	reviewed	Two or more actors wait on one another forever.
1526	defect	authored	generated_draft	defect is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the defect obligation named before work proceeds.
1527	degraded mode	authored	generated_draft	degraded mode is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the degraded mode obligation named before work proceeds.
1528	denial of service	authored	generated_draft	denial of service is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the denial of service obligation named before work proceeds.
1529	dependency hell	authored	reviewed	Transitive requirements turning ordinary change into a trap.
1530	divergence	authored	generated_draft	divergence is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the divergence obligation named before work proceeds.
1531	drift	authored	reviewed	Slow departure from the world you thought you were still in.
1532	error	authored	generated_draft	error is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the error obligation named before work proceeds.
1533	exception	authored	generated_draft	exception is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the exception obligation named before work proceeds.
1534	exhaustion	authored	reviewed	The resource is simply used up.
1535	failure domain	authored	generated_draft	failure domain is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the failure domain obligation named before work proceeds.
1536	fault	authored	generated_draft	fault is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the fault obligation named before work proceeds.
1537	flapping	authored	reviewed	Rapid unhealthy oscillation between states.
1538	fragmentation	authored	generated_draft	fragmentation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the fragmentation obligation named before work proceeds.
1539	freeze	authored	generated_draft	freeze is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the freeze obligation named before work proceeds.
1540	hang	authored	generated_draft	hang is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the hang obligation named before work proceeds.
1541	hotspot	authored	generated_draft	hotspot is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the hotspot obligation named before work proceeds.
1542	inconsistent read	authored	reviewed	A read that sees a world that never really existed as one coherent moment.
1543	infinite loop	authored	generated_draft	infinite loop is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the infinite loop obligation named before work proceeds.
1544	invalid state	authored	generated_draft	invalid state is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the invalid state obligation named before work proceeds.
1545	jitter spike	authored	generated_draft	jitter spike is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the jitter spike obligation named before work proceeds.
1546	leak {Curse}	authored	reviewed	Something escapes the boundary that should have held it: memory, secrets, file descriptors, authority, abstraction, or time.
1547	livelock	authored	reviewed	Everyone keeps moving but nobody makes progress.
1548	lost update	authored	reviewed	One writer quietly stomps another writer’s valid change.
1549	memory corruption	authored	generated_draft	memory corruption is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the memory corruption obligation named before work proceeds.
1550	mismatch	authored	generated_draft	mismatch is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the mismatch obligation named before work proceeds.
1551	misroute	authored	generated_draft	misroute is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the misroute obligation named before work proceeds.
1552	missed heartbeat	authored	generated_draft	missed heartbeat is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the missed heartbeat obligation named before work proceeds.
1553	null dereference	authored	generated_draft	null dereference is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the null dereference obligation named before work proceeds.
1554	outage	authored	reviewed	Service unavailable where availability was expected.
1555	overflow	authored	reviewed	Value exceeds the representable range.
1556	packet loss {Curse}	authored	generated_draft	packet loss in its Curse sense is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the packet loss obligation named before work proceeds.
1557	panic	authored	generated_draft	panic is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the panic obligation named before work proceeds.
1558	partial failure	authored	reviewed	Some of the system failed while the rest kept limping.
1559	partition storm	authored	generated_draft	partition storm is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the partition storm obligation named before work proceeds.
1560	poison pill	authored	generated_draft	poison pill is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the poison pill obligation named before work proceeds.
1561	race	authored	reviewed	An ordering curse: outcomes depend on timing you do not actually control. Name the race and the system becomes debuggable again.
1562	regression	authored	reviewed	A previously solved bug or quality loss has returned.
1563	resource starvation	authored	generated_draft	resource starvation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the resource starvation obligation named before work proceeds.
1564	retry storm	authored	reviewed	Recovery logic amplifying failure instead of containing it. Unguided retries can turn a partial outage into a self-made siege.
1565	rollback failure	authored	generated_draft	rollback failure is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the rollback failure obligation named before work proceeds.
1566	saturation	authored	generated_draft	saturation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the saturation obligation named before work proceeds.
1567	schema drift	authored	reviewed	The stored world and the assumed world have silently stopped matching. This is how migrations keep hurting after everyone thinks they are done.
1568	split-brain {Curse}	authored	reviewed	Separated leaders each believe they are authoritative.
1569	stack overflow	authored	generated_draft	stack overflow is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the stack overflow obligation named before work proceeds.
1570	stale read	authored	generated_draft	stale read is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the stale read obligation named before work proceeds.
1571	stall	authored	generated_draft	stall is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the stall obligation named before work proceeds.
1572	starvation	authored	generated_draft	starvation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the starvation obligation named before work proceeds.
1573	state explosion	authored	generated_draft	state explosion is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the state explosion obligation named before work proceeds.
1574	storm	authored	generated_draft	storm is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the storm obligation named before work proceeds.
1575	thrash	authored	generated_draft	thrash is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the thrash obligation named before work proceeds.
1576	timeout {Curse}	authored	generated_draft	timeout in its Curse sense is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the timeout obligation named before work proceeds.
1577	torn write	authored	generated_draft	torn write is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the torn write obligation named before work proceeds.
1578	underflow	authored	generated_draft	underflow is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the underflow obligation named before work proceeds.
1579	unhandled exception	authored	generated_draft	unhandled exception is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the unhandled exception obligation named before work proceeds.
1580	unstable equilibrium	authored	generated_draft	unstable equilibrium is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the unstable equilibrium obligation named before work proceeds.
1581	write amplification	authored	generated_draft	write amplification is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the write amplification obligation named before work proceeds.
1582	write skew {Curse}	authored	generated_draft	write skew in its Curse sense is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the write skew obligation named before work proceeds.

113.2 Entries

113.2.1 [1513] anomaly

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: anomaly is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the anomaly obligation named before work proceeds.

Shadow: misusing anomaly at rune 1513 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name anomaly when the prompt needs this obligation made explicit: anomaly is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the anomaly obligation named before work proceeds.
• Ask the assistant to state the anomaly shadow before proposing changes.

Example clause:

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

113.2.2 [1514] backlog collapse

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: backlog collapse is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the backlog collapse obligation named before work proceeds.

Shadow: misusing backlog collapse at rune 1514 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name backlog collapse when the prompt needs this obligation made explicit: backlog collapse is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the backlog collapse obligation named before work proceeds.
• Ask the assistant to state the backlog collapse shadow before proposing changes.

Example clause:

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

113.2.3 [1515] broken pipe

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: broken pipe is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the broken pipe obligation named before work proceeds.

Shadow: misusing broken pipe at rune 1515 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name broken pipe when the prompt needs this obligation made explicit: broken pipe is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the broken pipe obligation named before work proceeds.
• Ask the assistant to state the broken pipe shadow before proposing changes.

Example clause:

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

113.2.4 [1516] bug

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: bug is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the bug obligation named before work proceeds.

Shadow: misusing bug at rune 1516 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name bug when the prompt needs this obligation made explicit: bug is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the bug obligation named before work proceeds.
• Ask the assistant to state the bug shadow before proposing changes.

Example clause:

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

113.2.5 [1517] cascading failure

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: One failure fans out into many dependent failures.

Shadow: misusing cascading failure at rune 1517 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name cascading failure when the prompt needs this obligation made explicit: One failure fans out into many dependent failures.
• Ask the assistant to state the cascading failure shadow before proposing changes.

Example clause:

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

Pocket gloss: One failure fans out into many dependent failures.

113.2.6 [1518] checksum mismatch

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: checksum mismatch is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the checksum mismatch obligation named before work proceeds.

Shadow: misusing checksum mismatch at rune 1518 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name checksum mismatch when the prompt needs this obligation made explicit: checksum mismatch is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the checksum mismatch obligation named before work proceeds.
• Ask the assistant to state the checksum mismatch shadow before proposing changes.

Example clause:

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

113.2.7 [1519] collision

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: collision is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the collision obligation named before work proceeds.

Shadow: misusing collision at rune 1519 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name collision when the prompt needs this obligation made explicit: collision is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the collision obligation named before work proceeds.
• Ask the assistant to state the collision shadow before proposing changes.

Example clause:

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

113.2.8 [1520] contention

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Too many actors fighting for the same scarce resource.

Shadow: misusing contention at rune 1520 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name contention when the prompt needs this obligation made explicit: Too many actors fighting for the same scarce resource.
• Ask the assistant to state the contention shadow before proposing changes.

Example clause:

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

Pocket gloss: Too many actors fighting for the same scarce resource.

113.2.9 [1521] corruption

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Stored or transmitted truth damaged into falsehood.

Shadow: misusing corruption at rune 1521 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name corruption when the prompt needs this obligation made explicit: Stored or transmitted truth damaged into falsehood.
• Ask the assistant to state the corruption shadow before proposing changes.

Example clause:

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

Pocket gloss: Stored or transmitted truth damaged into falsehood.

113.2.10 [1522] crash

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: crash is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the crash obligation named before work proceeds.

Shadow: misusing crash at rune 1522 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name crash when the prompt needs this obligation made explicit: crash is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the crash obligation named before work proceeds.
• Ask the assistant to state the crash shadow before proposing changes.

Example clause:

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

113.2.11 [1523] curse of shared state

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: curse of shared state is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the curse of shared state obligation named before work proceeds.

Shadow: misusing curse of shared state at rune 1523 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name curse of shared state when the prompt needs this obligation made explicit: curse of shared state is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the curse of shared state obligation named before work proceeds.
• Ask the assistant to state the curse of shared state shadow before proposing changes.

Example clause:

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

113.2.12 [1524] data drift

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: data drift is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the data drift obligation named before work proceeds.

Shadow: misusing data drift at rune 1524 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name data drift when the prompt needs this obligation made explicit: data drift is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the data drift obligation named before work proceeds.
• Ask the assistant to state the data drift shadow before proposing changes.

Example clause:

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

113.2.13 [1525] deadlock {Curse}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Two or more actors wait on one another forever.

Shadow: misusing deadlock at rune 1525 in the Curse lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name deadlock when the prompt needs this obligation made explicit: Two or more actors wait on one another forever.
• Ask the assistant to state the deadlock shadow before proposing changes.

Example clause:

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

Pocket gloss: Two or more actors wait on one another forever.

113.2.14 [1526] defect

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: defect is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the defect obligation named before work proceeds.

Shadow: misusing defect at rune 1526 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name defect when the prompt needs this obligation made explicit: defect is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the defect obligation named before work proceeds.
• Ask the assistant to state the defect shadow before proposing changes.

Example clause:

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

113.2.15 [1527] degraded mode

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: degraded mode is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the degraded mode obligation named before work proceeds.

Shadow: misusing degraded mode at rune 1527 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name degraded mode when the prompt needs this obligation made explicit: degraded mode is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the degraded mode obligation named before work proceeds.
• Ask the assistant to state the degraded mode shadow before proposing changes.

Example clause:

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

113.2.16 [1528] denial of service

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: denial of service is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the denial of service obligation named before work proceeds.

Shadow: misusing denial of service at rune 1528 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name denial of service when the prompt needs this obligation made explicit: denial of service is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the denial of service obligation named before work proceeds.
• Ask the assistant to state the denial of service shadow before proposing changes.

Example clause:

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

113.2.17 [1529] dependency hell

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Transitive requirements turning ordinary change into a trap.

Shadow: misusing dependency hell at rune 1529 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name dependency hell when the prompt needs this obligation made explicit: Transitive requirements turning ordinary change into a trap.
• Ask the assistant to state the dependency hell shadow before proposing changes.

Example clause:

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

Pocket gloss: Transitive requirements turning ordinary change into a trap.

113.2.18 [1530] divergence

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: divergence is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the divergence obligation named before work proceeds.

Shadow: misusing divergence at rune 1530 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name divergence when the prompt needs this obligation made explicit: divergence is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the divergence obligation named before work proceeds.
• Ask the assistant to state the divergence shadow before proposing changes.

Example clause:

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

113.2.19 [1531] drift

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Slow departure from the world you thought you were still in.

Shadow: misusing drift at rune 1531 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name drift when the prompt needs this obligation made explicit: Slow departure from the world you thought you were still in.
• Ask the assistant to state the drift shadow before proposing changes.

Example clause:

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

Pocket gloss: Slow departure from the world you thought you were still in.

113.2.20 [1532] error

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: error is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the error obligation named before work proceeds.

Shadow: misusing error at rune 1532 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name error when the prompt needs this obligation made explicit: error is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the error obligation named before work proceeds.
• Ask the assistant to state the error shadow before proposing changes.

Example clause:

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

113.2.21 [1533] exception

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: exception is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the exception obligation named before work proceeds.

Shadow: misusing exception at rune 1533 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name exception when the prompt needs this obligation made explicit: exception is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the exception obligation named before work proceeds.
• Ask the assistant to state the exception shadow before proposing changes.

Example clause:

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

113.2.22 [1534] exhaustion

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The resource is simply used up.

Shadow: misusing exhaustion at rune 1534 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name exhaustion when the prompt needs this obligation made explicit: The resource is simply used up.
• Ask the assistant to state the exhaustion shadow before proposing changes.

Example clause:

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

Pocket gloss: The resource is simply used up.

113.2.23 [1535] failure domain

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: failure domain is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the failure domain obligation named before work proceeds.

Shadow: misusing failure domain at rune 1535 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name failure domain when the prompt needs this obligation made explicit: failure domain is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the failure domain obligation named before work proceeds.
• Ask the assistant to state the failure domain shadow before proposing changes.

Example clause:

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

113.2.24 [1536] fault

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fault is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the fault obligation named before work proceeds.

Shadow: misusing fault at rune 1536 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name fault when the prompt needs this obligation made explicit: fault is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the fault obligation named before work proceeds.
• Ask the assistant to state the fault shadow before proposing changes.

Example clause:

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

113.2.25 [1537] flapping

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Rapid unhealthy oscillation between states.

Shadow: misusing flapping at rune 1537 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name flapping when the prompt needs this obligation made explicit: Rapid unhealthy oscillation between states.
• Ask the assistant to state the flapping shadow before proposing changes.

Example clause:

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

Pocket gloss: Rapid unhealthy oscillation between states.

113.2.26 [1538] fragmentation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fragmentation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the fragmentation obligation named before work proceeds.

Shadow: misusing fragmentation at rune 1538 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name fragmentation when the prompt needs this obligation made explicit: fragmentation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the fragmentation obligation named before work proceeds.
• Ask the assistant to state the fragmentation shadow before proposing changes.

Example clause:

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

113.2.27 [1539] freeze

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: freeze is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the freeze obligation named before work proceeds.

Shadow: misusing freeze at rune 1539 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name freeze when the prompt needs this obligation made explicit: freeze is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the freeze obligation named before work proceeds.
• Ask the assistant to state the freeze shadow before proposing changes.

Example clause:

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

113.2.28 [1540] hang

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: hang is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the hang obligation named before work proceeds.

Shadow: misusing hang at rune 1540 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name hang when the prompt needs this obligation made explicit: hang is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the hang obligation named before work proceeds.
• Ask the assistant to state the hang shadow before proposing changes.

Example clause:

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

113.2.29 [1541] hotspot

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: hotspot is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the hotspot obligation named before work proceeds.

Shadow: misusing hotspot at rune 1541 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name hotspot when the prompt needs this obligation made explicit: hotspot is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the hotspot obligation named before work proceeds.
• Ask the assistant to state the hotspot shadow before proposing changes.

Example clause:

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

113.2.30 [1542] inconsistent read

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A read that sees a world that never really existed as one coherent moment.

Shadow: misusing inconsistent read at rune 1542 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name inconsistent read when the prompt needs this obligation made explicit: A read that sees a world that never really existed as one coherent moment.
• Ask the assistant to state the inconsistent read shadow before proposing changes.

Example clause:

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

Pocket gloss: A read that sees a world that never really existed as one coherent moment.

113.2.31 [1543] infinite loop

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: infinite loop is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the infinite loop obligation named before work proceeds.

Shadow: misusing infinite loop at rune 1543 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name infinite loop when the prompt needs this obligation made explicit: infinite loop is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the infinite loop obligation named before work proceeds.
• Ask the assistant to state the infinite loop shadow before proposing changes.

Example clause:

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

113.2.32 [1544] invalid state

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: invalid state is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the invalid state obligation named before work proceeds.

Shadow: misusing invalid state at rune 1544 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name invalid state when the prompt needs this obligation made explicit: invalid state is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the invalid state obligation named before work proceeds.
• Ask the assistant to state the invalid state shadow before proposing changes.

Example clause:

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

113.2.33 [1545] jitter spike

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: jitter spike is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the jitter spike obligation named before work proceeds.

Shadow: misusing jitter spike at rune 1545 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name jitter spike when the prompt needs this obligation made explicit: jitter spike is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the jitter spike obligation named before work proceeds.
• Ask the assistant to state the jitter spike shadow before proposing changes.

Example clause:

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

113.2.34 [1546] leak {Curse}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Something escapes the boundary that should have held it: memory, secrets, file descriptors, authority, abstraction, or time.

Shadow: when treating a leak as the cause prevents finding the owner, lifetime, or boundary.

Prompt uses:

• Name leak when the prompt needs this obligation made explicit: Something escapes the boundary that should have held it: memory, secrets, file descriptors, authority, abstraction, or time.
• Ask the assistant to state the leak shadow before proposing changes.

Example clause:

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

Pocket gloss: Something escapes the boundary that should have held it.

113.2.35 [1547] livelock

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Everyone keeps moving but nobody makes progress.

Shadow: misusing livelock at rune 1547 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name livelock when the prompt needs this obligation made explicit: Everyone keeps moving but nobody makes progress.
• Ask the assistant to state the livelock shadow before proposing changes.

Example clause:

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

Pocket gloss: Everyone keeps moving but nobody makes progress.

113.2.36 [1548] lost update

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: One writer quietly stomps another writer’s valid change.

Shadow: misusing lost update at rune 1548 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name lost update when the prompt needs this obligation made explicit: One writer quietly stomps another writer’s valid change.
• Ask the assistant to state the lost update shadow before proposing changes.

Example clause:

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

Pocket gloss: One writer quietly stomps another writer’s valid change.

113.2.37 [1549] memory corruption

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: memory corruption is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the memory corruption obligation named before work proceeds.

Shadow: misusing memory corruption at rune 1549 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name memory corruption when the prompt needs this obligation made explicit: memory corruption is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the memory corruption obligation named before work proceeds.
• Ask the assistant to state the memory corruption shadow before proposing changes.

Example clause:

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

113.2.38 [1550] mismatch

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: mismatch is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the mismatch obligation named before work proceeds.

Shadow: misusing mismatch at rune 1550 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name mismatch when the prompt needs this obligation made explicit: mismatch is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the mismatch obligation named before work proceeds.
• Ask the assistant to state the mismatch shadow before proposing changes.

Example clause:

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

113.2.39 [1551] misroute

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: misroute is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the misroute obligation named before work proceeds.

Shadow: misusing misroute at rune 1551 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name misroute when the prompt needs this obligation made explicit: misroute is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the misroute obligation named before work proceeds.
• Ask the assistant to state the misroute shadow before proposing changes.

Example clause:

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

113.2.40 [1552] missed heartbeat

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: missed heartbeat is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the missed heartbeat obligation named before work proceeds.

Shadow: misusing missed heartbeat at rune 1552 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name missed heartbeat when the prompt needs this obligation made explicit: missed heartbeat is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the missed heartbeat obligation named before work proceeds.
• Ask the assistant to state the missed heartbeat shadow before proposing changes.

Example clause:

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

113.2.41 [1553] null dereference

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: null dereference is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the null dereference obligation named before work proceeds.

Shadow: misusing null dereference at rune 1553 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name null dereference when the prompt needs this obligation made explicit: null dereference is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the null dereference obligation named before work proceeds.
• Ask the assistant to state the null dereference shadow before proposing changes.

Example clause:

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

113.2.42 [1554] outage

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Service unavailable where availability was expected.

Shadow: misusing outage at rune 1554 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name outage when the prompt needs this obligation made explicit: Service unavailable where availability was expected.
• Ask the assistant to state the outage shadow before proposing changes.

Example clause:

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

Pocket gloss: Service unavailable where availability was expected.

113.2.43 [1555] overflow

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Value exceeds the representable range.

Shadow: misusing overflow at rune 1555 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name overflow when the prompt needs this obligation made explicit: Value exceeds the representable range.
• Ask the assistant to state the overflow shadow before proposing changes.

Example clause:

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

Pocket gloss: Value exceeds the representable range.

113.2.44 [1556] packet loss {Curse}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: packet loss in its Curse sense is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the packet loss obligation named before work proceeds.

Shadow: misusing packet loss at rune 1556 in the Curse lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name packet loss when the prompt needs this obligation made explicit: packet loss in its Curse sense is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the packet loss obligation named before work proceeds.
• Ask the assistant to state the packet loss shadow before proposing changes.

Example clause:

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

113.2.45 [1557] panic

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: panic is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the panic obligation named before work proceeds.

Shadow: misusing panic at rune 1557 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name panic when the prompt needs this obligation made explicit: panic is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the panic obligation named before work proceeds.
• Ask the assistant to state the panic shadow before proposing changes.

Example clause:

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

113.2.46 [1558] partial failure

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Some of the system failed while the rest kept limping.

Shadow: misusing partial failure at rune 1558 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name partial failure when the prompt needs this obligation made explicit: Some of the system failed while the rest kept limping.
• Ask the assistant to state the partial failure shadow before proposing changes.

Example clause:

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

Pocket gloss: Some of the system failed while the rest kept limping.

113.2.47 [1559] partition storm

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: partition storm is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the partition storm obligation named before work proceeds.

Shadow: misusing partition storm at rune 1559 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name partition storm when the prompt needs this obligation made explicit: partition storm is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the partition storm obligation named before work proceeds.
• Ask the assistant to state the partition storm shadow before proposing changes.

Example clause:

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

113.2.48 [1560] poison pill

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: poison pill is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the poison pill obligation named before work proceeds.

Shadow: misusing poison pill at rune 1560 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name poison pill when the prompt needs this obligation made explicit: poison pill is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the poison pill obligation named before work proceeds.
• Ask the assistant to state the poison pill shadow before proposing changes.

Example clause:

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

113.2.49 [1561] race

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: An ordering curse: outcomes depend on timing you do not actually control. Name the race and the system becomes debuggable again.

Shadow: when the race is patched locally while the shared state contract remains undefined.

Prompt uses:

• Name race when the prompt needs this obligation made explicit: An ordering curse: outcomes depend on timing you do not actually control. Name the race and the system becomes debuggable again.
• Ask the assistant to state the race shadow before proposing changes.

Example clause:

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

Pocket gloss: Outcome depends on timing you do not actually control.

113.2.50 [1562] regression

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A previously solved bug or quality loss has returned.

Shadow: misusing regression at rune 1562 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name regression when the prompt needs this obligation made explicit: A previously solved bug or quality loss has returned.
• Ask the assistant to state the regression shadow before proposing changes.

Example clause:

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

Pocket gloss: A previously solved bug or quality loss has returned.

113.2.51 [1563] resource starvation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: resource starvation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the resource starvation obligation named before work proceeds.

Shadow: misusing resource starvation at rune 1563 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name resource starvation when the prompt needs this obligation made explicit: resource starvation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the resource starvation obligation named before work proceeds.
• Ask the assistant to state the resource starvation shadow before proposing changes.

Example clause:

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

113.2.52 [1564] retry storm

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Recovery logic amplifying failure instead of containing it. Unguided retries can turn a partial outage into a self-made siege.

Shadow: when retries synchronize into an outage amplifier rather than a recovery path.

Prompt uses:

• Name retry storm when the prompt needs this obligation made explicit: Recovery logic amplifying failure instead of containing it. Unguided retries can turn a partial outage into a self-made siege.
• Ask the assistant to state the retry storm shadow before proposing changes.

Example clause:

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

Pocket gloss: Recovery logic amplifying failure instead of containing it.

113.2.53 [1565] rollback failure

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: rollback failure is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the rollback failure obligation named before work proceeds.

Shadow: misusing rollback failure at rune 1565 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name rollback failure when the prompt needs this obligation made explicit: rollback failure is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the rollback failure obligation named before work proceeds.
• Ask the assistant to state the rollback failure shadow before proposing changes.

Example clause:

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

113.2.54 [1566] saturation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: saturation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the saturation obligation named before work proceeds.

Shadow: misusing saturation at rune 1566 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name saturation when the prompt needs this obligation made explicit: saturation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the saturation obligation named before work proceeds.
• Ask the assistant to state the saturation shadow before proposing changes.

Example clause:

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

113.2.55 [1567] schema drift

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: The stored world and the assumed world have silently stopped matching. This is how migrations keep hurting after everyone thinks they are done.

Shadow: when schema changes are shipped without compatibility checks, migration windows, or readers.

Prompt uses:

• Name schema drift when the prompt needs this obligation made explicit: The stored world and the assumed world have silently stopped matching. This is how migrations keep hurting after everyone thinks they are done.
• Ask the assistant to state the schema drift shadow before proposing changes.

Example clause:

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

Pocket gloss: Stored shape and assumed shape have silently diverged.

113.2.56 [1568] split-brain {Curse}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Separated leaders each believe they are authoritative.

Shadow: misusing split-brain at rune 1568 in the Curse lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name split-brain when the prompt needs this obligation made explicit: Separated leaders each believe they are authoritative.
• Ask the assistant to state the split-brain shadow before proposing changes.

Example clause:

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

Pocket gloss: Separated leaders each believe they are authoritative.

113.2.57 [1569] stack overflow

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stack overflow is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the stack overflow obligation named before work proceeds.

Shadow: misusing stack overflow at rune 1569 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name stack overflow when the prompt needs this obligation made explicit: stack overflow is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the stack overflow obligation named before work proceeds.
• Ask the assistant to state the stack overflow shadow before proposing changes.

Example clause:

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

113.2.58 [1570] stale read

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stale read is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the stale read obligation named before work proceeds.

Shadow: misusing stale read at rune 1570 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name stale read when the prompt needs this obligation made explicit: stale read is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the stale read obligation named before work proceeds.
• Ask the assistant to state the stale read shadow before proposing changes.

Example clause:

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

113.2.59 [1571] stall

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stall is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the stall obligation named before work proceeds.

Shadow: misusing stall at rune 1571 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name stall when the prompt needs this obligation made explicit: stall is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the stall obligation named before work proceeds.
• Ask the assistant to state the stall shadow before proposing changes.

Example clause:

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

113.2.60 [1572] starvation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: starvation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the starvation obligation named before work proceeds.

Shadow: misusing starvation at rune 1572 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name starvation when the prompt needs this obligation made explicit: starvation is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the starvation obligation named before work proceeds.
• Ask the assistant to state the starvation shadow before proposing changes.

Example clause:

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

113.2.61 [1573] state explosion

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: state explosion is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the state explosion obligation named before work proceeds.

Shadow: misusing state explosion at rune 1573 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name state explosion when the prompt needs this obligation made explicit: state explosion is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the state explosion obligation named before work proceeds.
• Ask the assistant to state the state explosion shadow before proposing changes.

Example clause:

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

113.2.62 [1574] storm

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: storm is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the storm obligation named before work proceeds.

Shadow: misusing storm at rune 1574 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name storm when the prompt needs this obligation made explicit: storm is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the storm obligation named before work proceeds.
• Ask the assistant to state the storm shadow before proposing changes.

Example clause:

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

113.2.63 [1575] thrash

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: thrash is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the thrash obligation named before work proceeds.

Shadow: misusing thrash at rune 1575 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name thrash when the prompt needs this obligation made explicit: thrash is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the thrash obligation named before work proceeds.
• Ask the assistant to state the thrash shadow before proposing changes.

Example clause:

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

113.2.64 [1576] timeout {Curse}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: timeout in its Curse sense is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the timeout obligation named before work proceeds.

Shadow: misusing timeout at rune 1576 in the Curse lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name timeout when the prompt needs this obligation made explicit: timeout in its Curse sense is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the timeout obligation named before work proceeds.
• Ask the assistant to state the timeout shadow before proposing changes.

Example clause:

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

113.2.65 [1577] torn write

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: torn write is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the torn write obligation named before work proceeds.

Shadow: misusing torn write at rune 1577 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name torn write when the prompt needs this obligation made explicit: torn write is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the torn write obligation named before work proceeds.
• Ask the assistant to state the torn write shadow before proposing changes.

Example clause:

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

113.2.66 [1578] underflow

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: underflow is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the underflow obligation named before work proceeds.

Shadow: misusing underflow at rune 1578 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name underflow when the prompt needs this obligation made explicit: underflow is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the underflow obligation named before work proceeds.
• Ask the assistant to state the underflow shadow before proposing changes.

Example clause:

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

113.2.67 [1579] unhandled exception

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: unhandled exception is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the unhandled exception obligation named before work proceeds.

Shadow: misusing unhandled exception at rune 1579 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name unhandled exception when the prompt needs this obligation made explicit: unhandled exception is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the unhandled exception obligation named before work proceeds.
• Ask the assistant to state the unhandled exception shadow before proposing changes.

Example clause:

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

113.2.68 [1580] unstable equilibrium

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: unstable equilibrium is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the unstable equilibrium obligation named before work proceeds.

Shadow: misusing unstable equilibrium at rune 1580 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name unstable equilibrium when the prompt needs this obligation made explicit: unstable equilibrium is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the unstable equilibrium obligation named before work proceeds.
• Ask the assistant to state the unstable equilibrium shadow before proposing changes.

Example clause:

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

113.2.69 [1581] write amplification

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: write amplification is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the write amplification obligation named before work proceeds.

Shadow: misusing write amplification at rune 1581 in the failure lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name write amplification when the prompt needs this obligation made explicit: write amplification is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the write amplification obligation named before work proceeds.
• Ask the assistant to state the write amplification shadow before proposing changes.

Example clause:

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

113.2.70 [1582] write skew {Curse}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: write skew in its Curse sense is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the write skew obligation named before work proceeds.

Shadow: misusing write skew at rune 1582 in the Curse lane can let early naming can freeze investigation around a symptom; verify by requiring the caster to state the evidence, rejected alternatives, and repair boundary.

Prompt uses:

• Name write skew when the prompt needs this obligation made explicit: write skew in its Curse sense is a failure analysis and counter-spells rune for name failure mechanisms without confusing symptom for cause; use it when the artifact needs the write skew obligation named before work proceeds.
• Ask the assistant to state the write skew shadow before proposing changes.

Example clause:

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