98  Data, State, and Representation

99 Data, State, and Representation

Range: 0250-0371.

99.1 Completion

Status	Count
authored	122

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

Sigil	Term	Completion	Semantic	Summary
0250	address	authored	generated_draft	address is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the address obligation named before work proceeds.
0251	aggregate state	authored	generated_draft	aggregate state is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the aggregate state obligation named before work proceeds.
0252	array	authored	reviewed	A contiguous ordered collection accessed by position.
0253	bag	authored	generated_draft	bag is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bag obligation named before work proceeds.
0254	binary blob	authored	generated_draft	binary blob is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the binary blob obligation named before work proceeds.
0255	bit	authored	generated_draft	bit is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bit obligation named before work proceeds.
0256	bitmap	authored	generated_draft	bitmap is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bitmap obligation named before work proceeds.
0257	blob	authored	generated_draft	blob is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the blob obligation named before work proceeds.
0258	block {Data}	authored	generated_draft	block in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the block obligation named before work proceeds.
0259	Bloom filter	authored	generated_draft	Bloom filter is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the Bloom filter obligation named before work proceeds.
0260	body	authored	generated_draft	body is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the body obligation named before work proceeds.
0261	book-keeping field	authored	generated_draft	book-keeping field is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the book-keeping field obligation named before work proceeds.
0262	bucket {Data}	authored	generated_draft	bucket in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bucket obligation named before work proceeds.
0263	buffer	authored	reviewed	A temporary holding area used to smooth movement, parsing, or I/O.
0264	byte	authored	generated_draft	byte is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the byte obligation named before work proceeds.
0265	cache entry	authored	generated_draft	cache entry is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the cache entry obligation named before work proceeds.
0266	canonical form {Data}	authored	generated_draft	canonical form in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the canonical form obligation named before work proceeds.
0267	cell	authored	generated_draft	cell is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the cell obligation named before work proceeds.
0268	checksum	authored	reviewed	A compact fingerprint used to detect accidental change.
0269	chunk	authored	generated_draft	chunk is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the chunk obligation named before work proceeds.
0270	column {Data}	authored	generated_draft	column in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the column obligation named before work proceeds.
0271	composite value	authored	generated_draft	composite value is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the composite value obligation named before work proceeds.
0272	config	authored	reviewed	Declared settings that shape behavior without editing code.
0273	constant pool	authored	generated_draft	constant pool is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the constant pool obligation named before work proceeds.
0274	content	authored	generated_draft	content is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the content obligation named before work proceeds.
0275	context object	authored	generated_draft	context object is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the context object obligation named before work proceeds.
0276	cookie	authored	generated_draft	cookie is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the cookie obligation named before work proceeds.
0277	corpus	authored	generated_draft	corpus is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the corpus obligation named before work proceeds.
0278	counter {Data}	authored	generated_draft	counter in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the counter obligation named before work proceeds.
0279	credential {Data}	authored	generated_draft	credential in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the credential obligation named before work proceeds.
0280	cursor {Data}	authored	reviewed	A movable pointer into a sequence or result set.
0281	data frame	authored	generated_draft	data frame is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the data frame obligation named before work proceeds.
0282	data point	authored	generated_draft	data point is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the data point obligation named before work proceeds.
0283	dataset	authored	generated_draft	dataset is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the dataset obligation named before work proceeds.
0284	datum	authored	generated_draft	datum is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the datum obligation named before work proceeds.
0285	delta	authored	generated_draft	delta is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the delta obligation named before work proceeds.
0286	dense vector	authored	generated_draft	dense vector is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the dense vector obligation named before work proceeds.
0287	descriptor	authored	generated_draft	descriptor is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the descriptor obligation named before work proceeds.
0288	dictionary	authored	reviewed	Keyed lookup structure for named values.
0289	digest {Data}	authored	generated_draft	digest in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the digest obligation named before work proceeds.
0290	document	authored	generated_draft	document is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the document obligation named before work proceeds.
0291	edge {Data}	authored	generated_draft	edge in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the edge obligation named before work proceeds.
0292	element	authored	generated_draft	element is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the element obligation named before work proceeds.
0293	embedding {Data}	authored	generated_draft	embedding in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the embedding obligation named before work proceeds.
0294	entity	authored	reviewed	A thing with stable identity that the system cares about.
0295	enum value	authored	generated_draft	enum value is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the enum value obligation named before work proceeds.
0296	envelope	authored	generated_draft	envelope is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the envelope obligation named before work proceeds.
0297	event	authored	reviewed	A record of something that happened.
0298	event log	authored	reviewed	History stored as events instead of overwritten final state.
0299	fact	authored	generated_draft	fact is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the fact obligation named before work proceeds.
0300	feature	authored	generated_draft	feature is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the feature obligation named before work proceeds.
0301	field {Data}	authored	generated_draft	field in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the field obligation named before work proceeds.
0302	fingerprint	authored	generated_draft	fingerprint is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the fingerprint obligation named before work proceeds.
0303	flag	authored	generated_draft	flag is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the flag obligation named before work proceeds.
0304	frame {Data}	authored	generated_draft	frame in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the frame obligation named before work proceeds.
0305	handle {Data}	authored	generated_draft	handle in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the handle obligation named before work proceeds.
0306	hash {Data}	authored	reviewed	A condensed fingerprint used for lookup, bucketing, or integrity checks.
0307	hash map	authored	generated_draft	hash map is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the hash map obligation named before work proceeds.
0308	header	authored	generated_draft	header is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the header obligation named before work proceeds.
0309	heap record	authored	generated_draft	heap record is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the heap record obligation named before work proceeds.
0310	index {Data}	authored	reviewed	An access structure that trades space and write cost for faster reads.
0311	index key	authored	generated_draft	index key is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the index key obligation named before work proceeds.
0312	item	authored	generated_draft	item is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the item obligation named before work proceeds.
0313	iterator	authored	generated_draft	iterator is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the iterator obligation named before work proceeds.
0314	journal	authored	generated_draft	journal is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the journal obligation named before work proceeds.
0315	key {Data}	authored	reviewed	The field by which something is found or grouped.
0316	key-value pair	authored	generated_draft	key-value pair is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the key-value pair obligation named before work proceeds.
0317	ledger	authored	generated_draft	ledger is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the ledger obligation named before work proceeds.
0318	list	authored	generated_draft	list is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the list obligation named before work proceeds.
0319	literal value	authored	generated_draft	literal value is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the literal value obligation named before work proceeds.
0320	map {Data}	authored	reviewed	Associative collection from keys to values.
0321	matrix	authored	generated_draft	matrix is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the matrix obligation named before work proceeds.
0322	message	authored	reviewed	A discrete packet of meaning sent between parts.
0323	metadata	authored	generated_draft	metadata is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the metadata obligation named before work proceeds.
0324	model {Data}	authored	generated_draft	model in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the model obligation named before work proceeds.
0325	multimap	authored	generated_draft	multimap is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the multimap obligation named before work proceeds.
0326	node {Data}	authored	generated_draft	node in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the node obligation named before work proceeds.
0327	null	authored	generated_draft	null is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the null obligation named before work proceeds.
0328	object state	authored	generated_draft	object state is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the object state obligation named before work proceeds.
0329	offset	authored	generated_draft	offset is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the offset obligation named before work proceeds.
0330	page {Data}	authored	generated_draft	page in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the page obligation named before work proceeds.
0331	pair	authored	generated_draft	pair is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the pair obligation named before work proceeds.
0332	payload	authored	generated_draft	payload is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the payload obligation named before work proceeds.
0333	pointer {Data}	authored	generated_draft	pointer in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the pointer obligation named before work proceeds.
0334	pool	authored	generated_draft	pool is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the pool obligation named before work proceeds.
0335	property {Data}	authored	generated_draft	property in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the property obligation named before work proceeds.
0336	queue element	authored	generated_draft	queue element is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the queue element obligation named before work proceeds.
0337	range	authored	generated_draft	range is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the range obligation named before work proceeds.
0338	record {Data}	authored	reviewed	A row-like bundle of named fields describing one thing.
0339	reference {Data}	authored	generated_draft	reference in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the reference obligation named before work proceeds.
0340	relation {Data}	authored	generated_draft	relation in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the relation obligation named before work proceeds.
0341	representation	authored	generated_draft	representation is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the representation obligation named before work proceeds.
0342	resource	authored	generated_draft	resource is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the resource obligation named before work proceeds.
0343	revision {Data}	authored	generated_draft	revision in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the revision obligation named before work proceeds.
0344	ring buffer	authored	generated_draft	ring buffer is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the ring buffer obligation named before work proceeds.
0345	row {Data}	authored	generated_draft	row in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the row obligation named before work proceeds.
0346	scalar	authored	generated_draft	scalar is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the scalar obligation named before work proceeds.
0347	schema {Data}	authored	reviewed	The declared shape of stored meaning. Shadow: drift, silent coercion, and backward-incompatible surprise.
0348	secret {Data}	authored	generated_draft	secret in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the secret obligation named before work proceeds.
0349	segment {Data}	authored	generated_draft	segment in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the segment obligation named before work proceeds.
0350	sequence	authored	generated_draft	sequence is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the sequence obligation named before work proceeds.
0351	series	authored	generated_draft	series is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the series obligation named before work proceeds.
0352	session	authored	generated_draft	session is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the session obligation named before work proceeds.
0353	set	authored	generated_draft	set is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the set obligation named before work proceeds.
0354	sketch	authored	generated_draft	sketch is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the sketch obligation named before work proceeds.
0355	slice	authored	generated_draft	slice is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the slice obligation named before work proceeds.
0356	snapshot	authored	reviewed	A captured view of state at one moment.
0357	sparse vector	authored	generated_draft	sparse vector is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the sparse vector obligation named before work proceeds.
0358	stack item	authored	generated_draft	stack item is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the stack item obligation named before work proceeds.
0359	state	authored	reviewed	The currently true condition of a thing that can change over time.
0360	stream item	authored	generated_draft	stream item is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the stream item obligation named before work proceeds.
0361	string	authored	generated_draft	string is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the string obligation named before work proceeds.
0362	struct {Data}	authored	generated_draft	struct in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the struct obligation named before work proceeds.
0363	table {Data}	authored	generated_draft	table in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the table obligation named before work proceeds.
0364	tensor	authored	generated_draft	tensor is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the tensor obligation named before work proceeds.
0365	token {Data}	authored	generated_draft	token in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the token obligation named before work proceeds.
0366	tree node	authored	generated_draft	tree node is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the tree node obligation named before work proceeds.
0367	trie	authored	generated_draft	trie is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the trie obligation named before work proceeds.
0368	tuple {Data}	authored	generated_draft	tuple in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the tuple obligation named before work proceeds.
0369	vector	authored	generated_draft	vector is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the vector obligation named before work proceeds.
0370	view {Data}	authored	generated_draft	view in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the view obligation named before work proceeds.
0371	window	authored	generated_draft	window is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the window obligation named before work proceeds.

99.2 Entries

99.2.1 [0250] address

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: address is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the address obligation named before work proceeds.

Shadow: misusing address at rune 0250 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name address when the prompt needs this obligation made explicit: address is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the address obligation named before work proceeds.
• Ask the assistant to state the address shadow before proposing changes.

Example clause:

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

99.2.2 [0251] aggregate state

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: aggregate state is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the aggregate state obligation named before work proceeds.

Shadow: misusing aggregate state at rune 0251 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name aggregate state when the prompt needs this obligation made explicit: aggregate state is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the aggregate state obligation named before work proceeds.
• Ask the assistant to state the aggregate state shadow before proposing changes.

Example clause:

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

99.2.3 [0252] array

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A contiguous ordered collection accessed by position.

Shadow: misusing array at rune 0252 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name array when the prompt needs this obligation made explicit: A contiguous ordered collection accessed by position.
• Ask the assistant to state the array shadow before proposing changes.

Example clause:

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

Pocket gloss: A contiguous ordered collection accessed by position.

99.2.4 [0253] bag

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: bag is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bag obligation named before work proceeds.

Shadow: misusing bag at rune 0253 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name bag when the prompt needs this obligation made explicit: bag is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bag obligation named before work proceeds.
• Ask the assistant to state the bag shadow before proposing changes.

Example clause:

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

99.2.5 [0254] binary blob

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: binary blob is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the binary blob obligation named before work proceeds.

Shadow: misusing binary blob at rune 0254 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name binary blob when the prompt needs this obligation made explicit: binary blob is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the binary blob obligation named before work proceeds.
• Ask the assistant to state the binary blob shadow before proposing changes.

Example clause:

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

99.2.6 [0255] bit

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: bit is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bit obligation named before work proceeds.

Shadow: misusing bit at rune 0255 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name bit when the prompt needs this obligation made explicit: bit is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bit obligation named before work proceeds.
• Ask the assistant to state the bit shadow before proposing changes.

Example clause:

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

99.2.7 [0256] bitmap

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: bitmap is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bitmap obligation named before work proceeds.

Shadow: misusing bitmap at rune 0256 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name bitmap when the prompt needs this obligation made explicit: bitmap is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bitmap obligation named before work proceeds.
• Ask the assistant to state the bitmap shadow before proposing changes.

Example clause:

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

99.2.8 [0257] blob

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: blob is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the blob obligation named before work proceeds.

Shadow: misusing blob at rune 0257 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name blob when the prompt needs this obligation made explicit: blob is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the blob obligation named before work proceeds.
• Ask the assistant to state the blob shadow before proposing changes.

Example clause:

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

99.2.9 [0258] block {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: block in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the block obligation named before work proceeds.

Shadow: misusing block at rune 0258 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name block when the prompt needs this obligation made explicit: block in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the block obligation named before work proceeds.
• Ask the assistant to state the block shadow before proposing changes.

Example clause:

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

99.2.10 [0259] Bloom filter

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: Bloom filter is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the Bloom filter obligation named before work proceeds.

Shadow: misusing Bloom filter at rune 0259 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name Bloom filter when the prompt needs this obligation made explicit: Bloom filter is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the Bloom filter obligation named before work proceeds.
• Ask the assistant to state the Bloom filter shadow before proposing changes.

Example clause:

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

99.2.11 [0260] body

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: body is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the body obligation named before work proceeds.

Shadow: misusing body at rune 0260 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name body when the prompt needs this obligation made explicit: body is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the body obligation named before work proceeds.
• Ask the assistant to state the body shadow before proposing changes.

Example clause:

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

99.2.12 [0261] book-keeping field

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: book-keeping field is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the book-keeping field obligation named before work proceeds.

Shadow: misusing book-keeping field at rune 0261 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name book-keeping field when the prompt needs this obligation made explicit: book-keeping field is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the book-keeping field obligation named before work proceeds.
• Ask the assistant to state the book-keeping field shadow before proposing changes.

Example clause:

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

99.2.13 [0262] bucket {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: bucket in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bucket obligation named before work proceeds.

Shadow: misusing bucket at rune 0262 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name bucket when the prompt needs this obligation made explicit: bucket in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the bucket obligation named before work proceeds.
• Ask the assistant to state the bucket shadow before proposing changes.

Example clause:

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

99.2.14 [0263] buffer

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A temporary holding area used to smooth movement, parsing, or I/O.

Shadow: misusing buffer at rune 0263 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name buffer when the prompt needs this obligation made explicit: A temporary holding area used to smooth movement, parsing, or I/O.
• Ask the assistant to state the buffer shadow before proposing changes.

Example clause:

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

Pocket gloss: A temporary holding area used to smooth movement, parsing, or I/O.

99.2.15 [0264] byte

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: byte is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the byte obligation named before work proceeds.

Shadow: misusing byte at rune 0264 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name byte when the prompt needs this obligation made explicit: byte is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the byte obligation named before work proceeds.
• Ask the assistant to state the byte shadow before proposing changes.

Example clause:

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

99.2.16 [0265] cache entry

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cache entry is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the cache entry obligation named before work proceeds.

Shadow: misusing cache entry at rune 0265 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name cache entry when the prompt needs this obligation made explicit: cache entry is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the cache entry obligation named before work proceeds.
• Ask the assistant to state the cache entry shadow before proposing changes.

Example clause:

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

99.2.17 [0266] canonical form {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: canonical form in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the canonical form obligation named before work proceeds.

Shadow: misusing canonical form at rune 0266 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name canonical form when the prompt needs this obligation made explicit: canonical form in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the canonical form obligation named before work proceeds.
• Ask the assistant to state the canonical form shadow before proposing changes.

Example clause:

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

99.2.18 [0267] cell

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cell is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the cell obligation named before work proceeds.

Shadow: misusing cell at rune 0267 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name cell when the prompt needs this obligation made explicit: cell is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the cell obligation named before work proceeds.
• Ask the assistant to state the cell shadow before proposing changes.

Example clause:

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

99.2.19 [0268] checksum

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A compact fingerprint used to detect accidental change.

Shadow: misusing checksum at rune 0268 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name checksum when the prompt needs this obligation made explicit: A compact fingerprint used to detect accidental change.
• Ask the assistant to state the checksum shadow before proposing changes.

Example clause:

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

Pocket gloss: A compact fingerprint used to detect accidental change.

99.2.20 [0269] chunk

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: chunk is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the chunk obligation named before work proceeds.

Shadow: misusing chunk at rune 0269 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name chunk when the prompt needs this obligation made explicit: chunk is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the chunk obligation named before work proceeds.
• Ask the assistant to state the chunk shadow before proposing changes.

Example clause:

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

99.2.21 [0270] column {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: column in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the column obligation named before work proceeds.

Shadow: misusing column at rune 0270 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name column when the prompt needs this obligation made explicit: column in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the column obligation named before work proceeds.
• Ask the assistant to state the column shadow before proposing changes.

Example clause:

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

99.2.22 [0271] composite value

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: composite value is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the composite value obligation named before work proceeds.

Shadow: misusing composite value at rune 0271 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name composite value when the prompt needs this obligation made explicit: composite value is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the composite value obligation named before work proceeds.
• Ask the assistant to state the composite value shadow before proposing changes.

Example clause:

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

99.2.23 [0272] config

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Declared settings that shape behavior without editing code.

Shadow: misusing config at rune 0272 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name config when the prompt needs this obligation made explicit: Declared settings that shape behavior without editing code.
• Ask the assistant to state the config shadow before proposing changes.

Example clause:

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

Pocket gloss: Declared settings that shape behavior without editing code.

99.2.24 [0273] constant pool

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: constant pool is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the constant pool obligation named before work proceeds.

Shadow: misusing constant pool at rune 0273 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name constant pool when the prompt needs this obligation made explicit: constant pool is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the constant pool obligation named before work proceeds.
• Ask the assistant to state the constant pool shadow before proposing changes.

Example clause:

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

99.2.25 [0274] content

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: content is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the content obligation named before work proceeds.

Shadow: misusing content at rune 0274 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name content when the prompt needs this obligation made explicit: content is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the content obligation named before work proceeds.
• Ask the assistant to state the content shadow before proposing changes.

Example clause:

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

99.2.26 [0275] context object

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: context object is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the context object obligation named before work proceeds.

Shadow: misusing context object at rune 0275 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name context object when the prompt needs this obligation made explicit: context object is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the context object obligation named before work proceeds.
• Ask the assistant to state the context object shadow before proposing changes.

Example clause:

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

99.2.27 [0276] cookie

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cookie is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the cookie obligation named before work proceeds.

Shadow: misusing cookie at rune 0276 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name cookie when the prompt needs this obligation made explicit: cookie is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the cookie obligation named before work proceeds.
• Ask the assistant to state the cookie shadow before proposing changes.

Example clause:

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

99.2.28 [0277] corpus

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: corpus is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the corpus obligation named before work proceeds.

Shadow: misusing corpus at rune 0277 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name corpus when the prompt needs this obligation made explicit: corpus is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the corpus obligation named before work proceeds.
• Ask the assistant to state the corpus shadow before proposing changes.

Example clause:

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

99.2.29 [0278] counter {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: counter in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the counter obligation named before work proceeds.

Shadow: misusing counter at rune 0278 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name counter when the prompt needs this obligation made explicit: counter in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the counter obligation named before work proceeds.
• Ask the assistant to state the counter shadow before proposing changes.

Example clause:

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

99.2.30 [0279] credential {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: credential in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the credential obligation named before work proceeds.

Shadow: misusing credential at rune 0279 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name credential when the prompt needs this obligation made explicit: credential in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the credential obligation named before work proceeds.
• Ask the assistant to state the credential shadow before proposing changes.

Example clause:

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

99.2.31 [0280] cursor {Data}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A movable pointer into a sequence or result set.

Shadow: misusing cursor at rune 0280 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name cursor when the prompt needs this obligation made explicit: A movable pointer into a sequence or result set.
• Ask the assistant to state the cursor shadow before proposing changes.

Example clause:

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

Pocket gloss: A movable pointer into a sequence or result set.

99.2.32 [0281] data frame

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: data frame is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the data frame obligation named before work proceeds.

Shadow: misusing data frame at rune 0281 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name data frame when the prompt needs this obligation made explicit: data frame is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the data frame obligation named before work proceeds.
• Ask the assistant to state the data frame shadow before proposing changes.

Example clause:

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

99.2.33 [0282] data point

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: data point is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the data point obligation named before work proceeds.

Shadow: misusing data point at rune 0282 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name data point when the prompt needs this obligation made explicit: data point is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the data point obligation named before work proceeds.
• Ask the assistant to state the data point shadow before proposing changes.

Example clause:

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

99.2.34 [0283] dataset

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: dataset is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the dataset obligation named before work proceeds.

Shadow: misusing dataset at rune 0283 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name dataset when the prompt needs this obligation made explicit: dataset is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the dataset obligation named before work proceeds.
• Ask the assistant to state the dataset shadow before proposing changes.

Example clause:

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

99.2.35 [0284] datum

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: datum is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the datum obligation named before work proceeds.

Shadow: misusing datum at rune 0284 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name datum when the prompt needs this obligation made explicit: datum is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the datum obligation named before work proceeds.
• Ask the assistant to state the datum shadow before proposing changes.

Example clause:

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

99.2.36 [0285] delta

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: delta is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the delta obligation named before work proceeds.

Shadow: misusing delta at rune 0285 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name delta when the prompt needs this obligation made explicit: delta is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the delta obligation named before work proceeds.
• Ask the assistant to state the delta shadow before proposing changes.

Example clause:

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

99.2.37 [0286] dense vector

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: dense vector is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the dense vector obligation named before work proceeds.

Shadow: misusing dense vector at rune 0286 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name dense vector when the prompt needs this obligation made explicit: dense vector is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the dense vector obligation named before work proceeds.
• Ask the assistant to state the dense vector shadow before proposing changes.

Example clause:

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

99.2.38 [0287] descriptor

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: descriptor is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the descriptor obligation named before work proceeds.

Shadow: misusing descriptor at rune 0287 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name descriptor when the prompt needs this obligation made explicit: descriptor is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the descriptor obligation named before work proceeds.
• Ask the assistant to state the descriptor shadow before proposing changes.

Example clause:

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

99.2.39 [0288] dictionary

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Keyed lookup structure for named values.

Shadow: misusing dictionary at rune 0288 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name dictionary when the prompt needs this obligation made explicit: Keyed lookup structure for named values.
• Ask the assistant to state the dictionary shadow before proposing changes.

Example clause:

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

Pocket gloss: Keyed lookup structure for named values.

99.2.40 [0289] digest {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: digest in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the digest obligation named before work proceeds.

Shadow: misusing digest at rune 0289 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name digest when the prompt needs this obligation made explicit: digest in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the digest obligation named before work proceeds.
• Ask the assistant to state the digest shadow before proposing changes.

Example clause:

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

99.2.41 [0290] document

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: document is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the document obligation named before work proceeds.

Shadow: misusing document at rune 0290 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name document when the prompt needs this obligation made explicit: document is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the document obligation named before work proceeds.
• Ask the assistant to state the document shadow before proposing changes.

Example clause:

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

99.2.42 [0291] edge {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: edge in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the edge obligation named before work proceeds.

Shadow: misusing edge at rune 0291 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name edge when the prompt needs this obligation made explicit: edge in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the edge obligation named before work proceeds.
• Ask the assistant to state the edge shadow before proposing changes.

Example clause:

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

99.2.43 [0292] element

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: element is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the element obligation named before work proceeds.

Shadow: misusing element at rune 0292 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name element when the prompt needs this obligation made explicit: element is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the element obligation named before work proceeds.
• Ask the assistant to state the element shadow before proposing changes.

Example clause:

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

99.2.44 [0293] embedding {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: embedding in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the embedding obligation named before work proceeds.

Shadow: misusing embedding at rune 0293 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name embedding when the prompt needs this obligation made explicit: embedding in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the embedding obligation named before work proceeds.
• Ask the assistant to state the embedding shadow before proposing changes.

Example clause:

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

99.2.45 [0294] entity

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A thing with stable identity that the system cares about.

Shadow: misusing entity at rune 0294 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name entity when the prompt needs this obligation made explicit: A thing with stable identity that the system cares about.
• Ask the assistant to state the entity shadow before proposing changes.

Example clause:

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

Pocket gloss: A thing with stable identity that the system cares about.

99.2.46 [0295] enum value

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: enum value is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the enum value obligation named before work proceeds.

Shadow: misusing enum value at rune 0295 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name enum value when the prompt needs this obligation made explicit: enum value is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the enum value obligation named before work proceeds.
• Ask the assistant to state the enum value shadow before proposing changes.

Example clause:

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

99.2.47 [0296] envelope

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: envelope is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the envelope obligation named before work proceeds.

Shadow: misusing envelope at rune 0296 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name envelope when the prompt needs this obligation made explicit: envelope is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the envelope obligation named before work proceeds.
• Ask the assistant to state the envelope shadow before proposing changes.

Example clause:

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

99.2.48 [0297] event

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A record of something that happened.

Shadow: misusing event at rune 0297 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name event when the prompt needs this obligation made explicit: A record of something that happened.
• Ask the assistant to state the event shadow before proposing changes.

Example clause:

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

Pocket gloss: A record of something that happened.

99.2.49 [0298] event log

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: History stored as events instead of overwritten final state.

Shadow: misusing event log at rune 0298 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name event log when the prompt needs this obligation made explicit: History stored as events instead of overwritten final state.
• Ask the assistant to state the event log shadow before proposing changes.

Example clause:

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

Pocket gloss: History stored as events instead of overwritten final state.

99.2.50 [0299] fact

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fact is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the fact obligation named before work proceeds.

Shadow: misusing fact at rune 0299 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name fact when the prompt needs this obligation made explicit: fact is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the fact obligation named before work proceeds.
• Ask the assistant to state the fact shadow before proposing changes.

Example clause:

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

99.2.51 [0300] feature

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: feature is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the feature obligation named before work proceeds.

Shadow: misusing feature at rune 0300 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name feature when the prompt needs this obligation made explicit: feature is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the feature obligation named before work proceeds.
• Ask the assistant to state the feature shadow before proposing changes.

Example clause:

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

99.2.52 [0301] field {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: field in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the field obligation named before work proceeds.

Shadow: misusing field at rune 0301 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name field when the prompt needs this obligation made explicit: field in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the field obligation named before work proceeds.
• 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.

99.2.53 [0302] fingerprint

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fingerprint is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the fingerprint obligation named before work proceeds.

Shadow: misusing fingerprint at rune 0302 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name fingerprint when the prompt needs this obligation made explicit: fingerprint is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the fingerprint obligation named before work proceeds.
• Ask the assistant to state the fingerprint shadow before proposing changes.

Example clause:

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

99.2.54 [0303] flag

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: flag is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the flag obligation named before work proceeds.

Shadow: misusing flag at rune 0303 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name flag when the prompt needs this obligation made explicit: flag is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the flag obligation named before work proceeds.
• Ask the assistant to state the flag shadow before proposing changes.

Example clause:

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

99.2.55 [0304] frame {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: frame in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the frame obligation named before work proceeds.

Shadow: misusing frame at rune 0304 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name frame when the prompt needs this obligation made explicit: frame in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the frame obligation named before work proceeds.
• Ask the assistant to state the frame shadow before proposing changes.

Example clause:

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

99.2.56 [0305] handle {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: handle in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the handle obligation named before work proceeds.

Shadow: misusing handle at rune 0305 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name handle when the prompt needs this obligation made explicit: handle in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the handle obligation named before work proceeds.
• Ask the assistant to state the handle shadow before proposing changes.

Example clause:

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

99.2.57 [0306] hash {Data}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A condensed fingerprint used for lookup, bucketing, or integrity checks.

Shadow: misusing hash at rune 0306 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name hash when the prompt needs this obligation made explicit: A condensed fingerprint used for lookup, bucketing, or integrity checks.
• Ask the assistant to state the hash shadow before proposing changes.

Example clause:

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

Pocket gloss: A condensed fingerprint used for lookup, bucketing, or integrity checks.

99.2.58 [0307] hash map

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: hash map is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the hash map obligation named before work proceeds.

Shadow: misusing hash map at rune 0307 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name hash map when the prompt needs this obligation made explicit: hash map is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the hash map obligation named before work proceeds.
• Ask the assistant to state the hash map shadow before proposing changes.

Example clause:

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

99.2.59 [0308] header

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: header is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the header obligation named before work proceeds.

Shadow: misusing header at rune 0308 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name header when the prompt needs this obligation made explicit: header is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the header obligation named before work proceeds.
• Ask the assistant to state the header shadow before proposing changes.

Example clause:

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

99.2.60 [0309] heap record

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: heap record is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the heap record obligation named before work proceeds.

Shadow: misusing heap record at rune 0309 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name heap record when the prompt needs this obligation made explicit: heap record is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the heap record obligation named before work proceeds.
• Ask the assistant to state the heap record shadow before proposing changes.

Example clause:

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

99.2.61 [0310] index {Data}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: An access structure that trades space and write cost for faster reads.

Shadow: misusing index at rune 0310 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name index when the prompt needs this obligation made explicit: An access structure that trades space and write cost for faster reads.
• Ask the assistant to state the index shadow before proposing changes.

Example clause:

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

Pocket gloss: An access structure that trades space and write cost for faster reads.

99.2.62 [0311] index key

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: index key is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the index key obligation named before work proceeds.

Shadow: misusing index key at rune 0311 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name index key when the prompt needs this obligation made explicit: index key is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the index key obligation named before work proceeds.
• Ask the assistant to state the index key shadow before proposing changes.

Example clause:

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

99.2.63 [0312] item

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: item is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the item obligation named before work proceeds.

Shadow: misusing item at rune 0312 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name item when the prompt needs this obligation made explicit: item is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the item obligation named before work proceeds.
• Ask the assistant to state the item shadow before proposing changes.

Example clause:

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

99.2.64 [0313] iterator

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: iterator is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the iterator obligation named before work proceeds.

Shadow: misusing iterator at rune 0313 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name iterator when the prompt needs this obligation made explicit: iterator is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the iterator obligation named before work proceeds.
• Ask the assistant to state the iterator shadow before proposing changes.

Example clause:

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

99.2.65 [0314] journal

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: journal is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the journal obligation named before work proceeds.

Shadow: misusing journal at rune 0314 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name journal when the prompt needs this obligation made explicit: journal is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the journal obligation named before work proceeds.
• Ask the assistant to state the journal shadow before proposing changes.

Example clause:

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

99.2.66 [0315] key {Data}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The field by which something is found or grouped.

Shadow: misusing key at rune 0315 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name key when the prompt needs this obligation made explicit: The field by which something is found or grouped.
• Ask the assistant to state the key shadow before proposing changes.

Example clause:

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

Pocket gloss: The field by which something is found or grouped.

99.2.67 [0316] key-value pair

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: key-value pair is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the key-value pair obligation named before work proceeds.

Shadow: misusing key-value pair at rune 0316 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name key-value pair when the prompt needs this obligation made explicit: key-value pair is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the key-value pair obligation named before work proceeds.
• Ask the assistant to state the key-value pair shadow before proposing changes.

Example clause:

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

99.2.68 [0317] ledger

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: ledger is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the ledger obligation named before work proceeds.

Shadow: misusing ledger at rune 0317 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name ledger when the prompt needs this obligation made explicit: ledger is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the ledger obligation named before work proceeds.
• Ask the assistant to state the ledger shadow before proposing changes.

Example clause:

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

99.2.69 [0318] list

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: list is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the list obligation named before work proceeds.

Shadow: misusing list at rune 0318 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name list when the prompt needs this obligation made explicit: list is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the list obligation named before work proceeds.
• Ask the assistant to state the list shadow before proposing changes.

Example clause:

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

99.2.70 [0319] literal value

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: literal value is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the literal value obligation named before work proceeds.

Shadow: misusing literal value at rune 0319 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name literal value when the prompt needs this obligation made explicit: literal value is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the literal value obligation named before work proceeds.
• Ask the assistant to state the literal value shadow before proposing changes.

Example clause:

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

99.2.71 [0320] map {Data}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Associative collection from keys to values.

Shadow: misusing map at rune 0320 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name map when the prompt needs this obligation made explicit: Associative collection from keys to values.
• Ask the assistant to state the map shadow before proposing changes.

Example clause:

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

Pocket gloss: Associative collection from keys to values.

99.2.72 [0321] matrix

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: matrix is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the matrix obligation named before work proceeds.

Shadow: misusing matrix at rune 0321 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name matrix when the prompt needs this obligation made explicit: matrix is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the matrix obligation named before work proceeds.
• Ask the assistant to state the matrix shadow before proposing changes.

Example clause:

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

99.2.73 [0322] message

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A discrete packet of meaning sent between parts.

Shadow: misusing message at rune 0322 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name message when the prompt needs this obligation made explicit: A discrete packet of meaning sent between parts.
• Ask the assistant to state the message shadow before proposing changes.

Example clause:

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

Pocket gloss: A discrete packet of meaning sent between parts.

99.2.74 [0323] metadata

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: metadata is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the metadata obligation named before work proceeds.

Shadow: misusing metadata at rune 0323 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name metadata when the prompt needs this obligation made explicit: metadata is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the metadata obligation named before work proceeds.
• Ask the assistant to state the metadata shadow before proposing changes.

Example clause:

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

99.2.75 [0324] model {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: model in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the model obligation named before work proceeds.

Shadow: misusing model at rune 0324 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name model when the prompt needs this obligation made explicit: model in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the model obligation named before work proceeds.
• Ask the assistant to state the model shadow before proposing changes.

Example clause:

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

99.2.76 [0325] multimap

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: multimap is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the multimap obligation named before work proceeds.

Shadow: misusing multimap at rune 0325 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name multimap when the prompt needs this obligation made explicit: multimap is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the multimap obligation named before work proceeds.
• Ask the assistant to state the multimap shadow before proposing changes.

Example clause:

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

99.2.77 [0326] node {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: node in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the node obligation named before work proceeds.

Shadow: misusing node at rune 0326 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name node when the prompt needs this obligation made explicit: node in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the node obligation named before work proceeds.
• Ask the assistant to state the node shadow before proposing changes.

Example clause:

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

99.2.78 [0327] null

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: null is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the null obligation named before work proceeds.

Shadow: misusing null at rune 0327 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name null when the prompt needs this obligation made explicit: null is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the null obligation named before work proceeds.
• Ask the assistant to state the null shadow before proposing changes.

Example clause:

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

99.2.79 [0328] object state

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: object state is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the object state obligation named before work proceeds.

Shadow: misusing object state at rune 0328 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name object state when the prompt needs this obligation made explicit: object state is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the object state obligation named before work proceeds.
• Ask the assistant to state the object state shadow before proposing changes.

Example clause:

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

99.2.80 [0329] offset

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: offset is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the offset obligation named before work proceeds.

Shadow: misusing offset at rune 0329 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name offset when the prompt needs this obligation made explicit: offset is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the offset obligation named before work proceeds.
• Ask the assistant to state the offset shadow before proposing changes.

Example clause:

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

99.2.81 [0330] page {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: page in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the page obligation named before work proceeds.

Shadow: misusing page at rune 0330 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name page when the prompt needs this obligation made explicit: page in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the page obligation named before work proceeds.
• Ask the assistant to state the page shadow before proposing changes.

Example clause:

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

99.2.82 [0331] pair

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: pair is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the pair obligation named before work proceeds.

Shadow: misusing pair at rune 0331 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name pair when the prompt needs this obligation made explicit: pair is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the pair obligation named before work proceeds.
• Ask the assistant to state the pair shadow before proposing changes.

Example clause:

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

99.2.83 [0332] payload

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: payload is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the payload obligation named before work proceeds.

Shadow: misusing payload at rune 0332 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name payload when the prompt needs this obligation made explicit: payload is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the payload obligation named before work proceeds.
• Ask the assistant to state the payload shadow before proposing changes.

Example clause:

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

99.2.84 [0333] pointer {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: pointer in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the pointer obligation named before work proceeds.

Shadow: misusing pointer at rune 0333 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name pointer when the prompt needs this obligation made explicit: pointer in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the pointer obligation named before work proceeds.
• Ask the assistant to state the pointer shadow before proposing changes.

Example clause:

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

99.2.85 [0334] pool

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: pool is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the pool obligation named before work proceeds.

Shadow: misusing pool at rune 0334 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name pool when the prompt needs this obligation made explicit: pool is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the pool obligation named before work proceeds.
• Ask the assistant to state the pool shadow before proposing changes.

Example clause:

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

99.2.86 [0335] property {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: property in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the property obligation named before work proceeds.

Shadow: misusing property at rune 0335 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name property when the prompt needs this obligation made explicit: property in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the property obligation named before work proceeds.
• 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.

99.2.87 [0336] queue element

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: queue element is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the queue element obligation named before work proceeds.

Shadow: misusing queue element at rune 0336 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name queue element when the prompt needs this obligation made explicit: queue element is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the queue element obligation named before work proceeds.
• Ask the assistant to state the queue element shadow before proposing changes.

Example clause:

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

99.2.88 [0337] range

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: range is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the range obligation named before work proceeds.

Shadow: misusing range at rune 0337 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name range when the prompt needs this obligation made explicit: range is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the range obligation named before work proceeds.
• Ask the assistant to state the range shadow before proposing changes.

Example clause:

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

99.2.89 [0338] record {Data}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A row-like bundle of named fields describing one thing.

Shadow: misusing record at rune 0338 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name record when the prompt needs this obligation made explicit: A row-like bundle of named fields describing one thing.
• 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.

Pocket gloss: A row-like bundle of named fields describing one thing.

99.2.90 [0339] reference {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: reference in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the reference obligation named before work proceeds.

Shadow: misusing reference at rune 0339 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name reference when the prompt needs this obligation made explicit: reference in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the reference obligation named before work proceeds.
• 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.

99.2.91 [0340] relation {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: relation in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the relation obligation named before work proceeds.

Shadow: misusing relation at rune 0340 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name relation when the prompt needs this obligation made explicit: relation in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the relation obligation named before work proceeds.
• Ask the assistant to state the relation shadow before proposing changes.

Example clause:

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

99.2.92 [0341] representation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: representation is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the representation obligation named before work proceeds.

Shadow: misusing representation at rune 0341 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name representation when the prompt needs this obligation made explicit: representation is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the representation obligation named before work proceeds.
• Ask the assistant to state the representation shadow before proposing changes.

Example clause:

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

99.2.93 [0342] resource

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: resource is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the resource obligation named before work proceeds.

Shadow: misusing resource at rune 0342 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name resource when the prompt needs this obligation made explicit: resource is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the resource obligation named before work proceeds.
• Ask the assistant to state the resource shadow before proposing changes.

Example clause:

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

99.2.94 [0343] revision {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: revision in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the revision obligation named before work proceeds.

Shadow: misusing revision at rune 0343 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name revision when the prompt needs this obligation made explicit: revision in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the revision obligation named before work proceeds.
• Ask the assistant to state the revision shadow before proposing changes.

Example clause:

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

99.2.95 [0344] ring buffer

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: ring buffer is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the ring buffer obligation named before work proceeds.

Shadow: misusing ring buffer at rune 0344 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name ring buffer when the prompt needs this obligation made explicit: ring buffer is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the ring buffer obligation named before work proceeds.
• Ask the assistant to state the ring buffer shadow before proposing changes.

Example clause:

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

99.2.96 [0345] row {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: row in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the row obligation named before work proceeds.

Shadow: misusing row at rune 0345 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name row when the prompt needs this obligation made explicit: row in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the row obligation named before work proceeds.
• Ask the assistant to state the row shadow before proposing changes.

Example clause:

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

99.2.97 [0346] scalar

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: scalar is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the scalar obligation named before work proceeds.

Shadow: misusing scalar at rune 0346 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name scalar when the prompt needs this obligation made explicit: scalar is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the scalar obligation named before work proceeds.
• Ask the assistant to state the scalar shadow before proposing changes.

Example clause:

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

99.2.98 [0347] schema {Data}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: The declared shape of stored meaning.

Shadow: drift, silent coercion, and backward-incompatible surprise.

Prompt uses:

• Name schema when the prompt needs this obligation made explicit: The declared shape of stored meaning.
• Ask the assistant to state the schema shadow before proposing changes.

Example clause:

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

Pocket gloss: The declared shape of stored meaning.

99.2.99 [0348] secret {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: secret in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the secret obligation named before work proceeds.

Shadow: misusing secret at rune 0348 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name secret when the prompt needs this obligation made explicit: secret in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the secret obligation named before work proceeds.
• Ask the assistant to state the secret shadow before proposing changes.

Example clause:

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

99.2.100 [0349] segment {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: segment in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the segment obligation named before work proceeds.

Shadow: misusing segment at rune 0349 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name segment when the prompt needs this obligation made explicit: segment in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the segment obligation named before work proceeds.
• Ask the assistant to state the segment shadow before proposing changes.

Example clause:

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

99.2.101 [0350] sequence

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sequence is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the sequence obligation named before work proceeds.

Shadow: misusing sequence at rune 0350 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name sequence when the prompt needs this obligation made explicit: sequence is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the sequence obligation named before work proceeds.
• Ask the assistant to state the sequence shadow before proposing changes.

Example clause:

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

99.2.102 [0351] series

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: series is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the series obligation named before work proceeds.

Shadow: misusing series at rune 0351 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name series when the prompt needs this obligation made explicit: series is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the series obligation named before work proceeds.
• Ask the assistant to state the series shadow before proposing changes.

Example clause:

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

99.2.103 [0352] session

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: session is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the session obligation named before work proceeds.

Shadow: misusing session at rune 0352 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name session when the prompt needs this obligation made explicit: session is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the session obligation named before work proceeds.
• Ask the assistant to state the session shadow before proposing changes.

Example clause:

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

99.2.104 [0353] set

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: set is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the set obligation named before work proceeds.

Shadow: misusing set at rune 0353 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name set when the prompt needs this obligation made explicit: set is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the set obligation named before work proceeds.
• Ask the assistant to state the set shadow before proposing changes.

Example clause:

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

99.2.105 [0354] sketch

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sketch is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the sketch obligation named before work proceeds.

Shadow: misusing sketch at rune 0354 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name sketch when the prompt needs this obligation made explicit: sketch is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the sketch obligation named before work proceeds.
• Ask the assistant to state the sketch shadow before proposing changes.

Example clause:

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

99.2.106 [0355] slice

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: slice is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the slice obligation named before work proceeds.

Shadow: misusing slice at rune 0355 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name slice when the prompt needs this obligation made explicit: slice is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the slice obligation named before work proceeds.
• Ask the assistant to state the slice shadow before proposing changes.

Example clause:

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

99.2.107 [0356] snapshot

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A captured view of state at one moment.

Shadow: misusing snapshot at rune 0356 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name snapshot when the prompt needs this obligation made explicit: A captured view of state at one moment.
• Ask the assistant to state the snapshot shadow before proposing changes.

Example clause:

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

Pocket gloss: A captured view of state at one moment.

99.2.108 [0357] sparse vector

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sparse vector is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the sparse vector obligation named before work proceeds.

Shadow: misusing sparse vector at rune 0357 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name sparse vector when the prompt needs this obligation made explicit: sparse vector is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the sparse vector obligation named before work proceeds.
• Ask the assistant to state the sparse vector shadow before proposing changes.

Example clause:

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

99.2.109 [0358] stack item

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stack item is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the stack item obligation named before work proceeds.

Shadow: misusing stack item at rune 0358 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name stack item when the prompt needs this obligation made explicit: stack item is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the stack item obligation named before work proceeds.
• Ask the assistant to state the stack item shadow before proposing changes.

Example clause:

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

99.2.110 [0359] state

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The currently true condition of a thing that can change over time.

Shadow: misusing state at rune 0359 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name state when the prompt needs this obligation made explicit: The currently true condition of a thing that can change over time.
• Ask the assistant to state the state shadow before proposing changes.

Example clause:

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

Pocket gloss: The currently true condition of a thing that can change over time.

99.2.111 [0360] stream item

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stream item is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the stream item obligation named before work proceeds.

Shadow: misusing stream item at rune 0360 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name stream item when the prompt needs this obligation made explicit: stream item is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the stream item obligation named before work proceeds.
• Ask the assistant to state the stream item shadow before proposing changes.

Example clause:

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

99.2.112 [0361] string

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: string is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the string obligation named before work proceeds.

Shadow: misusing string at rune 0361 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name string when the prompt needs this obligation made explicit: string is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the string obligation named before work proceeds.
• Ask the assistant to state the string shadow before proposing changes.

Example clause:

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

99.2.113 [0362] struct {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: struct in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the struct obligation named before work proceeds.

Shadow: misusing struct at rune 0362 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name struct when the prompt needs this obligation made explicit: struct in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the struct obligation named before work proceeds.
• 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.

99.2.114 [0363] table {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: table in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the table obligation named before work proceeds.

Shadow: misusing table at rune 0363 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name table when the prompt needs this obligation made explicit: table in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the table obligation named before work proceeds.
• Ask the assistant to state the table shadow before proposing changes.

Example clause:

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

99.2.115 [0364] tensor

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: tensor is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the tensor obligation named before work proceeds.

Shadow: misusing tensor at rune 0364 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name tensor when the prompt needs this obligation made explicit: tensor is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the tensor obligation named before work proceeds.
• Ask the assistant to state the tensor shadow before proposing changes.

Example clause:

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

99.2.116 [0365] token {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: token in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the token obligation named before work proceeds.

Shadow: misusing token at rune 0365 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name token when the prompt needs this obligation made explicit: token in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the token obligation named before work proceeds.
• 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.

99.2.117 [0366] tree node

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: tree node is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the tree node obligation named before work proceeds.

Shadow: misusing tree node at rune 0366 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name tree node when the prompt needs this obligation made explicit: tree node is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the tree node obligation named before work proceeds.
• Ask the assistant to state the tree node shadow before proposing changes.

Example clause:

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

99.2.118 [0367] trie

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: trie is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the trie obligation named before work proceeds.

Shadow: misusing trie at rune 0367 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name trie when the prompt needs this obligation made explicit: trie is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the trie obligation named before work proceeds.
• Ask the assistant to state the trie shadow before proposing changes.

Example clause:

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

99.2.119 [0368] tuple {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: tuple in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the tuple obligation named before work proceeds.

Shadow: misusing tuple at rune 0368 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name tuple when the prompt needs this obligation made explicit: tuple in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the tuple obligation named before work proceeds.
• 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.

99.2.120 [0369] vector

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: vector is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the vector obligation named before work proceeds.

Shadow: misusing vector at rune 0369 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name vector when the prompt needs this obligation made explicit: vector is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the vector obligation named before work proceeds.
• Ask the assistant to state the vector shadow before proposing changes.

Example clause:

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

99.2.121 [0370] view {Data}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: view in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the view obligation named before work proceeds.

Shadow: misusing view at rune 0370 in the Data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name view when the prompt needs this obligation made explicit: view in its Data sense is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the view obligation named before work proceeds.
• Ask the assistant to state the view shadow before proposing changes.

Example clause:

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

99.2.122 [0371] window

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: window is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the window obligation named before work proceeds.

Shadow: misusing window at rune 0371 in the data lane can let stored shape can diverge from the world it claims to model; verify by requiring the caster to state invariants, null behavior, and compatibility expectations.

Prompt uses:

• Name window when the prompt needs this obligation made explicit: window is a data and state rune for control shape, identity, lifecycle, and representation drift; use it when the artifact needs the window obligation named before work proceeds.
• Ask the assistant to state the window shadow before proposing changes.

Example clause:

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