107  Testing, Verification, and Observability

108 Testing, Verification, and Observability

Range: 1140-1210.

108.1 Completion

Status	Count
authored	71

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

Sigil	Term	Completion	Semantic	Summary
1140	acceptance test	authored	generated_draft	acceptance test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the acceptance test obligation named before work proceeds.
1141	alert	authored	reviewed	A threshold that wakes humans or automation when evidence crosses concern.
1142	assertion {Proof}	authored	generated_draft	assertion in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the assertion obligation named before work proceeds.
1143	audit log	authored	generated_draft	audit log is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the audit log obligation named before work proceeds.
1144	backtrace	authored	generated_draft	backtrace is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the backtrace obligation named before work proceeds.
1145	baseline {Proof}	authored	generated_draft	baseline in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the baseline obligation named before work proceeds.
1146	benchmark	authored	reviewed	A performance claim forced to meet measurement. Benchmarks are where speed rhetoric either cashes out or dies.
1147	black-box test	authored	generated_draft	black-box test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the black-box test obligation named before work proceeds.
1148	canary check	authored	generated_draft	canary check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the canary check obligation named before work proceeds.
1149	check	authored	generated_draft	check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the check obligation named before work proceeds.
1150	code coverage	authored	generated_draft	code coverage is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the code coverage obligation named before work proceeds.
1151	conformance	authored	generated_draft	conformance is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the conformance obligation named before work proceeds.
1152	contract test	authored	reviewed	A promise checked at the seam between systems. Use it when mocks are too flattering and end-to-end tests are too blunt.
1153	core dump {Proof}	authored	generated_draft	core dump in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the core dump obligation named before work proceeds.
1154	counter {Proof}	authored	generated_draft	counter in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the counter obligation named before work proceeds.
1155	dashboard	authored	generated_draft	dashboard is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the dashboard obligation named before work proceeds.
1156	debugger	authored	generated_draft	debugger is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the debugger obligation named before work proceeds.
1157	diagnostic	authored	generated_draft	diagnostic is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the diagnostic obligation named before work proceeds.
1158	error budget	authored	generated_draft	error budget is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the error budget obligation named before work proceeds.
1159	evaluation {Proof}	authored	generated_draft	evaluation in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the evaluation obligation named before work proceeds.
1160	expectation	authored	generated_draft	expectation is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the expectation obligation named before work proceeds.
1161	fixture	authored	generated_draft	fixture is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the fixture obligation named before work proceeds.
1162	flame graph	authored	generated_draft	flame graph is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the flame graph obligation named before work proceeds.
1163	fuzzing	authored	reviewed	Throw weird inputs at the system until hidden assumptions break.
1164	gauge	authored	generated_draft	gauge is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the gauge obligation named before work proceeds.
1165	golden test	authored	generated_draft	golden test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the golden test obligation named before work proceeds.
1166	harness	authored	generated_draft	harness is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the harness obligation named before work proceeds.
1167	health probe	authored	generated_draft	health probe is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the health probe obligation named before work proceeds.
1168	histogram	authored	generated_draft	histogram is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the histogram obligation named before work proceeds.
1169	hypothesis	authored	generated_draft	hypothesis is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the hypothesis obligation named before work proceeds.
1170	incident report	authored	generated_draft	incident report is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the incident report obligation named before work proceeds.
1171	integration test	authored	reviewed	Test that multiple real parts cooperate correctly together.
1172	invariant	authored	reviewed	A law that must remain true while the rest of the system is allowed to move. If you cannot say the invariant, you probably do not yet understand the change.
1173	load test	authored	generated_draft	load test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the load test obligation named before work proceeds.
1174	log	authored	reviewed	A recorded stream of events or decisions for later reading.
1175	logger	authored	generated_draft	logger is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the logger obligation named before work proceeds.
1176	metric	authored	reviewed	A numeric measure that can be tracked over time.
1177	mock	authored	generated_draft	mock is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the mock obligation named before work proceeds.
1178	model check	authored	generated_draft	model check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the model check obligation named before work proceeds.
1179	monitor	authored	generated_draft	monitor is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the monitor obligation named before work proceeds.
1180	observability	authored	reviewed	Enough internal evidence exists that you can infer what the system is doing from the outside. Not logs alone: legible state under pressure.
1181	oracle	authored	generated_draft	oracle is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the oracle obligation named before work proceeds.
1182	postcondition	authored	generated_draft	postcondition is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the postcondition obligation named before work proceeds.
1183	precondition	authored	generated_draft	precondition is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the precondition obligation named before work proceeds.
1184	profiler	authored	reviewed	A measurement tool that reveals where time or allocation is being spent.
1185	proof	authored	generated_draft	proof is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the proof obligation named before work proceeds.
1186	property-based test	authored	reviewed	Instead of checking one remembered example, ask whether a law survives many generated cases. Use it when you care more about the invariant than the anecdote.
1187	regression test	authored	reviewed	A test written so yesterday’s bug does not return tomorrow.
1188	replay	authored	generated_draft	replay is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the replay obligation named before work proceeds.
1189	sampling	authored	generated_draft	sampling is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the sampling obligation named before work proceeds.
1190	sanity check	authored	generated_draft	sanity check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the sanity check obligation named before work proceeds.
1191	simulation	authored	generated_draft	simulation is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the simulation obligation named before work proceeds.
1192	smoke test	authored	reviewed	A fast confidence check that the basic path still breathes.
1193	snapshot test	authored	generated_draft	snapshot test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the snapshot test obligation named before work proceeds.
1194	soak test	authored	generated_draft	soak test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the soak test obligation named before work proceeds.
1195	solver	authored	generated_draft	solver is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the solver obligation named before work proceeds.
1196	span	authored	generated_draft	span is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the span obligation named before work proceeds.
1197	stack trace	authored	generated_draft	stack trace is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the stack trace obligation named before work proceeds.
1198	static checker	authored	generated_draft	static checker is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the static checker obligation named before work proceeds.
1199	stress test	authored	generated_draft	stress test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the stress test obligation named before work proceeds.
1200	stub	authored	generated_draft	stub is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the stub obligation named before work proceeds.
1201	symbolic execution	authored	generated_draft	symbolic execution is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the symbolic execution obligation named before work proceeds.
1202	telemetry	authored	reviewed	Measurements leaving the system in a form other systems can compare, store, and alert on. Shadow: metric exhaust without explanatory power.
1203	theorem {Proof}	authored	generated_draft	theorem in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the theorem obligation named before work proceeds.
1204	trace {Proof}	authored	reviewed	A preserved path through execution. Use it when the question is not only what failed, but where the causal thread first bent.
1205	tracer	authored	generated_draft	tracer is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the tracer obligation named before work proceeds.
1206	triage	authored	generated_draft	triage is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the triage obligation named before work proceeds.
1207	unit test	authored	reviewed	Test the smallest meaningful unit in isolation.
1208	validation	authored	generated_draft	validation is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the validation obligation named before work proceeds.
1209	verifier	authored	generated_draft	verifier is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the verifier obligation named before work proceeds.
1210	white-box test	authored	generated_draft	white-box test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the white-box test obligation named before work proceeds.

108.2 Entries

108.2.1 [1140] acceptance test

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: acceptance test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the acceptance test obligation named before work proceeds.

Shadow: misusing acceptance test at rune 1140 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name acceptance test when the prompt needs this obligation made explicit: acceptance test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the acceptance test obligation named before work proceeds.
• Ask the assistant to state the acceptance test shadow before proposing changes.

Example clause:

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

108.2.2 [1141] alert

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A threshold that wakes humans or automation when evidence crosses concern.

Shadow: misusing alert at rune 1141 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name alert when the prompt needs this obligation made explicit: A threshold that wakes humans or automation when evidence crosses concern.
• Ask the assistant to state the alert shadow before proposing changes.

Example clause:

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

Pocket gloss: A threshold that wakes humans or automation when evidence crosses concern.

108.2.3 [1142] assertion {Proof}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: assertion in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the assertion obligation named before work proceeds.

Shadow: misusing assertion at rune 1142 in the Proof lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name assertion when the prompt needs this obligation made explicit: assertion in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the assertion obligation named before work proceeds.
• Ask the assistant to state the assertion shadow before proposing changes.

Example clause:

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

108.2.4 [1143] audit log

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: audit log is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the audit log obligation named before work proceeds.

Shadow: misusing audit log at rune 1143 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name audit log when the prompt needs this obligation made explicit: audit log is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the audit log obligation named before work proceeds.
• Ask the assistant to state the audit log shadow before proposing changes.

Example clause:

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

108.2.5 [1144] backtrace

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: backtrace is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the backtrace obligation named before work proceeds.

Shadow: misusing backtrace at rune 1144 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name backtrace when the prompt needs this obligation made explicit: backtrace is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the backtrace obligation named before work proceeds.
• Ask the assistant to state the backtrace shadow before proposing changes.

Example clause:

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

108.2.6 [1145] baseline {Proof}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: baseline in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the baseline obligation named before work proceeds.

Shadow: misusing baseline at rune 1145 in the Proof lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name baseline when the prompt needs this obligation made explicit: baseline in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the baseline obligation named before work proceeds.
• Ask the assistant to state the baseline shadow before proposing changes.

Example clause:

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

108.2.7 [1146] benchmark

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A performance claim forced to meet measurement. Benchmarks are where speed rhetoric either cashes out or dies.

Shadow: when a benchmark optimizes the measured path and neglects the production path.

Prompt uses:

• Name benchmark when the prompt needs this obligation made explicit: A performance claim forced to meet measurement. Benchmarks are where speed rhetoric either cashes out or dies.
• Ask the assistant to state the benchmark shadow before proposing changes.

Example clause:

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

Pocket gloss: Force a performance claim to meet measurement.

108.2.8 [1147] black-box test

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: black-box test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the black-box test obligation named before work proceeds.

Shadow: misusing black-box test at rune 1147 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name black-box test when the prompt needs this obligation made explicit: black-box test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the black-box test obligation named before work proceeds.
• Ask the assistant to state the black-box test shadow before proposing changes.

Example clause:

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

108.2.9 [1148] canary check

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: canary check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the canary check obligation named before work proceeds.

Shadow: misusing canary check at rune 1148 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name canary check when the prompt needs this obligation made explicit: canary check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the canary check obligation named before work proceeds.
• Ask the assistant to state the canary check shadow before proposing changes.

Example clause:

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

108.2.10 [1149] check

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the check obligation named before work proceeds.

Shadow: misusing check at rune 1149 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name check when the prompt needs this obligation made explicit: check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the check obligation named before work proceeds.
• Ask the assistant to state the check shadow before proposing changes.

Example clause:

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

108.2.11 [1150] code coverage

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: code coverage is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the code coverage obligation named before work proceeds.

Shadow: misusing code coverage at rune 1150 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name code coverage when the prompt needs this obligation made explicit: code coverage is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the code coverage obligation named before work proceeds.
• Ask the assistant to state the code coverage shadow before proposing changes.

Example clause:

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

108.2.12 [1151] conformance

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: conformance is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the conformance obligation named before work proceeds.

Shadow: misusing conformance at rune 1151 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name conformance when the prompt needs this obligation made explicit: conformance is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the conformance obligation named before work proceeds.
• Ask the assistant to state the conformance shadow before proposing changes.

Example clause:

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

108.2.13 [1152] contract test

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A promise checked at the seam between systems. Use it when mocks are too flattering and end-to-end tests are too blunt.

Shadow: when the contract test freezes provider quirks instead of public obligations.

Prompt uses:

• Name contract test when the prompt needs this obligation made explicit: A promise checked at the seam between systems. Use it when mocks are too flattering and end-to-end tests are too blunt.
• Ask the assistant to state the contract test shadow before proposing changes.

Example clause:

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

Pocket gloss: A promise checked at the seam between systems.

108.2.14 [1153] core dump {Proof}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: core dump in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the core dump obligation named before work proceeds.

Shadow: misusing core dump at rune 1153 in the Proof lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name core dump when the prompt needs this obligation made explicit: core dump in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the core dump obligation named before work proceeds.
• Ask the assistant to state the core dump shadow before proposing changes.

Example clause:

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

108.2.15 [1154] counter {Proof}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: counter in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the counter obligation named before work proceeds.

Shadow: misusing counter at rune 1154 in the Proof lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name counter when the prompt needs this obligation made explicit: counter in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the counter obligation named before work proceeds.
• Ask the assistant to state the counter shadow before proposing changes.

Example clause:

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

108.2.16 [1155] dashboard

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: dashboard is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the dashboard obligation named before work proceeds.

Shadow: misusing dashboard at rune 1155 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name dashboard when the prompt needs this obligation made explicit: dashboard is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the dashboard obligation named before work proceeds.
• Ask the assistant to state the dashboard shadow before proposing changes.

Example clause:

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

108.2.17 [1156] debugger

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: debugger is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the debugger obligation named before work proceeds.

Shadow: misusing debugger at rune 1156 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name debugger when the prompt needs this obligation made explicit: debugger is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the debugger obligation named before work proceeds.
• Ask the assistant to state the debugger shadow before proposing changes.

Example clause:

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

108.2.18 [1157] diagnostic

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: diagnostic is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the diagnostic obligation named before work proceeds.

Shadow: misusing diagnostic at rune 1157 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name diagnostic when the prompt needs this obligation made explicit: diagnostic is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the diagnostic obligation named before work proceeds.
• Ask the assistant to state the diagnostic shadow before proposing changes.

Example clause:

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

108.2.19 [1158] error budget

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: error budget is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the error budget obligation named before work proceeds.

Shadow: misusing error budget at rune 1158 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name error budget when the prompt needs this obligation made explicit: error budget is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the error budget obligation named before work proceeds.
• Ask the assistant to state the error budget shadow before proposing changes.

Example clause:

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

108.2.20 [1159] evaluation {Proof}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: evaluation in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the evaluation obligation named before work proceeds.

Shadow: misusing evaluation at rune 1159 in the Proof lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name evaluation when the prompt needs this obligation made explicit: evaluation in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the evaluation obligation named before work proceeds.
• Ask the assistant to state the evaluation shadow before proposing changes.

Example clause:

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

108.2.21 [1160] expectation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: expectation is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the expectation obligation named before work proceeds.

Shadow: misusing expectation at rune 1160 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name expectation when the prompt needs this obligation made explicit: expectation is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the expectation obligation named before work proceeds.
• Ask the assistant to state the expectation shadow before proposing changes.

Example clause:

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

108.2.22 [1161] fixture

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fixture is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the fixture obligation named before work proceeds.

Shadow: misusing fixture at rune 1161 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name fixture when the prompt needs this obligation made explicit: fixture is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the fixture obligation named before work proceeds.
• Ask the assistant to state the fixture shadow before proposing changes.

Example clause:

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

108.2.23 [1162] flame graph

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: flame graph is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the flame graph obligation named before work proceeds.

Shadow: misusing flame graph at rune 1162 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name flame graph when the prompt needs this obligation made explicit: flame graph is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the flame graph obligation named before work proceeds.
• Ask the assistant to state the flame graph shadow before proposing changes.

Example clause:

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

108.2.24 [1163] fuzzing

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Throw weird inputs at the system until hidden assumptions break.

Shadow: misusing fuzzing at rune 1163 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name fuzzing when the prompt needs this obligation made explicit: Throw weird inputs at the system until hidden assumptions break.
• Ask the assistant to state the fuzzing shadow before proposing changes.

Example clause:

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

Pocket gloss: Throw weird inputs at the system until hidden assumptions break.

108.2.25 [1164] gauge

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: gauge is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the gauge obligation named before work proceeds.

Shadow: misusing gauge at rune 1164 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name gauge when the prompt needs this obligation made explicit: gauge is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the gauge obligation named before work proceeds.
• Ask the assistant to state the gauge shadow before proposing changes.

Example clause:

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

108.2.26 [1165] golden test

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: golden test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the golden test obligation named before work proceeds.

Shadow: misusing golden test at rune 1165 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name golden test when the prompt needs this obligation made explicit: golden test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the golden test obligation named before work proceeds.
• Ask the assistant to state the golden test shadow before proposing changes.

Example clause:

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

108.2.27 [1166] harness

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: harness is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the harness obligation named before work proceeds.

Shadow: misusing harness at rune 1166 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name harness when the prompt needs this obligation made explicit: harness is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the harness obligation named before work proceeds.
• Ask the assistant to state the harness shadow before proposing changes.

Example clause:

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

108.2.28 [1167] health probe

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: health probe is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the health probe obligation named before work proceeds.

Shadow: misusing health probe at rune 1167 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name health probe when the prompt needs this obligation made explicit: health probe is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the health probe obligation named before work proceeds.
• Ask the assistant to state the health probe shadow before proposing changes.

Example clause:

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

108.2.29 [1168] histogram

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: histogram is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the histogram obligation named before work proceeds.

Shadow: misusing histogram at rune 1168 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name histogram when the prompt needs this obligation made explicit: histogram is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the histogram obligation named before work proceeds.
• Ask the assistant to state the histogram shadow before proposing changes.

Example clause:

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

108.2.30 [1169] hypothesis

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: hypothesis is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the hypothesis obligation named before work proceeds.

Shadow: misusing hypothesis at rune 1169 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name hypothesis when the prompt needs this obligation made explicit: hypothesis is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the hypothesis obligation named before work proceeds.
• Ask the assistant to state the hypothesis shadow before proposing changes.

Example clause:

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

108.2.31 [1170] incident report

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: incident report is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the incident report obligation named before work proceeds.

Shadow: misusing incident report at rune 1170 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name incident report when the prompt needs this obligation made explicit: incident report is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the incident report obligation named before work proceeds.
• Ask the assistant to state the incident report shadow before proposing changes.

Example clause:

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

108.2.32 [1171] integration test

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Test that multiple real parts cooperate correctly together.

Shadow: misusing integration test at rune 1171 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name integration test when the prompt needs this obligation made explicit: Test that multiple real parts cooperate correctly together.
• Ask the assistant to state the integration test shadow before proposing changes.

Example clause:

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

Pocket gloss: Test that multiple real parts cooperate correctly together.

108.2.33 [1172] invariant

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A law that must remain true while the rest of the system is allowed to move. If you cannot say the invariant, you probably do not yet understand the change.

Shadow: when the invariant is asserted in prose but not guarded by checks or tests.

Prompt uses:

• Name invariant when the prompt needs this obligation made explicit: A law that must remain true while the rest of the system is allowed to move. If you cannot say the invariant, you probably do not yet understand the change.
• Ask the assistant to state the invariant shadow before proposing changes.

Example clause:

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

Pocket gloss: A law that must remain true while the rest of the system moves.

108.2.34 [1173] load test

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: load test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the load test obligation named before work proceeds.

Shadow: misusing load test at rune 1173 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name load test when the prompt needs this obligation made explicit: load test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the load test obligation named before work proceeds.
• Ask the assistant to state the load test shadow before proposing changes.

Example clause:

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

108.2.35 [1174] log

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A recorded stream of events or decisions for later reading.

Shadow: misusing log at rune 1174 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name log when the prompt needs this obligation made explicit: A recorded stream of events or decisions for later reading.
• Ask the assistant to state the log shadow before proposing changes.

Example clause:

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

Pocket gloss: A recorded stream of events or decisions for later reading.

108.2.36 [1175] logger

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: logger is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the logger obligation named before work proceeds.

Shadow: misusing logger at rune 1175 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name logger when the prompt needs this obligation made explicit: logger is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the logger obligation named before work proceeds.
• Ask the assistant to state the logger shadow before proposing changes.

Example clause:

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

108.2.37 [1176] metric

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A numeric measure that can be tracked over time.

Shadow: misusing metric at rune 1176 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name metric when the prompt needs this obligation made explicit: A numeric measure that can be tracked over time.
• Ask the assistant to state the metric shadow before proposing changes.

Example clause:

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

Pocket gloss: A numeric measure that can be tracked over time.

108.2.38 [1177] mock

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: mock is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the mock obligation named before work proceeds.

Shadow: misusing mock at rune 1177 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name mock when the prompt needs this obligation made explicit: mock is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the mock obligation named before work proceeds.
• Ask the assistant to state the mock shadow before proposing changes.

Example clause:

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

108.2.39 [1178] model check

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: model check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the model check obligation named before work proceeds.

Shadow: misusing model check at rune 1178 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name model check when the prompt needs this obligation made explicit: model check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the model check obligation named before work proceeds.
• Ask the assistant to state the model check shadow before proposing changes.

Example clause:

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

108.2.40 [1179] monitor

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: monitor is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the monitor obligation named before work proceeds.

Shadow: misusing monitor at rune 1179 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name monitor when the prompt needs this obligation made explicit: monitor is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the monitor obligation named before work proceeds.
• Ask the assistant to state the monitor shadow before proposing changes.

Example clause:

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

108.2.41 [1180] observability

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Enough internal evidence exists that you can infer what the system is doing from the outside. Not logs alone: legible state under pressure.

Shadow: when observable signals exist but no one can connect them to user impact.

Prompt uses:

• Name observability when the prompt needs this obligation made explicit: Enough internal evidence exists that you can infer what the system is doing from the outside. Not logs alone: legible state under pressure.
• Ask the assistant to state the observability shadow before proposing changes.

Example clause:

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

Pocket gloss: Enough evidence exists to infer what the system is doing from the outside.

108.2.42 [1181] oracle

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: oracle is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the oracle obligation named before work proceeds.

Shadow: misusing oracle at rune 1181 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name oracle when the prompt needs this obligation made explicit: oracle is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the oracle obligation named before work proceeds.
• Ask the assistant to state the oracle shadow before proposing changes.

Example clause:

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

108.2.43 [1182] postcondition

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: postcondition is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the postcondition obligation named before work proceeds.

Shadow: misusing postcondition at rune 1182 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name postcondition when the prompt needs this obligation made explicit: postcondition is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the postcondition obligation named before work proceeds.
• Ask the assistant to state the postcondition shadow before proposing changes.

Example clause:

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

108.2.44 [1183] precondition

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: precondition is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the precondition obligation named before work proceeds.

Shadow: misusing precondition at rune 1183 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name precondition when the prompt needs this obligation made explicit: precondition is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the precondition obligation named before work proceeds.
• Ask the assistant to state the precondition shadow before proposing changes.

Example clause:

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

108.2.45 [1184] profiler

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A measurement tool that reveals where time or allocation is being spent.

Shadow: misusing profiler at rune 1184 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name profiler when the prompt needs this obligation made explicit: A measurement tool that reveals where time or allocation is being spent.
• Ask the assistant to state the profiler shadow before proposing changes.

Example clause:

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

Pocket gloss: A measurement tool that reveals where time or allocation is being spent.

108.2.46 [1185] proof

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: proof is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the proof obligation named before work proceeds.

Shadow: misusing proof at rune 1185 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name proof when the prompt needs this obligation made explicit: proof is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the proof obligation named before work proceeds.
• Ask the assistant to state the proof shadow before proposing changes.

Example clause:

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

108.2.47 [1186] property-based test

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Instead of checking one remembered example, ask whether a law survives many generated cases. Use it when you care more about the invariant than the anecdote.

Shadow: when generated cases explore input space but miss the property users depend on.

Prompt uses:

• Name property-based test when the prompt needs this obligation made explicit: Instead of checking one remembered example, ask whether a law survives many generated cases. Use it when you care more about the invariant than the anecdote.
• Ask the assistant to state the property-based test shadow before proposing changes.

Example clause:

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

Pocket gloss: Test the law across many generated cases instead of one remembered example.

108.2.48 [1187] regression test

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A test written so yesterday’s bug does not return tomorrow.

Shadow: misusing regression test at rune 1187 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name regression test when the prompt needs this obligation made explicit: A test written so yesterday’s bug does not return tomorrow.
• Ask the assistant to state the regression test shadow before proposing changes.

Example clause:

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

Pocket gloss: A test written so yesterday’s bug does not return tomorrow.

108.2.49 [1188] replay

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: replay is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the replay obligation named before work proceeds.

Shadow: misusing replay at rune 1188 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name replay when the prompt needs this obligation made explicit: replay is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the replay obligation named before work proceeds.
• Ask the assistant to state the replay shadow before proposing changes.

Example clause:

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

108.2.50 [1189] sampling

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sampling is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the sampling obligation named before work proceeds.

Shadow: misusing sampling at rune 1189 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name sampling when the prompt needs this obligation made explicit: sampling is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the sampling obligation named before work proceeds.
• Ask the assistant to state the sampling shadow before proposing changes.

Example clause:

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

108.2.51 [1190] sanity check

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sanity check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the sanity check obligation named before work proceeds.

Shadow: misusing sanity check at rune 1190 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name sanity check when the prompt needs this obligation made explicit: sanity check is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the sanity check obligation named before work proceeds.
• Ask the assistant to state the sanity check shadow before proposing changes.

Example clause:

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

108.2.52 [1191] simulation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: simulation is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the simulation obligation named before work proceeds.

Shadow: misusing simulation at rune 1191 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name simulation when the prompt needs this obligation made explicit: simulation is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the simulation obligation named before work proceeds.
• Ask the assistant to state the simulation shadow before proposing changes.

Example clause:

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

108.2.53 [1192] smoke test

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A fast confidence check that the basic path still breathes.

Shadow: misusing smoke test at rune 1192 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name smoke test when the prompt needs this obligation made explicit: A fast confidence check that the basic path still breathes.
• Ask the assistant to state the smoke test shadow before proposing changes.

Example clause:

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

Pocket gloss: A fast confidence check that the basic path still breathes.

108.2.54 [1193] snapshot test

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: snapshot test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the snapshot test obligation named before work proceeds.

Shadow: misusing snapshot test at rune 1193 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name snapshot test when the prompt needs this obligation made explicit: snapshot test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the snapshot test obligation named before work proceeds.
• Ask the assistant to state the snapshot test shadow before proposing changes.

Example clause:

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

108.2.55 [1194] soak test

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: soak test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the soak test obligation named before work proceeds.

Shadow: misusing soak test at rune 1194 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name soak test when the prompt needs this obligation made explicit: soak test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the soak test obligation named before work proceeds.
• Ask the assistant to state the soak test shadow before proposing changes.

Example clause:

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

108.2.56 [1195] solver

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: solver is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the solver obligation named before work proceeds.

Shadow: misusing solver at rune 1195 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name solver when the prompt needs this obligation made explicit: solver is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the solver obligation named before work proceeds.
• Ask the assistant to state the solver shadow before proposing changes.

Example clause:

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

108.2.57 [1196] span

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: span is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the span obligation named before work proceeds.

Shadow: misusing span at rune 1196 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name span when the prompt needs this obligation made explicit: span is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the span obligation named before work proceeds.
• Ask the assistant to state the span shadow before proposing changes.

Example clause:

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

108.2.58 [1197] stack trace

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stack trace is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the stack trace obligation named before work proceeds.

Shadow: misusing stack trace at rune 1197 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name stack trace when the prompt needs this obligation made explicit: stack trace is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the stack trace obligation named before work proceeds.
• Ask the assistant to state the stack trace shadow before proposing changes.

Example clause:

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

108.2.59 [1198] static checker

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: static checker is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the static checker obligation named before work proceeds.

Shadow: misusing static checker at rune 1198 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name static checker when the prompt needs this obligation made explicit: static checker is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the static checker obligation named before work proceeds.
• Ask the assistant to state the static checker shadow before proposing changes.

Example clause:

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

108.2.60 [1199] stress test

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stress test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the stress test obligation named before work proceeds.

Shadow: misusing stress test at rune 1199 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name stress test when the prompt needs this obligation made explicit: stress test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the stress test obligation named before work proceeds.
• Ask the assistant to state the stress test shadow before proposing changes.

Example clause:

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

108.2.61 [1200] stub

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stub is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the stub obligation named before work proceeds.

Shadow: misusing stub at rune 1200 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name stub when the prompt needs this obligation made explicit: stub is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the stub obligation named before work proceeds.
• Ask the assistant to state the stub shadow before proposing changes.

Example clause:

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

108.2.62 [1201] symbolic execution

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: symbolic execution is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the symbolic execution obligation named before work proceeds.

Shadow: misusing symbolic execution at rune 1201 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name symbolic execution when the prompt needs this obligation made explicit: symbolic execution is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the symbolic execution obligation named before work proceeds.
• Ask the assistant to state the symbolic execution shadow before proposing changes.

Example clause:

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

108.2.63 [1202] telemetry

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Measurements leaving the system in a form other systems can compare, store, and alert on.

Shadow: metric exhaust without explanatory power.

Prompt uses:

• Name telemetry when the prompt needs this obligation made explicit: Measurements leaving the system in a form other systems can compare, store, and alert on.
• Ask the assistant to state the telemetry shadow before proposing changes.

Example clause:

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

Pocket gloss: Measurements emitted in a form other systems can store and alert on.

108.2.64 [1203] theorem {Proof}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: theorem in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the theorem obligation named before work proceeds.

Shadow: misusing theorem at rune 1203 in the Proof lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name theorem when the prompt needs this obligation made explicit: theorem in its Proof sense is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the theorem obligation named before work proceeds.
• Ask the assistant to state the theorem shadow before proposing changes.

Example clause:

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

108.2.65 [1204] trace {Proof}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A preserved path through execution. Use it when the question is not only what failed, but where the causal thread first bent.

Shadow: when trace detail becomes noise and the causal path still remains unclear.

Prompt uses:

• Name trace when the prompt needs this obligation made explicit: A preserved path through execution. Use it when the question is not only what failed, but where the causal thread first bent.
• Ask the assistant to state the trace shadow before proposing changes.

Example clause:

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

Pocket gloss: A preserved path through execution.

108.2.66 [1205] tracer

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: tracer is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the tracer obligation named before work proceeds.

Shadow: misusing tracer at rune 1205 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name tracer when the prompt needs this obligation made explicit: tracer is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the tracer obligation named before work proceeds.
• Ask the assistant to state the tracer shadow before proposing changes.

Example clause:

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

108.2.67 [1206] triage

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: triage is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the triage obligation named before work proceeds.

Shadow: misusing triage at rune 1206 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name triage when the prompt needs this obligation made explicit: triage is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the triage obligation named before work proceeds.
• Ask the assistant to state the triage shadow before proposing changes.

Example clause:

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

108.2.68 [1207] unit test

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Test the smallest meaningful unit in isolation.

Shadow: misusing unit test at rune 1207 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name unit test when the prompt needs this obligation made explicit: Test the smallest meaningful unit in isolation.
• Ask the assistant to state the unit test shadow before proposing changes.

Example clause:

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

Pocket gloss: Test the smallest meaningful unit in isolation.

108.2.69 [1208] validation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: validation is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the validation obligation named before work proceeds.

Shadow: misusing validation at rune 1208 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name validation when the prompt needs this obligation made explicit: validation is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the validation obligation named before work proceeds.
• Ask the assistant to state the validation shadow before proposing changes.

Example clause:

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

108.2.70 [1209] verifier

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: verifier is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the verifier obligation named before work proceeds.

Shadow: misusing verifier at rune 1209 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name verifier when the prompt needs this obligation made explicit: verifier is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the verifier obligation named before work proceeds.
• Ask the assistant to state the verifier shadow before proposing changes.

Example clause:

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

108.2.71 [1210] white-box test

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: white-box test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the white-box test obligation named before work proceeds.

Shadow: misusing white-box test at rune 1210 in the verification lane can let passing checks can miss the property users depend on; verify by requiring the caster to state the invariant, signal, threshold, and decision it supports.

Prompt uses:

• Name white-box test when the prompt needs this obligation made explicit: white-box test is a testing and observability rune for turn claims into checks, signals, traces, and reviewable evidence; use it when the artifact needs the white-box test obligation named before work proceeds.
• Ask the assistant to state the white-box test shadow before proposing changes.

Example clause:

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