97  Language, Semantics, and Formal Shape

98 Language, Semantics, and Formal Shape

Range: 0113-0249.

98.1 Completion

Status	Count
authored	137

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

Sigil	Term	Completion	Semantic	Summary
0113	abstract class	authored	reviewed	abstract class names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies abstract class, and the review check that would catch drift.
0114	alias	authored	reviewed	alias names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies alias, and the review check that would catch drift.
0115	annotation	authored	reviewed	annotation names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies annotation, and the review check that would catch drift.
0116	argument	authored	reviewed	argument names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies argument, and the review check that would catch drift.
0117	arity	authored	reviewed	arity names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies arity, and the review check that would catch drift.
0118	assembly	authored	reviewed	assembly names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies assembly, and the review check that would catch drift.
0119	assertion {Lang}	authored	reviewed	assertion (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies assertion, and the review check that would catch drift.
0120	AST	authored	reviewed	The tree form of parsed program structure.
0121	attribute	authored	reviewed	attribute names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies attribute, and the review check that would catch drift.
0122	binding	authored	reviewed	binding names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies binding, and the review check that would catch drift.
0123	borrow {Lang}	authored	reviewed	borrow (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies borrow, and the review check that would catch drift.
0124	borrow checker	authored	reviewed	A checker that enforces safe borrowing and lifetime law before runtime.
0125	bytecode	authored	reviewed	bytecode names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies bytecode, and the review check that would catch drift.
0126	capture	authored	reviewed	capture names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies capture, and the review check that would catch drift.
0127	cast	authored	reviewed	cast names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies cast, and the review check that would catch drift.
0128	class	authored	reviewed	class names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies class, and the review check that would catch drift.
0129	closure	authored	reviewed	closure names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies closure, and the review check that would catch drift.
0130	coercion	authored	reviewed	coercion names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies coercion, and the review check that would catch drift.
0131	comment	authored	reviewed	comment names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies comment, and the review check that would catch drift.
0132	compile-time	authored	reviewed	Known and fixed before execution begins.
0133	compiler	authored	reviewed	The translator from source language to lower-level executable form.
0134	constant	authored	reviewed	constant names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies constant, and the review check that would catch drift.
0135	constraint {Lang}	authored	reviewed	constraint (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies constraint, and the review check that would catch drift.
0136	constructor	authored	reviewed	constructor names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies constructor, and the review check that would catch drift.
0137	contravariance	authored	reviewed	contravariance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies contravariance, and the review check that would catch drift.
0138	covariance	authored	reviewed	covariance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies covariance, and the review check that would catch drift.
0139	currying	authored	reviewed	currying names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies currying, and the review check that would catch drift.
0140	declaration	authored	reviewed	declaration names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies declaration, and the review check that would catch drift.
0141	decorator {Lang}	authored	reviewed	decorator (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies decorator, and the review check that would catch drift.
0142	default	authored	reviewed	default names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies default, and the review check that would catch drift.
0143	definition	authored	reviewed	definition names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies definition, and the review check that would catch drift.
0144	denotation	authored	reviewed	denotation names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies denotation, and the review check that would catch drift.
0145	destructor {Lang}	authored	reviewed	destructor (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies destructor, and the review check that would catch drift.
0146	dispatch {Lang}	authored	reviewed	dispatch (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies dispatch, and the review check that would catch drift.
0147	domain-specific language	authored	reviewed	domain-specific language names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies domain-specific language, and the review check that would catch drift.
0148	dynamic scope	authored	reviewed	dynamic scope names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies dynamic scope, and the review check that would catch drift.
0149	effect	authored	reviewed	effect names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies effect, and the review check that would catch drift.
0150	enum	authored	reviewed	enum names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies enum, and the review check that would catch drift.
0151	evaluation {Lang}	authored	reviewed	evaluation (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies evaluation, and the review check that would catch drift.
0152	export {Lang}	authored	reviewed	export (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies export, and the review check that would catch drift.
0153	expression	authored	reviewed	expression names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies expression, and the review check that would catch drift.
0154	extern	authored	reviewed	extern names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies extern, and the review check that would catch drift.
0155	field {Lang}	authored	reviewed	field (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies field, and the review check that would catch drift.
0156	final	authored	reviewed	final names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies final, and the review check that would catch drift.
0157	function	authored	reviewed	function names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies function, and the review check that would catch drift.
0158	generic {Lang}	authored	reviewed	One definition parameterized over many concrete types or cases.
0159	grammar	authored	reviewed	The rules that say what strings count as well-formed structure.
0160	higher-order function	authored	reviewed	higher-order function names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies higher-order function, and the review check that would catch drift.
0161	identifier	authored	reviewed	identifier names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies identifier, and the review check that would catch drift.
0162	impl	authored	reviewed	impl names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies impl, and the review check that would catch drift.
0163	implementation {Lang}	authored	reviewed	implementation (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies implementation, and the review check that would catch drift.
0164	import	authored	reviewed	import names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies import, and the review check that would catch drift.
0165	include	authored	reviewed	include names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies include, and the review check that would catch drift.
0166	inference	authored	reviewed	Recovering missing type or shape information from surrounding evidence.
0167	inheritance	authored	reviewed	inheritance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies inheritance, and the review check that would catch drift.
0168	inline {Lang}	authored	reviewed	inline (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies inline, and the review check that would catch drift.
0169	instruction {Lang}	authored	reviewed	instruction (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies instruction, and the review check that would catch drift.
0170	interface {Lang}	authored	reviewed	interface (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies interface, and the review check that would catch drift.
0171	interpreter {Lang}	authored	reviewed	A runtime that executes a representation rather than precompiling it away.
0172	IR	authored	reviewed	An internal representation built for analysis and transformation.
0173	keyword	authored	reviewed	keyword names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies keyword, and the review check that would catch drift.
0174	lambda	authored	reviewed	lambda names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies lambda, and the review check that would catch drift.
0175	lexical scope	authored	reviewed	lexical scope names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies lexical scope, and the review check that would catch drift.
0176	lifetime {Lang}	authored	reviewed	lifetime (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies lifetime, and the review check that would catch drift.
0177	linker	authored	reviewed	The binder that turns compiled pieces into one loadable whole.
0178	literal	authored	reviewed	literal names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies literal, and the review check that would catch drift.
0179	loader	authored	reviewed	loader names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies loader, and the review check that would catch drift.
0180	macro	authored	reviewed	Code that writes or reshapes code.
0181	metaprogramming	authored	reviewed	metaprogramming names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies metaprogramming, and the review check that would catch drift.
0182	method	authored	reviewed	method names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies method, and the review check that would catch drift.
0183	mixin	authored	reviewed	mixin names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mixin, and the review check that would catch drift.
0184	module {Lang}	authored	reviewed	module (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies module, and the review check that would catch drift.
0185	monomorphization	authored	reviewed	monomorphization names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies monomorphization, and the review check that would catch drift.
0186	mutability	authored	reviewed	mutability names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mutability, and the review check that would catch drift.
0187	name resolution	authored	reviewed	name resolution names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies name resolution, and the review check that would catch drift.
0188	namespace {Lang}	authored	reviewed	A naming region that prevents collisions and clarifies ownership.
0189	object	authored	reviewed	object names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies object, and the review check that would catch drift.
0190	opcode {Lang}	authored	reviewed	opcode (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies opcode, and the review check that would catch drift.
0191	overload	authored	reviewed	overload names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies overload, and the review check that would catch drift.
0192	override	authored	reviewed	override names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies override, and the review check that would catch drift.
0193	ownership	authored	reviewed	ownership names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies ownership, and the review check that would catch drift.
0194	package {Lang}	authored	reviewed	package (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies package, and the review check that would catch drift.
0195	parameter	authored	reviewed	parameter names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies parameter, and the review check that would catch drift.
0196	parametric polymorphism	authored	reviewed	parametric polymorphism names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies parametric polymorphism, and the review check that would catch drift.
0197	parser	authored	reviewed	The mechanism that turns surface text into structured meaning.
0198	pattern	authored	reviewed	pattern names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies pattern, and the review check that would catch drift.
0199	pattern matching	authored	reviewed	pattern matching names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies pattern matching, and the review check that would catch drift.
0200	polymorphism	authored	reviewed	One interface, many concrete behaviors.
0201	procedure {Lang}	authored	reviewed	procedure (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies procedure, and the review check that would catch drift.
0202	program	authored	reviewed	program names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies program, and the review check that would catch drift.
0203	property {Lang}	authored	reviewed	property (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies property, and the review check that would catch drift.
0204	protected	authored	reviewed	protected names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies protected, and the review check that would catch drift.
0205	public	authored	reviewed	public names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies public, and the review check that would catch drift.
0206	purity	authored	reviewed	purity names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies purity, and the review check that would catch drift.
0207	qualified name	authored	reviewed	qualified name names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies qualified name, and the review check that would catch drift.
0208	readonly	authored	reviewed	readonly names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies readonly, and the review check that would catch drift.
0209	record {Lang}	authored	reviewed	record (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies record, and the review check that would catch drift.
0210	reference {Lang}	authored	reviewed	reference (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies reference, and the review check that would catch drift.
0211	referential transparency	authored	reviewed	referential transparency names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies referential transparency, and the review check that would catch drift.
0212	reflection	authored	reviewed	reflection names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies reflection, and the review check that would catch drift.
0213	resolution	authored	reviewed	resolution names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies resolution, and the review check that would catch drift.
0214	return type	authored	reviewed	return type names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies return type, and the review check that would catch drift.
0215	runtime type	authored	reviewed	runtime type names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies runtime type, and the review check that would catch drift.
0216	scope {Lang}	authored	reviewed	scope (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies scope, and the review check that would catch drift.
0217	sealed	authored	reviewed	sealed names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies sealed, and the review check that would catch drift.
0218	semantics	authored	reviewed	What a program means, not just how it is spelled.
0219	signature {Lang}	authored	reviewed	signature (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies signature, and the review check that would catch drift.
0220	source code	authored	reviewed	source code names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies source code, and the review check that would catch drift.
0221	specialization	authored	reviewed	specialization names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies specialization, and the review check that would catch drift.
0222	statement	authored	reviewed	statement names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies statement, and the review check that would catch drift.
0223	static dispatch	authored	reviewed	static dispatch names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies static dispatch, and the review check that would catch drift.
0224	strictness	authored	reviewed	strictness names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies strictness, and the review check that would catch drift.
0225	struct {Lang}	authored	reviewed	struct (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies struct, and the review check that would catch drift.
0226	subtype	authored	reviewed	subtype names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies subtype, and the review check that would catch drift.
0227	supertype	authored	reviewed	supertype names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies supertype, and the review check that would catch drift.
0228	symbol	authored	reviewed	symbol names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies symbol, and the review check that would catch drift.
0229	syntax	authored	reviewed	The legal surface form of the language.
0230	template {Lang}	authored	reviewed	template (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies template, and the review check that would catch drift.
0231	theorem {Lang}	authored	reviewed	theorem (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies theorem, and the review check that would catch drift.
0232	token {Lang}	authored	reviewed	token (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies token, and the review check that would catch drift.
0233	trait	authored	reviewed	trait names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies trait, and the review check that would catch drift.
0234	transpiler	authored	reviewed	transpiler names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies transpiler, and the review check that would catch drift.
0235	tuple {Lang}	authored	reviewed	tuple (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies tuple, and the review check that would catch drift.
0236	type	authored	reviewed	A declared or inferred class of values and allowed operations.
0237	type alias	authored	reviewed	type alias names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies type alias, and the review check that would catch drift.
0238	type inference	authored	reviewed	type inference names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies type inference, and the review check that would catch drift.
0239	type system	authored	reviewed	type system names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies type system, and the review check that would catch drift.
0240	typechecker	authored	reviewed	The checker that enforces type law before execution.
0241	typeclass	authored	reviewed	typeclass names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies typeclass, and the review check that would catch drift.
0242	unification	authored	reviewed	unification names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies unification, and the review check that would catch drift.
0243	union	authored	reviewed	union names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies union, and the review check that would catch drift.
0244	value	authored	reviewed	value names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies value, and the review check that would catch drift.
0245	variance	authored	reviewed	variance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies variance, and the review check that would catch drift.
0246	virtual	authored	reviewed	virtual names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies virtual, and the review check that would catch drift.
0247	visibility	authored	reviewed	visibility names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies visibility, and the review check that would catch drift.
0248	visitor	authored	reviewed	visitor names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies visitor, and the review check that would catch drift.
0249	where-clause	authored	reviewed	where-clause names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies where-clause, and the review check that would catch drift.

98.2 Entries

98.2.1 [0113] abstract class

Status: canonical

Completion: authored

Semantic status: reviewed

Force: abstract class names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies abstract class, and the review check that would catch drift.

Shadow: misusing abstract class at rune 0113 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name abstract class when the prompt needs this obligation made explicit: abstract class names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies abstract class, and the review check that would catch drift.
• Ask the assistant to state the abstract class shadow before proposing changes.

Example clause:

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

98.2.2 [0114] alias

Status: canonical

Completion: authored

Semantic status: reviewed

Force: alias names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies alias, and the review check that would catch drift.

Shadow: misusing alias at rune 0114 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name alias when the prompt needs this obligation made explicit: alias names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies alias, and the review check that would catch drift.
• Ask the assistant to state the alias shadow before proposing changes.

Example clause:

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

98.2.3 [0115] annotation

Status: canonical

Completion: authored

Semantic status: reviewed

Force: annotation names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies annotation, and the review check that would catch drift.

Shadow: misusing annotation at rune 0115 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name annotation when the prompt needs this obligation made explicit: annotation names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies annotation, and the review check that would catch drift.
• Ask the assistant to state the annotation shadow before proposing changes.

Example clause:

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

98.2.4 [0116] argument

Status: canonical

Completion: authored

Semantic status: reviewed

Force: argument names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies argument, and the review check that would catch drift.

Shadow: misusing argument at rune 0116 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name argument when the prompt needs this obligation made explicit: argument names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies argument, and the review check that would catch drift.
• Ask the assistant to state the argument shadow before proposing changes.

Example clause:

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

98.2.5 [0117] arity

Status: canonical

Completion: authored

Semantic status: reviewed

Force: arity names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies arity, and the review check that would catch drift.

Shadow: misusing arity at rune 0117 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name arity when the prompt needs this obligation made explicit: arity names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies arity, and the review check that would catch drift.
• Ask the assistant to state the arity shadow before proposing changes.

Example clause:

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

98.2.6 [0118] assembly

Status: canonical

Completion: authored

Semantic status: reviewed

Force: assembly names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies assembly, and the review check that would catch drift.

Shadow: misusing assembly at rune 0118 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name assembly when the prompt needs this obligation made explicit: assembly names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies assembly, and the review check that would catch drift.
• Ask the assistant to state the assembly shadow before proposing changes.

Example clause:

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

98.2.7 [0119] assertion {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: assertion (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies assertion, and the review check that would catch drift.

Shadow: misusing assertion at rune 0119 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name assertion when the prompt needs this obligation made explicit: assertion (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies assertion, and the review check that would catch drift.
• 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.

98.2.8 [0120] AST

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The tree form of parsed program structure.

Shadow: misusing AST at rune 0120 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name AST when the prompt needs this obligation made explicit: The tree form of parsed program structure.
• Ask the assistant to state the AST shadow before proposing changes.

Example clause:

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

Pocket gloss: The tree form of parsed program structure.

98.2.9 [0121] attribute

Status: canonical

Completion: authored

Semantic status: reviewed

Force: attribute names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies attribute, and the review check that would catch drift.

Shadow: misusing attribute at rune 0121 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name attribute when the prompt needs this obligation made explicit: attribute names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies attribute, and the review check that would catch drift.
• Ask the assistant to state the attribute shadow before proposing changes.

Example clause:

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

98.2.10 [0122] binding

Status: canonical

Completion: authored

Semantic status: reviewed

Force: binding names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies binding, and the review check that would catch drift.

Shadow: misusing binding at rune 0122 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name binding when the prompt needs this obligation made explicit: binding names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies binding, and the review check that would catch drift.
• Ask the assistant to state the binding shadow before proposing changes.

Example clause:

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

98.2.11 [0123] borrow {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: borrow (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies borrow, and the review check that would catch drift.

Shadow: misusing borrow at rune 0123 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name borrow when the prompt needs this obligation made explicit: borrow (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies borrow, and the review check that would catch drift.
• Ask the assistant to state the borrow shadow before proposing changes.

Example clause:

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

98.2.12 [0124] borrow checker

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A checker that enforces safe borrowing and lifetime law before runtime.

Shadow: misusing borrow checker at rune 0124 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name borrow checker when the prompt needs this obligation made explicit: A checker that enforces safe borrowing and lifetime law before runtime.
• Ask the assistant to state the borrow checker shadow before proposing changes.

Example clause:

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

Pocket gloss: A checker that enforces safe borrowing and lifetime law before runtime.

98.2.13 [0125] bytecode

Status: canonical

Completion: authored

Semantic status: reviewed

Force: bytecode names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies bytecode, and the review check that would catch drift.

Shadow: misusing bytecode at rune 0125 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name bytecode when the prompt needs this obligation made explicit: bytecode names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies bytecode, and the review check that would catch drift.
• Ask the assistant to state the bytecode shadow before proposing changes.

Example clause:

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

98.2.14 [0126] capture

Status: canonical

Completion: authored

Semantic status: reviewed

Force: capture names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies capture, and the review check that would catch drift.

Shadow: misusing capture at rune 0126 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name capture when the prompt needs this obligation made explicit: capture names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies capture, and the review check that would catch drift.
• Ask the assistant to state the capture shadow before proposing changes.

Example clause:

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

98.2.15 [0127] cast

Status: canonical

Completion: authored

Semantic status: reviewed

Force: cast names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies cast, and the review check that would catch drift.

Shadow: misusing cast at rune 0127 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name cast when the prompt needs this obligation made explicit: cast names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies cast, and the review check that would catch drift.
• Ask the assistant to state the cast shadow before proposing changes.

Example clause:

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

98.2.16 [0128] class

Status: canonical

Completion: authored

Semantic status: reviewed

Force: class names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies class, and the review check that would catch drift.

Shadow: misusing class at rune 0128 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name class when the prompt needs this obligation made explicit: class names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies class, and the review check that would catch drift.
• Ask the assistant to state the class shadow before proposing changes.

Example clause:

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

98.2.17 [0129] closure

Status: canonical

Completion: authored

Semantic status: reviewed

Force: closure names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies closure, and the review check that would catch drift.

Shadow: misusing closure at rune 0129 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name closure when the prompt needs this obligation made explicit: closure names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies closure, and the review check that would catch drift.
• Ask the assistant to state the closure shadow before proposing changes.

Example clause:

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

98.2.18 [0130] coercion

Status: canonical

Completion: authored

Semantic status: reviewed

Force: coercion names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies coercion, and the review check that would catch drift.

Shadow: misusing coercion at rune 0130 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name coercion when the prompt needs this obligation made explicit: coercion names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies coercion, and the review check that would catch drift.
• Ask the assistant to state the coercion shadow before proposing changes.

Example clause:

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

98.2.19 [0131] comment

Status: canonical

Completion: authored

Semantic status: reviewed

Force: comment names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies comment, and the review check that would catch drift.

Shadow: misusing comment at rune 0131 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name comment when the prompt needs this obligation made explicit: comment names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies comment, and the review check that would catch drift.
• Ask the assistant to state the comment shadow before proposing changes.

Example clause:

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

98.2.20 [0132] compile-time

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Known and fixed before execution begins.

Shadow: misusing compile-time at rune 0132 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name compile-time when the prompt needs this obligation made explicit: Known and fixed before execution begins.
• Ask the assistant to state the compile-time shadow before proposing changes.

Example clause:

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

Pocket gloss: Known and fixed before execution begins.

98.2.21 [0133] compiler

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The translator from source language to lower-level executable form.

Shadow: misusing compiler at rune 0133 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name compiler when the prompt needs this obligation made explicit: The translator from source language to lower-level executable form.
• Ask the assistant to state the compiler shadow before proposing changes.

Example clause:

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

Pocket gloss: The translator from source language to lower-level executable form.

98.2.22 [0134] constant

Status: canonical

Completion: authored

Semantic status: reviewed

Force: constant names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies constant, and the review check that would catch drift.

Shadow: misusing constant at rune 0134 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name constant when the prompt needs this obligation made explicit: constant names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies constant, and the review check that would catch drift.
• Ask the assistant to state the constant shadow before proposing changes.

Example clause:

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

98.2.23 [0135] constraint {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: constraint (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies constraint, and the review check that would catch drift.

Shadow: misusing constraint at rune 0135 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name constraint when the prompt needs this obligation made explicit: constraint (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies constraint, and the review check that would catch drift.
• Ask the assistant to state the constraint shadow before proposing changes.

Example clause:

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

98.2.24 [0136] constructor

Status: canonical

Completion: authored

Semantic status: reviewed

Force: constructor names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies constructor, and the review check that would catch drift.

Shadow: misusing constructor at rune 0136 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name constructor when the prompt needs this obligation made explicit: constructor names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies constructor, and the review check that would catch drift.
• Ask the assistant to state the constructor shadow before proposing changes.

Example clause:

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

98.2.25 [0137] contravariance

Status: canonical

Completion: authored

Semantic status: reviewed

Force: contravariance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies contravariance, and the review check that would catch drift.

Shadow: misusing contravariance at rune 0137 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name contravariance when the prompt needs this obligation made explicit: contravariance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies contravariance, and the review check that would catch drift.
• Ask the assistant to state the contravariance shadow before proposing changes.

Example clause:

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

98.2.26 [0138] covariance

Status: canonical

Completion: authored

Semantic status: reviewed

Force: covariance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies covariance, and the review check that would catch drift.

Shadow: misusing covariance at rune 0138 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name covariance when the prompt needs this obligation made explicit: covariance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies covariance, and the review check that would catch drift.
• Ask the assistant to state the covariance shadow before proposing changes.

Example clause:

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

98.2.27 [0139] currying

Status: canonical

Completion: authored

Semantic status: reviewed

Force: currying names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies currying, and the review check that would catch drift.

Shadow: misusing currying at rune 0139 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name currying when the prompt needs this obligation made explicit: currying names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies currying, and the review check that would catch drift.
• Ask the assistant to state the currying shadow before proposing changes.

Example clause:

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

98.2.28 [0140] declaration

Status: canonical

Completion: authored

Semantic status: reviewed

Force: declaration names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies declaration, and the review check that would catch drift.

Shadow: misusing declaration at rune 0140 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name declaration when the prompt needs this obligation made explicit: declaration names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies declaration, and the review check that would catch drift.
• Ask the assistant to state the declaration shadow before proposing changes.

Example clause:

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

98.2.29 [0141] decorator {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: decorator (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies decorator, and the review check that would catch drift.

Shadow: misusing decorator at rune 0141 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name decorator when the prompt needs this obligation made explicit: decorator (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies decorator, and the review check that would catch drift.
• Ask the assistant to state the decorator shadow before proposing changes.

Example clause:

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

98.2.30 [0142] default

Status: canonical

Completion: authored

Semantic status: reviewed

Force: default names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies default, and the review check that would catch drift.

Shadow: misusing default at rune 0142 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name default when the prompt needs this obligation made explicit: default names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies default, and the review check that would catch drift.
• Ask the assistant to state the default shadow before proposing changes.

Example clause:

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

98.2.31 [0143] definition

Status: canonical

Completion: authored

Semantic status: reviewed

Force: definition names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies definition, and the review check that would catch drift.

Shadow: misusing definition at rune 0143 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name definition when the prompt needs this obligation made explicit: definition names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies definition, and the review check that would catch drift.
• Ask the assistant to state the definition shadow before proposing changes.

Example clause:

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

98.2.32 [0144] denotation

Status: canonical

Completion: authored

Semantic status: reviewed

Force: denotation names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies denotation, and the review check that would catch drift.

Shadow: misusing denotation at rune 0144 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name denotation when the prompt needs this obligation made explicit: denotation names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies denotation, and the review check that would catch drift.
• Ask the assistant to state the denotation shadow before proposing changes.

Example clause:

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

98.2.33 [0145] destructor {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: destructor (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies destructor, and the review check that would catch drift.

Shadow: misusing destructor at rune 0145 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name destructor when the prompt needs this obligation made explicit: destructor (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies destructor, and the review check that would catch drift.
• Ask the assistant to state the destructor shadow before proposing changes.

Example clause:

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

98.2.34 [0146] dispatch {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: dispatch (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies dispatch, and the review check that would catch drift.

Shadow: misusing dispatch at rune 0146 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name dispatch when the prompt needs this obligation made explicit: dispatch (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies dispatch, and the review check that would catch drift.
• Ask the assistant to state the dispatch shadow before proposing changes.

Example clause:

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

98.2.35 [0147] domain-specific language

Status: canonical

Completion: authored

Semantic status: reviewed

Force: domain-specific language names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies domain-specific language, and the review check that would catch drift.

Shadow: misusing domain-specific language at rune 0147 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name domain-specific language when the prompt needs this obligation made explicit: domain-specific language names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies domain-specific language, and the review check that would catch drift.
• Ask the assistant to state the domain-specific language shadow before proposing changes.

Example clause:

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

98.2.36 [0148] dynamic scope

Status: canonical

Completion: authored

Semantic status: reviewed

Force: dynamic scope names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies dynamic scope, and the review check that would catch drift.

Shadow: misusing dynamic scope at rune 0148 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name dynamic scope when the prompt needs this obligation made explicit: dynamic scope names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies dynamic scope, and the review check that would catch drift.
• Ask the assistant to state the dynamic scope shadow before proposing changes.

Example clause:

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

98.2.37 [0149] effect

Status: canonical

Completion: authored

Semantic status: reviewed

Force: effect names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies effect, and the review check that would catch drift.

Shadow: misusing effect at rune 0149 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name effect when the prompt needs this obligation made explicit: effect names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies effect, and the review check that would catch drift.
• Ask the assistant to state the effect shadow before proposing changes.

Example clause:

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

98.2.38 [0150] enum

Status: canonical

Completion: authored

Semantic status: reviewed

Force: enum names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies enum, and the review check that would catch drift.

Shadow: misusing enum at rune 0150 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name enum when the prompt needs this obligation made explicit: enum names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies enum, and the review check that would catch drift.
• Ask the assistant to state the enum shadow before proposing changes.

Example clause:

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

98.2.39 [0151] evaluation {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: evaluation (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies evaluation, and the review check that would catch drift.

Shadow: misusing evaluation at rune 0151 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name evaluation when the prompt needs this obligation made explicit: evaluation (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies evaluation, and the review check that would catch drift.
• 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.

98.2.40 [0152] export {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: export (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies export, and the review check that would catch drift.

Shadow: misusing export at rune 0152 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name export when the prompt needs this obligation made explicit: export (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies export, and the review check that would catch drift.
• Ask the assistant to state the export shadow before proposing changes.

Example clause:

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

98.2.41 [0153] expression

Status: canonical

Completion: authored

Semantic status: reviewed

Force: expression names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies expression, and the review check that would catch drift.

Shadow: misusing expression at rune 0153 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name expression when the prompt needs this obligation made explicit: expression names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies expression, and the review check that would catch drift.
• Ask the assistant to state the expression shadow before proposing changes.

Example clause:

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

98.2.42 [0154] extern

Status: canonical

Completion: authored

Semantic status: reviewed

Force: extern names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies extern, and the review check that would catch drift.

Shadow: misusing extern at rune 0154 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name extern when the prompt needs this obligation made explicit: extern names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies extern, and the review check that would catch drift.
• Ask the assistant to state the extern shadow before proposing changes.

Example clause:

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

98.2.43 [0155] field {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: field (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies field, and the review check that would catch drift.

Shadow: misusing field at rune 0155 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name field when the prompt needs this obligation made explicit: field (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies field, and the review check that would catch drift.
• Ask the assistant to state the field shadow before proposing changes.

Example clause:

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

98.2.44 [0156] final

Status: canonical

Completion: authored

Semantic status: reviewed

Force: final names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies final, and the review check that would catch drift.

Shadow: misusing final at rune 0156 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name final when the prompt needs this obligation made explicit: final names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies final, and the review check that would catch drift.
• Ask the assistant to state the final shadow before proposing changes.

Example clause:

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

98.2.45 [0157] function

Status: canonical

Completion: authored

Semantic status: reviewed

Force: function names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies function, and the review check that would catch drift.

Shadow: misusing function at rune 0157 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name function when the prompt needs this obligation made explicit: function names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies function, and the review check that would catch drift.
• Ask the assistant to state the function shadow before proposing changes.

Example clause:

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

98.2.46 [0158] generic {Lang}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: One definition parameterized over many concrete types or cases.

Shadow: misusing generic at rune 0158 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name generic when the prompt needs this obligation made explicit: One definition parameterized over many concrete types or cases.
• Ask the assistant to state the generic shadow before proposing changes.

Example clause:

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

Pocket gloss: One definition parameterized over many concrete types or cases.

98.2.47 [0159] grammar

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The rules that say what strings count as well-formed structure.

Shadow: misusing grammar at rune 0159 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name grammar when the prompt needs this obligation made explicit: The rules that say what strings count as well-formed structure.
• Ask the assistant to state the grammar shadow before proposing changes.

Example clause:

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

Pocket gloss: The rules that say what strings count as well-formed structure.

98.2.48 [0160] higher-order function

Status: canonical

Completion: authored

Semantic status: reviewed

Force: higher-order function names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies higher-order function, and the review check that would catch drift.

Shadow: misusing higher-order function at rune 0160 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name higher-order function when the prompt needs this obligation made explicit: higher-order function names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies higher-order function, and the review check that would catch drift.
• Ask the assistant to state the higher-order function shadow before proposing changes.

Example clause:

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

98.2.49 [0161] identifier

Status: canonical

Completion: authored

Semantic status: reviewed

Force: identifier names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies identifier, and the review check that would catch drift.

Shadow: misusing identifier at rune 0161 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name identifier when the prompt needs this obligation made explicit: identifier names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies identifier, and the review check that would catch drift.
• Ask the assistant to state the identifier shadow before proposing changes.

Example clause:

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

98.2.50 [0162] impl

Status: canonical

Completion: authored

Semantic status: reviewed

Force: impl names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies impl, and the review check that would catch drift.

Shadow: misusing impl at rune 0162 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name impl when the prompt needs this obligation made explicit: impl names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies impl, and the review check that would catch drift.
• Ask the assistant to state the impl shadow before proposing changes.

Example clause:

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

98.2.51 [0163] implementation {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: implementation (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies implementation, and the review check that would catch drift.

Shadow: misusing implementation at rune 0163 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name implementation when the prompt needs this obligation made explicit: implementation (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies implementation, and the review check that would catch drift.
• Ask the assistant to state the implementation shadow before proposing changes.

Example clause:

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

98.2.52 [0164] import

Status: canonical

Completion: authored

Semantic status: reviewed

Force: import names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies import, and the review check that would catch drift.

Shadow: misusing import at rune 0164 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name import when the prompt needs this obligation made explicit: import names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies import, and the review check that would catch drift.
• Ask the assistant to state the import shadow before proposing changes.

Example clause:

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

98.2.53 [0165] include

Status: canonical

Completion: authored

Semantic status: reviewed

Force: include names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies include, and the review check that would catch drift.

Shadow: misusing include at rune 0165 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name include when the prompt needs this obligation made explicit: include names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies include, and the review check that would catch drift.
• Ask the assistant to state the include shadow before proposing changes.

Example clause:

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

98.2.54 [0166] inference

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Recovering missing type or shape information from surrounding evidence.

Shadow: misusing inference at rune 0166 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name inference when the prompt needs this obligation made explicit: Recovering missing type or shape information from surrounding evidence.
• Ask the assistant to state the inference shadow before proposing changes.

Example clause:

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

Pocket gloss: Recovering missing type or shape information from surrounding evidence.

98.2.55 [0167] inheritance

Status: canonical

Completion: authored

Semantic status: reviewed

Force: inheritance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies inheritance, and the review check that would catch drift.

Shadow: misusing inheritance at rune 0167 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name inheritance when the prompt needs this obligation made explicit: inheritance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies inheritance, and the review check that would catch drift.
• Ask the assistant to state the inheritance shadow before proposing changes.

Example clause:

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

98.2.56 [0168] inline {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: inline (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies inline, and the review check that would catch drift.

Shadow: misusing inline at rune 0168 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name inline when the prompt needs this obligation made explicit: inline (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies inline, and the review check that would catch drift.
• Ask the assistant to state the inline shadow before proposing changes.

Example clause:

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

98.2.57 [0169] instruction {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: instruction (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies instruction, and the review check that would catch drift.

Shadow: misusing instruction at rune 0169 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name instruction when the prompt needs this obligation made explicit: instruction (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies instruction, and the review check that would catch drift.
• Ask the assistant to state the instruction shadow before proposing changes.

Example clause:

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

98.2.58 [0170] interface {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: interface (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies interface, and the review check that would catch drift.

Shadow: misusing interface at rune 0170 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name interface when the prompt needs this obligation made explicit: interface (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies interface, and the review check that would catch drift.
• Ask the assistant to state the interface shadow before proposing changes.

Example clause:

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

98.2.59 [0171] interpreter {Lang}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A runtime that executes a representation rather than precompiling it away.

Shadow: misusing interpreter at rune 0171 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name interpreter when the prompt needs this obligation made explicit: A runtime that executes a representation rather than precompiling it away.
• Ask the assistant to state the interpreter shadow before proposing changes.

Example clause:

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

Pocket gloss: A runtime that executes a representation rather than precompiling it away.

98.2.60 [0172] IR

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: An internal representation built for analysis and transformation.

Shadow: misusing IR at rune 0172 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name IR when the prompt needs this obligation made explicit: An internal representation built for analysis and transformation.
• Ask the assistant to state the IR shadow before proposing changes.

Example clause:

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

Pocket gloss: An internal representation built for analysis and transformation.

98.2.61 [0173] keyword

Status: canonical

Completion: authored

Semantic status: reviewed

Force: keyword names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies keyword, and the review check that would catch drift.

Shadow: misusing keyword at rune 0173 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name keyword when the prompt needs this obligation made explicit: keyword names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies keyword, and the review check that would catch drift.
• Ask the assistant to state the keyword shadow before proposing changes.

Example clause:

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

98.2.62 [0174] lambda

Status: canonical

Completion: authored

Semantic status: reviewed

Force: lambda names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies lambda, and the review check that would catch drift.

Shadow: misusing lambda at rune 0174 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name lambda when the prompt needs this obligation made explicit: lambda names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies lambda, and the review check that would catch drift.
• Ask the assistant to state the lambda shadow before proposing changes.

Example clause:

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

98.2.63 [0175] lexical scope

Status: canonical

Completion: authored

Semantic status: reviewed

Force: lexical scope names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies lexical scope, and the review check that would catch drift.

Shadow: misusing lexical scope at rune 0175 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name lexical scope when the prompt needs this obligation made explicit: lexical scope names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies lexical scope, and the review check that would catch drift.
• Ask the assistant to state the lexical scope shadow before proposing changes.

Example clause:

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

98.2.64 [0176] lifetime {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: lifetime (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies lifetime, and the review check that would catch drift.

Shadow: misusing lifetime at rune 0176 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name lifetime when the prompt needs this obligation made explicit: lifetime (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies lifetime, and the review check that would catch drift.
• Ask the assistant to state the lifetime shadow before proposing changes.

Example clause:

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

98.2.65 [0177] linker

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The binder that turns compiled pieces into one loadable whole.

Shadow: misusing linker at rune 0177 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name linker when the prompt needs this obligation made explicit: The binder that turns compiled pieces into one loadable whole.
• Ask the assistant to state the linker shadow before proposing changes.

Example clause:

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

Pocket gloss: The binder that turns compiled pieces into one loadable whole.

98.2.66 [0178] literal

Status: canonical

Completion: authored

Semantic status: reviewed

Force: literal names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies literal, and the review check that would catch drift.

Shadow: misusing literal at rune 0178 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name literal when the prompt needs this obligation made explicit: literal names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies literal, and the review check that would catch drift.
• Ask the assistant to state the literal shadow before proposing changes.

Example clause:

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

98.2.67 [0179] loader

Status: canonical

Completion: authored

Semantic status: reviewed

Force: loader names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies loader, and the review check that would catch drift.

Shadow: misusing loader at rune 0179 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name loader when the prompt needs this obligation made explicit: loader names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies loader, and the review check that would catch drift.
• Ask the assistant to state the loader shadow before proposing changes.

Example clause:

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

98.2.68 [0180] macro

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Code that writes or reshapes code.

Shadow: misusing macro at rune 0180 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name macro when the prompt needs this obligation made explicit: Code that writes or reshapes code.
• Ask the assistant to state the macro shadow before proposing changes.

Example clause:

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

Pocket gloss: Code that writes or reshapes code.

98.2.69 [0181] metaprogramming

Status: canonical

Completion: authored

Semantic status: reviewed

Force: metaprogramming names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies metaprogramming, and the review check that would catch drift.

Shadow: misusing metaprogramming at rune 0181 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name metaprogramming when the prompt needs this obligation made explicit: metaprogramming names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies metaprogramming, and the review check that would catch drift.
• Ask the assistant to state the metaprogramming shadow before proposing changes.

Example clause:

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

98.2.70 [0182] method

Status: canonical

Completion: authored

Semantic status: reviewed

Force: method names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies method, and the review check that would catch drift.

Shadow: misusing method at rune 0182 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name method when the prompt needs this obligation made explicit: method names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies method, and the review check that would catch drift.
• Ask the assistant to state the method shadow before proposing changes.

Example clause:

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

98.2.71 [0183] mixin

Status: canonical

Completion: authored

Semantic status: reviewed

Force: mixin names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mixin, and the review check that would catch drift.

Shadow: misusing mixin at rune 0183 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name mixin when the prompt needs this obligation made explicit: mixin names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mixin, and the review check that would catch drift.
• Ask the assistant to state the mixin shadow before proposing changes.

Example clause:

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

98.2.72 [0184] module {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: module (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies module, and the review check that would catch drift.

Shadow: misusing module at rune 0184 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name module when the prompt needs this obligation made explicit: module (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies module, and the review check that would catch drift.
• Ask the assistant to state the module shadow before proposing changes.

Example clause:

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

98.2.73 [0185] monomorphization

Status: canonical

Completion: authored

Semantic status: reviewed

Force: monomorphization names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies monomorphization, and the review check that would catch drift.

Shadow: misusing monomorphization at rune 0185 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name monomorphization when the prompt needs this obligation made explicit: monomorphization names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies monomorphization, and the review check that would catch drift.
• Ask the assistant to state the monomorphization shadow before proposing changes.

Example clause:

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

98.2.74 [0186] mutability

Status: canonical

Completion: authored

Semantic status: reviewed

Force: mutability names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mutability, and the review check that would catch drift.

Shadow: misusing mutability at rune 0186 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name mutability when the prompt needs this obligation made explicit: mutability names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies mutability, and the review check that would catch drift.
• Ask the assistant to state the mutability shadow before proposing changes.

Example clause:

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

98.2.75 [0187] name resolution

Status: canonical

Completion: authored

Semantic status: reviewed

Force: name resolution names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies name resolution, and the review check that would catch drift.

Shadow: misusing name resolution at rune 0187 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name name resolution when the prompt needs this obligation made explicit: name resolution names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies name resolution, and the review check that would catch drift.
• Ask the assistant to state the name resolution shadow before proposing changes.

Example clause:

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

98.2.76 [0188] namespace {Lang}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A naming region that prevents collisions and clarifies ownership.

Shadow: misusing namespace at rune 0188 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name namespace when the prompt needs this obligation made explicit: A naming region that prevents collisions and clarifies ownership.
• Ask the assistant to state the namespace shadow before proposing changes.

Example clause:

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

Pocket gloss: A naming region that prevents collisions and clarifies ownership.

98.2.77 [0189] object

Status: canonical

Completion: authored

Semantic status: reviewed

Force: object names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies object, and the review check that would catch drift.

Shadow: misusing object at rune 0189 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name object when the prompt needs this obligation made explicit: object names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies object, and the review check that would catch drift.
• Ask the assistant to state the object shadow before proposing changes.

Example clause:

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

98.2.78 [0190] opcode {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: opcode (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies opcode, and the review check that would catch drift.

Shadow: misusing opcode at rune 0190 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name opcode when the prompt needs this obligation made explicit: opcode (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies opcode, and the review check that would catch drift.
• Ask the assistant to state the opcode shadow before proposing changes.

Example clause:

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

98.2.79 [0191] overload

Status: canonical

Completion: authored

Semantic status: reviewed

Force: overload names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies overload, and the review check that would catch drift.

Shadow: misusing overload at rune 0191 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name overload when the prompt needs this obligation made explicit: overload names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies overload, and the review check that would catch drift.
• Ask the assistant to state the overload shadow before proposing changes.

Example clause:

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

98.2.80 [0192] override

Status: canonical

Completion: authored

Semantic status: reviewed

Force: override names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies override, and the review check that would catch drift.

Shadow: misusing override at rune 0192 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name override when the prompt needs this obligation made explicit: override names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies override, and the review check that would catch drift.
• Ask the assistant to state the override shadow before proposing changes.

Example clause:

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

98.2.81 [0193] ownership

Status: canonical

Completion: authored

Semantic status: reviewed

Force: ownership names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies ownership, and the review check that would catch drift.

Shadow: misusing ownership at rune 0193 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name ownership when the prompt needs this obligation made explicit: ownership names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies ownership, and the review check that would catch drift.
• Ask the assistant to state the ownership shadow before proposing changes.

Example clause:

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

98.2.82 [0194] package {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: package (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies package, and the review check that would catch drift.

Shadow: misusing package at rune 0194 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name package when the prompt needs this obligation made explicit: package (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies package, and the review check that would catch drift.
• Ask the assistant to state the package shadow before proposing changes.

Example clause:

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

98.2.83 [0195] parameter

Status: canonical

Completion: authored

Semantic status: reviewed

Force: parameter names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies parameter, and the review check that would catch drift.

Shadow: misusing parameter at rune 0195 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name parameter when the prompt needs this obligation made explicit: parameter names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies parameter, and the review check that would catch drift.
• Ask the assistant to state the parameter shadow before proposing changes.

Example clause:

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

98.2.84 [0196] parametric polymorphism

Status: canonical

Completion: authored

Semantic status: reviewed

Force: parametric polymorphism names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies parametric polymorphism, and the review check that would catch drift.

Shadow: misusing parametric polymorphism at rune 0196 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name parametric polymorphism when the prompt needs this obligation made explicit: parametric polymorphism names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies parametric polymorphism, and the review check that would catch drift.
• Ask the assistant to state the parametric polymorphism shadow before proposing changes.

Example clause:

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

98.2.85 [0197] parser

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The mechanism that turns surface text into structured meaning.

Shadow: misusing parser at rune 0197 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name parser when the prompt needs this obligation made explicit: The mechanism that turns surface text into structured meaning.
• Ask the assistant to state the parser shadow before proposing changes.

Example clause:

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

Pocket gloss: The mechanism that turns surface text into structured meaning.

98.2.86 [0198] pattern

Status: canonical

Completion: authored

Semantic status: reviewed

Force: pattern names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies pattern, and the review check that would catch drift.

Shadow: misusing pattern at rune 0198 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name pattern when the prompt needs this obligation made explicit: pattern names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies pattern, and the review check that would catch drift.
• Ask the assistant to state the pattern shadow before proposing changes.

Example clause:

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

98.2.87 [0199] pattern matching

Status: canonical

Completion: authored

Semantic status: reviewed

Force: pattern matching names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies pattern matching, and the review check that would catch drift.

Shadow: misusing pattern matching at rune 0199 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name pattern matching when the prompt needs this obligation made explicit: pattern matching names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies pattern matching, and the review check that would catch drift.
• Ask the assistant to state the pattern matching shadow before proposing changes.

Example clause:

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

98.2.88 [0200] polymorphism

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: One interface, many concrete behaviors.

Shadow: misusing polymorphism at rune 0200 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name polymorphism when the prompt needs this obligation made explicit: One interface, many concrete behaviors.
• Ask the assistant to state the polymorphism shadow before proposing changes.

Example clause:

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

Pocket gloss: One interface, many concrete behaviors.

98.2.89 [0201] procedure {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: procedure (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies procedure, and the review check that would catch drift.

Shadow: misusing procedure at rune 0201 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name procedure when the prompt needs this obligation made explicit: procedure (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies procedure, and the review check that would catch drift.
• Ask the assistant to state the procedure shadow before proposing changes.

Example clause:

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

98.2.90 [0202] program

Status: canonical

Completion: authored

Semantic status: reviewed

Force: program names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies program, and the review check that would catch drift.

Shadow: misusing program at rune 0202 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name program when the prompt needs this obligation made explicit: program names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies program, and the review check that would catch drift.
• Ask the assistant to state the program shadow before proposing changes.

Example clause:

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

98.2.91 [0203] property {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: property (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies property, and the review check that would catch drift.

Shadow: misusing property at rune 0203 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name property when the prompt needs this obligation made explicit: property (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies property, and the review check that would catch drift.
• Ask the assistant to state the property shadow before proposing changes.

Example clause:

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

98.2.92 [0204] protected

Status: canonical

Completion: authored

Semantic status: reviewed

Force: protected names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies protected, and the review check that would catch drift.

Shadow: misusing protected at rune 0204 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name protected when the prompt needs this obligation made explicit: protected names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies protected, and the review check that would catch drift.
• Ask the assistant to state the protected shadow before proposing changes.

Example clause:

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

98.2.93 [0205] public

Status: canonical

Completion: authored

Semantic status: reviewed

Force: public names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies public, and the review check that would catch drift.

Shadow: misusing public at rune 0205 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name public when the prompt needs this obligation made explicit: public names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies public, and the review check that would catch drift.
• Ask the assistant to state the public shadow before proposing changes.

Example clause:

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

98.2.94 [0206] purity

Status: canonical

Completion: authored

Semantic status: reviewed

Force: purity names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies purity, and the review check that would catch drift.

Shadow: misusing purity at rune 0206 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name purity when the prompt needs this obligation made explicit: purity names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies purity, and the review check that would catch drift.
• Ask the assistant to state the purity shadow before proposing changes.

Example clause:

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

98.2.95 [0207] qualified name

Status: canonical

Completion: authored

Semantic status: reviewed

Force: qualified name names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies qualified name, and the review check that would catch drift.

Shadow: misusing qualified name at rune 0207 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name qualified name when the prompt needs this obligation made explicit: qualified name names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies qualified name, and the review check that would catch drift.
• Ask the assistant to state the qualified name shadow before proposing changes.

Example clause:

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

98.2.96 [0208] readonly

Status: canonical

Completion: authored

Semantic status: reviewed

Force: readonly names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies readonly, and the review check that would catch drift.

Shadow: misusing readonly at rune 0208 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name readonly when the prompt needs this obligation made explicit: readonly names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies readonly, and the review check that would catch drift.
• Ask the assistant to state the readonly shadow before proposing changes.

Example clause:

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

98.2.97 [0209] record {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: record (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies record, and the review check that would catch drift.

Shadow: misusing record at rune 0209 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name record when the prompt needs this obligation made explicit: record (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies record, and the review check that would catch drift.
• Ask the assistant to state the record shadow before proposing changes.

Example clause:

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

98.2.98 [0210] reference {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: reference (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies reference, and the review check that would catch drift.

Shadow: misusing reference at rune 0210 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name reference when the prompt needs this obligation made explicit: reference (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies reference, and the review check that would catch drift.
• Ask the assistant to state the reference shadow before proposing changes.

Example clause:

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

98.2.99 [0211] referential transparency

Status: canonical

Completion: authored

Semantic status: reviewed

Force: referential transparency names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies referential transparency, and the review check that would catch drift.

Shadow: misusing referential transparency at rune 0211 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name referential transparency when the prompt needs this obligation made explicit: referential transparency names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies referential transparency, and the review check that would catch drift.
• Ask the assistant to state the referential transparency shadow before proposing changes.

Example clause:

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

98.2.100 [0212] reflection

Status: canonical

Completion: authored

Semantic status: reviewed

Force: reflection names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies reflection, and the review check that would catch drift.

Shadow: misusing reflection at rune 0212 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name reflection when the prompt needs this obligation made explicit: reflection names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies reflection, and the review check that would catch drift.
• Ask the assistant to state the reflection shadow before proposing changes.

Example clause:

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

98.2.101 [0213] resolution

Status: canonical

Completion: authored

Semantic status: reviewed

Force: resolution names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies resolution, and the review check that would catch drift.

Shadow: misusing resolution at rune 0213 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name resolution when the prompt needs this obligation made explicit: resolution names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies resolution, and the review check that would catch drift.
• Ask the assistant to state the resolution shadow before proposing changes.

Example clause:

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

98.2.102 [0214] return type

Status: canonical

Completion: authored

Semantic status: reviewed

Force: return type names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies return type, and the review check that would catch drift.

Shadow: misusing return type at rune 0214 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name return type when the prompt needs this obligation made explicit: return type names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies return type, and the review check that would catch drift.
• Ask the assistant to state the return type shadow before proposing changes.

Example clause:

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

98.2.103 [0215] runtime type

Status: canonical

Completion: authored

Semantic status: reviewed

Force: runtime type names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies runtime type, and the review check that would catch drift.

Shadow: misusing runtime type at rune 0215 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name runtime type when the prompt needs this obligation made explicit: runtime type names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies runtime type, and the review check that would catch drift.
• Ask the assistant to state the runtime type shadow before proposing changes.

Example clause:

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

98.2.104 [0216] scope {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: scope (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies scope, and the review check that would catch drift.

Shadow: misusing scope at rune 0216 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name scope when the prompt needs this obligation made explicit: scope (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies scope, and the review check that would catch drift.
• Ask the assistant to state the scope shadow before proposing changes.

Example clause:

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

98.2.105 [0217] sealed

Status: canonical

Completion: authored

Semantic status: reviewed

Force: sealed names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies sealed, and the review check that would catch drift.

Shadow: misusing sealed at rune 0217 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name sealed when the prompt needs this obligation made explicit: sealed names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies sealed, and the review check that would catch drift.
• Ask the assistant to state the sealed shadow before proposing changes.

Example clause:

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

98.2.106 [0218] semantics

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: What a program means, not just how it is spelled.

Shadow: misusing semantics at rune 0218 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name semantics when the prompt needs this obligation made explicit: What a program means, not just how it is spelled.
• Ask the assistant to state the semantics shadow before proposing changes.

Example clause:

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

Pocket gloss: What a program means, not just how it is spelled.

98.2.107 [0219] signature {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: signature (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies signature, and the review check that would catch drift.

Shadow: misusing signature at rune 0219 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name signature when the prompt needs this obligation made explicit: signature (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies signature, and the review check that would catch drift.
• Ask the assistant to state the signature shadow before proposing changes.

Example clause:

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

98.2.108 [0220] source code

Status: canonical

Completion: authored

Semantic status: reviewed

Force: source code names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies source code, and the review check that would catch drift.

Shadow: misusing source code at rune 0220 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name source code when the prompt needs this obligation made explicit: source code names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies source code, and the review check that would catch drift.
• Ask the assistant to state the source code shadow before proposing changes.

Example clause:

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

98.2.109 [0221] specialization

Status: canonical

Completion: authored

Semantic status: reviewed

Force: specialization names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies specialization, and the review check that would catch drift.

Shadow: misusing specialization at rune 0221 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name specialization when the prompt needs this obligation made explicit: specialization names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies specialization, and the review check that would catch drift.
• Ask the assistant to state the specialization shadow before proposing changes.

Example clause:

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

98.2.110 [0222] statement

Status: canonical

Completion: authored

Semantic status: reviewed

Force: statement names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies statement, and the review check that would catch drift.

Shadow: misusing statement at rune 0222 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name statement when the prompt needs this obligation made explicit: statement names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies statement, and the review check that would catch drift.
• Ask the assistant to state the statement shadow before proposing changes.

Example clause:

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

98.2.111 [0223] static dispatch

Status: canonical

Completion: authored

Semantic status: reviewed

Force: static dispatch names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies static dispatch, and the review check that would catch drift.

Shadow: misusing static dispatch at rune 0223 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name static dispatch when the prompt needs this obligation made explicit: static dispatch names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies static dispatch, and the review check that would catch drift.
• Ask the assistant to state the static dispatch shadow before proposing changes.

Example clause:

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

98.2.112 [0224] strictness

Status: canonical

Completion: authored

Semantic status: reviewed

Force: strictness names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies strictness, and the review check that would catch drift.

Shadow: misusing strictness at rune 0224 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name strictness when the prompt needs this obligation made explicit: strictness names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies strictness, and the review check that would catch drift.
• Ask the assistant to state the strictness shadow before proposing changes.

Example clause:

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

98.2.113 [0225] struct {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: struct (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies struct, and the review check that would catch drift.

Shadow: misusing struct at rune 0225 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name struct when the prompt needs this obligation made explicit: struct (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies struct, and the review check that would catch drift.
• Ask the assistant to state the struct shadow before proposing changes.

Example clause:

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

98.2.114 [0226] subtype

Status: canonical

Completion: authored

Semantic status: reviewed

Force: subtype names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies subtype, and the review check that would catch drift.

Shadow: misusing subtype at rune 0226 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name subtype when the prompt needs this obligation made explicit: subtype names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies subtype, and the review check that would catch drift.
• Ask the assistant to state the subtype shadow before proposing changes.

Example clause:

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

98.2.115 [0227] supertype

Status: canonical

Completion: authored

Semantic status: reviewed

Force: supertype names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies supertype, and the review check that would catch drift.

Shadow: misusing supertype at rune 0227 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name supertype when the prompt needs this obligation made explicit: supertype names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies supertype, and the review check that would catch drift.
• Ask the assistant to state the supertype shadow before proposing changes.

Example clause:

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

98.2.116 [0228] symbol

Status: canonical

Completion: authored

Semantic status: reviewed

Force: symbol names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies symbol, and the review check that would catch drift.

Shadow: misusing symbol at rune 0228 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name symbol when the prompt needs this obligation made explicit: symbol names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies symbol, and the review check that would catch drift.
• Ask the assistant to state the symbol shadow before proposing changes.

Example clause:

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

98.2.117 [0229] syntax

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The legal surface form of the language.

Shadow: misusing syntax at rune 0229 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name syntax when the prompt needs this obligation made explicit: The legal surface form of the language.
• Ask the assistant to state the syntax shadow before proposing changes.

Example clause:

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

Pocket gloss: The legal surface form of the language.

98.2.118 [0230] template {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: template (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies template, and the review check that would catch drift.

Shadow: misusing template at rune 0230 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name template when the prompt needs this obligation made explicit: template (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies template, and the review check that would catch drift.
• Ask the assistant to state the template shadow before proposing changes.

Example clause:

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

98.2.119 [0231] theorem {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: theorem (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies theorem, and the review check that would catch drift.

Shadow: misusing theorem at rune 0231 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name theorem when the prompt needs this obligation made explicit: theorem (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies theorem, and the review check that would catch drift.
• 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.

98.2.120 [0232] token {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: token (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies token, and the review check that would catch drift.

Shadow: misusing token at rune 0232 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name token when the prompt needs this obligation made explicit: token (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies token, and the review check that would catch drift.
• Ask the assistant to state the token shadow before proposing changes.

Example clause:

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

98.2.121 [0233] trait

Status: canonical

Completion: authored

Semantic status: reviewed

Force: trait names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies trait, and the review check that would catch drift.

Shadow: misusing trait at rune 0233 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name trait when the prompt needs this obligation made explicit: trait names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies trait, and the review check that would catch drift.
• Ask the assistant to state the trait shadow before proposing changes.

Example clause:

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

98.2.122 [0234] transpiler

Status: canonical

Completion: authored

Semantic status: reviewed

Force: transpiler names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies transpiler, and the review check that would catch drift.

Shadow: misusing transpiler at rune 0234 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name transpiler when the prompt needs this obligation made explicit: transpiler names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies transpiler, and the review check that would catch drift.
• Ask the assistant to state the transpiler shadow before proposing changes.

Example clause:

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

98.2.123 [0235] tuple {Lang}

Status: canonical

Completion: authored

Semantic status: reviewed

Force: tuple (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies tuple, and the review check that would catch drift.

Shadow: misusing tuple at rune 0235 in the Lang lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name tuple when the prompt needs this obligation made explicit: tuple (Lang) names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies tuple, and the review check that would catch drift.
• Ask the assistant to state the tuple shadow before proposing changes.

Example clause:

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

98.2.124 [0236] type

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A declared or inferred class of values and allowed operations.

Shadow: misusing type at rune 0236 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name type when the prompt needs this obligation made explicit: A declared or inferred class of values and allowed operations.
• Ask the assistant to state the type shadow before proposing changes.

Example clause:

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

Pocket gloss: A declared or inferred class of values and allowed operations.

98.2.125 [0237] type alias

Status: canonical

Completion: authored

Semantic status: reviewed

Force: type alias names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies type alias, and the review check that would catch drift.

Shadow: misusing type alias at rune 0237 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name type alias when the prompt needs this obligation made explicit: type alias names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies type alias, and the review check that would catch drift.
• Ask the assistant to state the type alias shadow before proposing changes.

Example clause:

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

98.2.126 [0238] type inference

Status: canonical

Completion: authored

Semantic status: reviewed

Force: type inference names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies type inference, and the review check that would catch drift.

Shadow: misusing type inference at rune 0238 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name type inference when the prompt needs this obligation made explicit: type inference names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies type inference, and the review check that would catch drift.
• Ask the assistant to state the type inference shadow before proposing changes.

Example clause:

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

98.2.127 [0239] type system

Status: canonical

Completion: authored

Semantic status: reviewed

Force: type system names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies type system, and the review check that would catch drift.

Shadow: misusing type system at rune 0239 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name type system when the prompt needs this obligation made explicit: type system names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies type system, and the review check that would catch drift.
• Ask the assistant to state the type system shadow before proposing changes.

Example clause:

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

98.2.128 [0240] typechecker

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The checker that enforces type law before execution.

Shadow: misusing typechecker at rune 0240 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name typechecker when the prompt needs this obligation made explicit: The checker that enforces type law before execution.
• Ask the assistant to state the typechecker shadow before proposing changes.

Example clause:

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

Pocket gloss: The checker that enforces type law before execution.

98.2.129 [0241] typeclass

Status: canonical

Completion: authored

Semantic status: reviewed

Force: typeclass names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies typeclass, and the review check that would catch drift.

Shadow: misusing typeclass at rune 0241 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name typeclass when the prompt needs this obligation made explicit: typeclass names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies typeclass, and the review check that would catch drift.
• Ask the assistant to state the typeclass shadow before proposing changes.

Example clause:

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

98.2.130 [0242] unification

Status: canonical

Completion: authored

Semantic status: reviewed

Force: unification names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies unification, and the review check that would catch drift.

Shadow: misusing unification at rune 0242 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name unification when the prompt needs this obligation made explicit: unification names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies unification, and the review check that would catch drift.
• Ask the assistant to state the unification shadow before proposing changes.

Example clause:

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

98.2.131 [0243] union

Status: canonical

Completion: authored

Semantic status: reviewed

Force: union names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies union, and the review check that would catch drift.

Shadow: misusing union at rune 0243 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name union when the prompt needs this obligation made explicit: union names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies union, and the review check that would catch drift.
• Ask the assistant to state the union shadow before proposing changes.

Example clause:

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

98.2.132 [0244] value

Status: canonical

Completion: authored

Semantic status: reviewed

Force: value names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies value, and the review check that would catch drift.

Shadow: misusing value at rune 0244 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name value when the prompt needs this obligation made explicit: value names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies value, and the review check that would catch drift.
• Ask the assistant to state the value shadow before proposing changes.

Example clause:

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

98.2.133 [0245] variance

Status: canonical

Completion: authored

Semantic status: reviewed

Force: variance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies variance, and the review check that would catch drift.

Shadow: misusing variance at rune 0245 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name variance when the prompt needs this obligation made explicit: variance names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies variance, and the review check that would catch drift.
• Ask the assistant to state the variance shadow before proposing changes.

Example clause:

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

98.2.134 [0246] virtual

Status: canonical

Completion: authored

Semantic status: reviewed

Force: virtual names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies virtual, and the review check that would catch drift.

Shadow: misusing virtual at rune 0246 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name virtual when the prompt needs this obligation made explicit: virtual names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies virtual, and the review check that would catch drift.
• Ask the assistant to state the virtual shadow before proposing changes.

Example clause:

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

98.2.135 [0247] visibility

Status: canonical

Completion: authored

Semantic status: reviewed

Force: visibility names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies visibility, and the review check that would catch drift.

Shadow: misusing visibility at rune 0247 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name visibility when the prompt needs this obligation made explicit: visibility names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies visibility, and the review check that would catch drift.
• Ask the assistant to state the visibility shadow before proposing changes.

Example clause:

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

98.2.136 [0248] visitor

Status: canonical

Completion: authored

Semantic status: reviewed

Force: visitor names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies visitor, and the review check that would catch drift.

Shadow: misusing visitor at rune 0248 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name visitor when the prompt needs this obligation made explicit: visitor names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies visitor, and the review check that would catch drift.
• Ask the assistant to state the visitor shadow before proposing changes.

Example clause:

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

98.2.137 [0249] where-clause

Status: canonical

Completion: authored

Semantic status: reviewed

Force: where-clause names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies where-clause, and the review check that would catch drift.

Shadow: misusing where-clause at rune 0249 in the language lane can let valid-looking form can still carry the wrong meaning; verify by requiring the caster to state the parser, grammar, or semantic rule being relied on.

Prompt uses:

• Name where-clause when the prompt needs this obligation made explicit: where-clause names a concrete language and semantics obligation: make meaning, syntax, and interpretation rules inspectable. In a spell, require the assistant to state the artifact boundary, the evidence that satisfies where-clause, and the review check that would catch drift.
• Ask the assistant to state the where-clause shadow before proposing changes.

Example clause:

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