104  Databases, Persistence, and Time-Binding Words

105 Databases, Persistence, and Time-Binding Words

Range: 0887-0968.

105.1 Completion

Status	Count
authored	82

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

Sigil	Term	Completion	Semantic	Summary
0887	ACID	authored	reviewed	The classic four-part law of transactional storage: atomicity, consistency, isolation, durability.
0888	append-only log	authored	generated_draft	append-only log is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the append-only log obligation named before work proceeds.
0889	archive table	authored	generated_draft	archive table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the archive table obligation named before work proceeds.
0890	audit trail	authored	generated_draft	audit trail is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the audit trail obligation named before work proceeds.
0891	B-tree	authored	generated_draft	B-tree is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the B-tree obligation named before work proceeds.
0892	backup	authored	reviewed	A restorable copy taken so loss is not final.
0893	base table	authored	generated_draft	base table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the base table obligation named before work proceeds.
0894	bitmap index	authored	generated_draft	bitmap index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the bitmap index obligation named before work proceeds.
0895	checkpoint	authored	generated_draft	checkpoint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the checkpoint obligation named before work proceeds.
0896	column {DB}	authored	generated_draft	column in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the column obligation named before work proceeds.
0897	column store	authored	generated_draft	column store is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the column store obligation named before work proceeds.
0898	commit {DB}	authored	reviewed	The moment a proposed change becomes durable history. Shadow: writing too early, before the world is actually ready to carry the new truth.
0899	compaction {DB}	authored	generated_draft	compaction in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the compaction obligation named before work proceeds.
0900	conflict	authored	generated_draft	conflict is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the conflict obligation named before work proceeds.
0901	constraint {DB}	authored	reviewed	A rule the data is not allowed to violate.
0902	covering index	authored	generated_draft	covering index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the covering index obligation named before work proceeds.
0903	cursor {DB}	authored	generated_draft	cursor in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the cursor obligation named before work proceeds.
0904	data lake	authored	generated_draft	data lake is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the data lake obligation named before work proceeds.
0905	data warehouse	authored	generated_draft	data warehouse is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the data warehouse obligation named before work proceeds.
0906	database	authored	generated_draft	database is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the database obligation named before work proceeds.
0907	deadlock {DB}	authored	generated_draft	deadlock in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the deadlock obligation named before work proceeds.
0908	denormalization	authored	generated_draft	denormalization is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the denormalization obligation named before work proceeds.
0909	dimension table	authored	generated_draft	dimension table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the dimension table obligation named before work proceeds.
0910	durability	authored	generated_draft	durability is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the durability obligation named before work proceeds.
0911	durable log	authored	generated_draft	durable log is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the durable log obligation named before work proceeds.
0912	entity table	authored	generated_draft	entity table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the entity table obligation named before work proceeds.
0913	event store	authored	generated_draft	event store is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the event store obligation named before work proceeds.
0914	fact table	authored	generated_draft	fact table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the fact table obligation named before work proceeds.
0915	failover replica	authored	generated_draft	failover replica is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the failover replica obligation named before work proceeds.
0916	foreign key	authored	reviewed	A declared reference from one table to another table’s key.
0917	full table scan	authored	generated_draft	full table scan is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the full table scan obligation named before work proceeds.
0918	index {DB}	authored	reviewed	An access structure that speeds reads by paying extra write and space cost.
0919	index hint	authored	generated_draft	index hint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the index hint obligation named before work proceeds.
0920	index seek	authored	generated_draft	index seek is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the index seek obligation named before work proceeds.
0921	isolation level	authored	reviewed	The degree to which concurrent transactions are allowed to see one another’s motion.
0922	join {DB}	authored	generated_draft	join in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the join obligation named before work proceeds.
0923	keyspace	authored	generated_draft	keyspace is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the keyspace obligation named before work proceeds.
0924	LSM tree	authored	generated_draft	LSM tree is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the LSM tree obligation named before work proceeds.
0925	materialized view	authored	reviewed	A stored query result traded for cheaper future reads.
0926	migration	authored	reviewed	Stored reality changing shape without being lost. Good migrations are staged, inspectable, and reversible long enough to discover what the data actually contains.
0927	MVCC	authored	reviewed	Versioned rows that let readers and writers coexist more safely.
0928	nonclustered index	authored	generated_draft	nonclustered index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the nonclustered index obligation named before work proceeds.
0929	OLAP	authored	generated_draft	OLAP is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the OLAP obligation named before work proceeds.
0930	OLTP	authored	generated_draft	OLTP is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the OLTP obligation named before work proceeds.
0931	partition {DB}	authored	generated_draft	partition in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the partition obligation named before work proceeds.
0932	partition key	authored	generated_draft	partition key is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the partition key obligation named before work proceeds.
0933	primary key	authored	reviewed	The key that uniquely names one row inside its table.
0934	query plan	authored	reviewed	The strategy the database chose to answer the query.
0935	read committed	authored	generated_draft	read committed is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the read committed obligation named before work proceeds.
0936	read replica	authored	generated_draft	read replica is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the read replica obligation named before work proceeds.
0937	record lock	authored	generated_draft	record lock is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the record lock obligation named before work proceeds.
0938	redo log	authored	generated_draft	redo log is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the redo log obligation named before work proceeds.
0939	relation {DB}	authored	generated_draft	relation in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the relation obligation named before work proceeds.
0940	repeatable read	authored	generated_draft	repeatable read is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the repeatable read obligation named before work proceeds.
0941	replication lag	authored	generated_draft	replication lag is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the replication lag obligation named before work proceeds.
0942	retention	authored	generated_draft	retention is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the retention obligation named before work proceeds.
0943	rollback {DB}	authored	reviewed	Permission to retreat toward a previously trusted state. A system without rollback mistakes hope for safety.
0944	row {DB}	authored	generated_draft	row in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the row obligation named before work proceeds.
0945	row store	authored	generated_draft	row store is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the row store obligation named before work proceeds.
0946	savepoint	authored	generated_draft	savepoint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the savepoint obligation named before work proceeds.
0947	scan {DB}	authored	generated_draft	scan in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the scan obligation named before work proceeds.
0948	schema {DB}	authored	reviewed	The declared shape of database truth.
0949	secondary index	authored	generated_draft	secondary index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the secondary index obligation named before work proceeds.
0950	seed data	authored	generated_draft	seed data is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the seed data obligation named before work proceeds.
0951	serializable {DB}	authored	generated_draft	serializable in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the serializable obligation named before work proceeds.
0952	sharding	authored	generated_draft	sharding is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the sharding obligation named before work proceeds.
0953	snapshot isolation	authored	generated_draft	snapshot isolation is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the snapshot isolation obligation named before work proceeds.
0954	sort key	authored	generated_draft	sort key is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the sort key obligation named before work proceeds.
0955	stored procedure	authored	generated_draft	stored procedure is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the stored procedure obligation named before work proceeds.
0956	table {DB}	authored	generated_draft	table in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the table obligation named before work proceeds.
0957	table scan	authored	generated_draft	table scan is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the table scan obligation named before work proceeds.
0958	tenant isolation	authored	generated_draft	tenant isolation is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the tenant isolation obligation named before work proceeds.
0959	transaction	authored	reviewed	A unit of work meant to stand or fall together.
0960	TTL	authored	generated_draft	TTL is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the TTL obligation named before work proceeds.
0961	tuple {DB}	authored	generated_draft	tuple in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the tuple obligation named before work proceeds.
0962	unique constraint	authored	generated_draft	unique constraint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the unique constraint obligation named before work proceeds.
0963	upsert	authored	generated_draft	upsert is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the upsert obligation named before work proceeds.
0964	vacuum	authored	generated_draft	vacuum is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the vacuum obligation named before work proceeds.
0965	view {DB}	authored	generated_draft	view in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the view obligation named before work proceeds.
0966	WAL	authored	reviewed	Write-ahead log: history recorded before dirty pages reach their final home.
0967	warehouse model	authored	generated_draft	warehouse model is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the warehouse model obligation named before work proceeds.
0968	write skew {DB}	authored	generated_draft	write skew in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the write skew obligation named before work proceeds.

105.2 Entries

105.2.1 [0887] ACID

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The classic four-part law of transactional storage: atomicity, consistency, isolation, durability.

Shadow: misusing ACID at rune 0887 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name ACID when the prompt needs this obligation made explicit: The classic four-part law of transactional storage: atomicity, consistency, isolation, durability.
• Ask the assistant to state the ACID shadow before proposing changes.

Example clause:

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

Pocket gloss: The classic four-part law of transactional storage: atomicity, consistency, isolation, durability.

105.2.2 [0888] append-only log

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: append-only log is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the append-only log obligation named before work proceeds.

Shadow: misusing append-only log at rune 0888 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name append-only log when the prompt needs this obligation made explicit: append-only log is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the append-only log obligation named before work proceeds.
• Ask the assistant to state the append-only log shadow before proposing changes.

Example clause:

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

105.2.3 [0889] archive table

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: archive table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the archive table obligation named before work proceeds.

Shadow: misusing archive table at rune 0889 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name archive table when the prompt needs this obligation made explicit: archive table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the archive table obligation named before work proceeds.
• Ask the assistant to state the archive table shadow before proposing changes.

Example clause:

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

105.2.4 [0890] audit trail

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: audit trail is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the audit trail obligation named before work proceeds.

Shadow: misusing audit trail at rune 0890 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name audit trail when the prompt needs this obligation made explicit: audit trail is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the audit trail obligation named before work proceeds.
• Ask the assistant to state the audit trail shadow before proposing changes.

Example clause:

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

105.2.5 [0891] B-tree

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: B-tree is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the B-tree obligation named before work proceeds.

Shadow: misusing B-tree at rune 0891 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name B-tree when the prompt needs this obligation made explicit: B-tree is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the B-tree obligation named before work proceeds.
• Ask the assistant to state the B-tree shadow before proposing changes.

Example clause:

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

105.2.6 [0892] backup

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A restorable copy taken so loss is not final.

Shadow: misusing backup at rune 0892 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name backup when the prompt needs this obligation made explicit: A restorable copy taken so loss is not final.
• Ask the assistant to state the backup shadow before proposing changes.

Example clause:

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

Pocket gloss: A restorable copy taken so loss is not final.

105.2.7 [0893] base table

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: base table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the base table obligation named before work proceeds.

Shadow: misusing base table at rune 0893 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name base table when the prompt needs this obligation made explicit: base table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the base table obligation named before work proceeds.
• Ask the assistant to state the base table shadow before proposing changes.

Example clause:

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

105.2.8 [0894] bitmap index

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: bitmap index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the bitmap index obligation named before work proceeds.

Shadow: misusing bitmap index at rune 0894 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name bitmap index when the prompt needs this obligation made explicit: bitmap index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the bitmap index obligation named before work proceeds.
• Ask the assistant to state the bitmap index shadow before proposing changes.

Example clause:

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

105.2.9 [0895] checkpoint

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: checkpoint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the checkpoint obligation named before work proceeds.

Shadow: misusing checkpoint at rune 0895 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name checkpoint when the prompt needs this obligation made explicit: checkpoint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the checkpoint obligation named before work proceeds.
• Ask the assistant to state the checkpoint shadow before proposing changes.

Example clause:

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

105.2.10 [0896] column {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: column in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the column obligation named before work proceeds.

Shadow: misusing column at rune 0896 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name column when the prompt needs this obligation made explicit: column in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; 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.

105.2.11 [0897] column store

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: column store is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the column store obligation named before work proceeds.

Shadow: misusing column store at rune 0897 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name column store when the prompt needs this obligation made explicit: column store is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the column store obligation named before work proceeds.
• Ask the assistant to state the column store shadow before proposing changes.

Example clause:

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

105.2.12 [0898] commit {DB}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: The moment a proposed change becomes durable history.

Shadow: writing too early, before the world is actually ready to carry the new truth.

Prompt uses:

• Name commit when the prompt needs this obligation made explicit: The moment a proposed change becomes durable history.
• Ask the assistant to state the commit shadow before proposing changes.

Example clause:

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

Pocket gloss: Make a proposed change durable history.

105.2.13 [0899] compaction {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: compaction in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the compaction obligation named before work proceeds.

Shadow: misusing compaction at rune 0899 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name compaction when the prompt needs this obligation made explicit: compaction in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the compaction obligation named before work proceeds.
• Ask the assistant to state the compaction shadow before proposing changes.

Example clause:

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

105.2.14 [0900] conflict

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: conflict is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the conflict obligation named before work proceeds.

Shadow: misusing conflict at rune 0900 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name conflict when the prompt needs this obligation made explicit: conflict is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the conflict obligation named before work proceeds.
• Ask the assistant to state the conflict shadow before proposing changes.

Example clause:

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

105.2.15 [0901] constraint {DB}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A rule the data is not allowed to violate.

Shadow: misusing constraint at rune 0901 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name constraint when the prompt needs this obligation made explicit: A rule the data is not allowed to violate.
• Ask the assistant to state the constraint shadow before proposing changes.

Example clause:

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

Pocket gloss: A rule the data is not allowed to violate.

105.2.16 [0902] covering index

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: covering index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the covering index obligation named before work proceeds.

Shadow: misusing covering index at rune 0902 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name covering index when the prompt needs this obligation made explicit: covering index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the covering index obligation named before work proceeds.
• Ask the assistant to state the covering index shadow before proposing changes.

Example clause:

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

105.2.17 [0903] cursor {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cursor in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the cursor obligation named before work proceeds.

Shadow: misusing cursor at rune 0903 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name cursor when the prompt needs this obligation made explicit: cursor in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the cursor obligation named before work proceeds.
• 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.

105.2.18 [0904] data lake

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: data lake is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the data lake obligation named before work proceeds.

Shadow: misusing data lake at rune 0904 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name data lake when the prompt needs this obligation made explicit: data lake is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the data lake obligation named before work proceeds.
• Ask the assistant to state the data lake shadow before proposing changes.

Example clause:

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

105.2.19 [0905] data warehouse

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: data warehouse is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the data warehouse obligation named before work proceeds.

Shadow: misusing data warehouse at rune 0905 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name data warehouse when the prompt needs this obligation made explicit: data warehouse is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the data warehouse obligation named before work proceeds.
• Ask the assistant to state the data warehouse shadow before proposing changes.

Example clause:

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

105.2.20 [0906] database

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: database is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the database obligation named before work proceeds.

Shadow: misusing database at rune 0906 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name database when the prompt needs this obligation made explicit: database is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the database obligation named before work proceeds.
• Ask the assistant to state the database shadow before proposing changes.

Example clause:

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

105.2.21 [0907] deadlock {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: deadlock in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the deadlock obligation named before work proceeds.

Shadow: misusing deadlock at rune 0907 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name deadlock when the prompt needs this obligation made explicit: deadlock in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the deadlock obligation named before work proceeds.
• Ask the assistant to state the deadlock shadow before proposing changes.

Example clause:

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

105.2.22 [0908] denormalization

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: denormalization is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the denormalization obligation named before work proceeds.

Shadow: misusing denormalization at rune 0908 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name denormalization when the prompt needs this obligation made explicit: denormalization is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the denormalization obligation named before work proceeds.
• Ask the assistant to state the denormalization shadow before proposing changes.

Example clause:

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

105.2.23 [0909] dimension table

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: dimension table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the dimension table obligation named before work proceeds.

Shadow: misusing dimension table at rune 0909 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name dimension table when the prompt needs this obligation made explicit: dimension table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the dimension table obligation named before work proceeds.
• Ask the assistant to state the dimension table shadow before proposing changes.

Example clause:

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

105.2.24 [0910] durability

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: durability is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the durability obligation named before work proceeds.

Shadow: misusing durability at rune 0910 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name durability when the prompt needs this obligation made explicit: durability is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the durability obligation named before work proceeds.
• Ask the assistant to state the durability shadow before proposing changes.

Example clause:

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

105.2.25 [0911] durable log

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: durable log is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the durable log obligation named before work proceeds.

Shadow: misusing durable log at rune 0911 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name durable log when the prompt needs this obligation made explicit: durable log is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the durable log obligation named before work proceeds.
• Ask the assistant to state the durable log shadow before proposing changes.

Example clause:

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

105.2.26 [0912] entity table

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: entity table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the entity table obligation named before work proceeds.

Shadow: misusing entity table at rune 0912 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name entity table when the prompt needs this obligation made explicit: entity table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the entity table obligation named before work proceeds.
• Ask the assistant to state the entity table shadow before proposing changes.

Example clause:

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

105.2.27 [0913] event store

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: event store is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the event store obligation named before work proceeds.

Shadow: misusing event store at rune 0913 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name event store when the prompt needs this obligation made explicit: event store is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the event store obligation named before work proceeds.
• Ask the assistant to state the event store shadow before proposing changes.

Example clause:

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

105.2.28 [0914] fact table

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: fact table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the fact table obligation named before work proceeds.

Shadow: misusing fact table at rune 0914 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name fact table when the prompt needs this obligation made explicit: fact table is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the fact table obligation named before work proceeds.
• Ask the assistant to state the fact table shadow before proposing changes.

Example clause:

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

105.2.29 [0915] failover replica

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: failover replica is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the failover replica obligation named before work proceeds.

Shadow: misusing failover replica at rune 0915 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name failover replica when the prompt needs this obligation made explicit: failover replica is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the failover replica obligation named before work proceeds.
• Ask the assistant to state the failover replica shadow before proposing changes.

Example clause:

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

105.2.30 [0916] foreign key

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A declared reference from one table to another table’s key.

Shadow: misusing foreign key at rune 0916 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name foreign key when the prompt needs this obligation made explicit: A declared reference from one table to another table’s key.
• Ask the assistant to state the foreign key shadow before proposing changes.

Example clause:

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

Pocket gloss: A declared reference from one table to another table’s key.

105.2.31 [0917] full table scan

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: full table scan is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the full table scan obligation named before work proceeds.

Shadow: misusing full table scan at rune 0917 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name full table scan when the prompt needs this obligation made explicit: full table scan is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the full table scan obligation named before work proceeds.
• Ask the assistant to state the full table scan shadow before proposing changes.

Example clause:

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

105.2.32 [0918] index {DB}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: An access structure that speeds reads by paying extra write and space cost.

Shadow: misusing index at rune 0918 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name index when the prompt needs this obligation made explicit: An access structure that speeds reads by paying extra write and space cost.
• 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 speeds reads by paying extra write and space cost.

105.2.33 [0919] index hint

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: index hint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the index hint obligation named before work proceeds.

Shadow: misusing index hint at rune 0919 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name index hint when the prompt needs this obligation made explicit: index hint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the index hint obligation named before work proceeds.
• Ask the assistant to state the index hint shadow before proposing changes.

Example clause:

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

105.2.34 [0920] index seek

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: index seek is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the index seek obligation named before work proceeds.

Shadow: misusing index seek at rune 0920 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name index seek when the prompt needs this obligation made explicit: index seek is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the index seek obligation named before work proceeds.
• Ask the assistant to state the index seek shadow before proposing changes.

Example clause:

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

105.2.35 [0921] isolation level

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The degree to which concurrent transactions are allowed to see one another’s motion.

Shadow: misusing isolation level at rune 0921 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name isolation level when the prompt needs this obligation made explicit: The degree to which concurrent transactions are allowed to see one another’s motion.
• Ask the assistant to state the isolation level shadow before proposing changes.

Example clause:

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

Pocket gloss: The degree to which concurrent transactions are allowed to see one another’s motion.

105.2.36 [0922] join {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: join in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the join obligation named before work proceeds.

Shadow: misusing join at rune 0922 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name join when the prompt needs this obligation made explicit: join in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the join obligation named before work proceeds.
• Ask the assistant to state the join shadow before proposing changes.

Example clause:

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

105.2.37 [0923] keyspace

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: keyspace is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the keyspace obligation named before work proceeds.

Shadow: misusing keyspace at rune 0923 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name keyspace when the prompt needs this obligation made explicit: keyspace is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the keyspace obligation named before work proceeds.
• Ask the assistant to state the keyspace shadow before proposing changes.

Example clause:

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

105.2.38 [0924] LSM tree

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: LSM tree is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the LSM tree obligation named before work proceeds.

Shadow: misusing LSM tree at rune 0924 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name LSM tree when the prompt needs this obligation made explicit: LSM tree is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the LSM tree obligation named before work proceeds.
• Ask the assistant to state the LSM tree shadow before proposing changes.

Example clause:

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

105.2.39 [0925] materialized view

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A stored query result traded for cheaper future reads.

Shadow: misusing materialized view at rune 0925 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name materialized view when the prompt needs this obligation made explicit: A stored query result traded for cheaper future reads.
• Ask the assistant to state the materialized view shadow before proposing changes.

Example clause:

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

Pocket gloss: A stored query result traded for cheaper future reads.

105.2.40 [0926] migration

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Stored reality changing shape without being lost. Good migrations are staged, inspectable, and reversible long enough to discover what the data actually contains.

Shadow: when irreversible data movement starts before dirty cases and compatibility windows are known.

Prompt uses:

• Name migration when the prompt needs this obligation made explicit: Stored reality changing shape without being lost. Good migrations are staged, inspectable, and reversible long enough to discover what the data actually contains.
• Ask the assistant to state the migration shadow before proposing changes.

Example clause:

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

Pocket gloss: Change stored reality without losing it.

105.2.41 [0927] MVCC

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Versioned rows that let readers and writers coexist more safely.

Shadow: misusing MVCC at rune 0927 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name MVCC when the prompt needs this obligation made explicit: Versioned rows that let readers and writers coexist more safely.
• Ask the assistant to state the MVCC shadow before proposing changes.

Example clause:

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

Pocket gloss: Versioned rows that let readers and writers coexist more safely.

105.2.42 [0928] nonclustered index

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: nonclustered index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the nonclustered index obligation named before work proceeds.

Shadow: misusing nonclustered index at rune 0928 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name nonclustered index when the prompt needs this obligation made explicit: nonclustered index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the nonclustered index obligation named before work proceeds.
• Ask the assistant to state the nonclustered index shadow before proposing changes.

Example clause:

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

105.2.43 [0929] OLAP

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: OLAP is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the OLAP obligation named before work proceeds.

Shadow: misusing OLAP at rune 0929 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name OLAP when the prompt needs this obligation made explicit: OLAP is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the OLAP obligation named before work proceeds.
• Ask the assistant to state the OLAP shadow before proposing changes.

Example clause:

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

105.2.44 [0930] OLTP

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: OLTP is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the OLTP obligation named before work proceeds.

Shadow: misusing OLTP at rune 0930 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name OLTP when the prompt needs this obligation made explicit: OLTP is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the OLTP obligation named before work proceeds.
• Ask the assistant to state the OLTP shadow before proposing changes.

Example clause:

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

105.2.45 [0931] partition {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: partition in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the partition obligation named before work proceeds.

Shadow: misusing partition at rune 0931 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name partition when the prompt needs this obligation made explicit: partition in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the partition obligation named before work proceeds.
• Ask the assistant to state the partition shadow before proposing changes.

Example clause:

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

105.2.46 [0932] partition key

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: partition key is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the partition key obligation named before work proceeds.

Shadow: misusing partition key at rune 0932 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name partition key when the prompt needs this obligation made explicit: partition key is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the partition key obligation named before work proceeds.
• Ask the assistant to state the partition key shadow before proposing changes.

Example clause:

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

105.2.47 [0933] primary key

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The key that uniquely names one row inside its table.

Shadow: misusing primary key at rune 0933 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name primary key when the prompt needs this obligation made explicit: The key that uniquely names one row inside its table.
• Ask the assistant to state the primary key shadow before proposing changes.

Example clause:

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

Pocket gloss: The key that uniquely names one row inside its table.

105.2.48 [0934] query plan

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The strategy the database chose to answer the query.

Shadow: misusing query plan at rune 0934 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name query plan when the prompt needs this obligation made explicit: The strategy the database chose to answer the query.
• Ask the assistant to state the query plan shadow before proposing changes.

Example clause:

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

Pocket gloss: The strategy the database chose to answer the query.

105.2.49 [0935] read committed

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: read committed is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the read committed obligation named before work proceeds.

Shadow: misusing read committed at rune 0935 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name read committed when the prompt needs this obligation made explicit: read committed is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the read committed obligation named before work proceeds.
• Ask the assistant to state the read committed shadow before proposing changes.

Example clause:

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

105.2.50 [0936] read replica

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: read replica is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the read replica obligation named before work proceeds.

Shadow: misusing read replica at rune 0936 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name read replica when the prompt needs this obligation made explicit: read replica is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the read replica obligation named before work proceeds.
• Ask the assistant to state the read replica shadow before proposing changes.

Example clause:

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

105.2.51 [0937] record lock

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: record lock is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the record lock obligation named before work proceeds.

Shadow: misusing record lock at rune 0937 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name record lock when the prompt needs this obligation made explicit: record lock is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the record lock obligation named before work proceeds.
• Ask the assistant to state the record lock shadow before proposing changes.

Example clause:

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

105.2.52 [0938] redo log

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: redo log is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the redo log obligation named before work proceeds.

Shadow: misusing redo log at rune 0938 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name redo log when the prompt needs this obligation made explicit: redo log is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the redo log obligation named before work proceeds.
• Ask the assistant to state the redo log shadow before proposing changes.

Example clause:

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

105.2.53 [0939] relation {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: relation in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the relation obligation named before work proceeds.

Shadow: misusing relation at rune 0939 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name relation when the prompt needs this obligation made explicit: relation in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; 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.

105.2.54 [0940] repeatable read

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: repeatable read is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the repeatable read obligation named before work proceeds.

Shadow: misusing repeatable read at rune 0940 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name repeatable read when the prompt needs this obligation made explicit: repeatable read is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the repeatable read obligation named before work proceeds.
• Ask the assistant to state the repeatable read shadow before proposing changes.

Example clause:

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

105.2.55 [0941] replication lag

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: replication lag is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the replication lag obligation named before work proceeds.

Shadow: misusing replication lag at rune 0941 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name replication lag when the prompt needs this obligation made explicit: replication lag is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the replication lag obligation named before work proceeds.
• Ask the assistant to state the replication lag shadow before proposing changes.

Example clause:

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

105.2.56 [0942] retention

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: retention is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the retention obligation named before work proceeds.

Shadow: misusing retention at rune 0942 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name retention when the prompt needs this obligation made explicit: retention is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the retention obligation named before work proceeds.
• Ask the assistant to state the retention shadow before proposing changes.

Example clause:

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

105.2.57 [0943] rollback {DB}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: Permission to retreat toward a previously trusted state. A system without rollback mistakes hope for safety.

Shadow: when the rollback path exists on paper but cannot restore the actual user-visible state.

Prompt uses:

• Name rollback when the prompt needs this obligation made explicit: Permission to retreat toward a previously trusted state. A system without rollback mistakes hope for safety.
• Ask the assistant to state the rollback shadow before proposing changes.

Example clause:

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

Pocket gloss: Retreat toward a previously trusted state.

105.2.58 [0944] row {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: row in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the row obligation named before work proceeds.

Shadow: misusing row at rune 0944 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name row when the prompt needs this obligation made explicit: row in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; 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.

105.2.59 [0945] row store

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: row store is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the row store obligation named before work proceeds.

Shadow: misusing row store at rune 0945 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name row store when the prompt needs this obligation made explicit: row store is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the row store obligation named before work proceeds.
• Ask the assistant to state the row store shadow before proposing changes.

Example clause:

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

105.2.60 [0946] savepoint

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: savepoint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the savepoint obligation named before work proceeds.

Shadow: misusing savepoint at rune 0946 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name savepoint when the prompt needs this obligation made explicit: savepoint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the savepoint obligation named before work proceeds.
• Ask the assistant to state the savepoint shadow before proposing changes.

Example clause:

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

105.2.61 [0947] scan {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: scan in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the scan obligation named before work proceeds.

Shadow: misusing scan at rune 0947 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name scan when the prompt needs this obligation made explicit: scan in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the scan obligation named before work proceeds.
• Ask the assistant to state the scan shadow before proposing changes.

Example clause:

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

105.2.62 [0948] schema {DB}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The declared shape of database truth.

Shadow: misusing schema at rune 0948 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name schema when the prompt needs this obligation made explicit: The declared shape of database truth.
• 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 database truth.

105.2.63 [0949] secondary index

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: secondary index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the secondary index obligation named before work proceeds.

Shadow: misusing secondary index at rune 0949 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name secondary index when the prompt needs this obligation made explicit: secondary index is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the secondary index obligation named before work proceeds.
• Ask the assistant to state the secondary index shadow before proposing changes.

Example clause:

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

105.2.64 [0950] seed data

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: seed data is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the seed data obligation named before work proceeds.

Shadow: misusing seed data at rune 0950 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name seed data when the prompt needs this obligation made explicit: seed data is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the seed data obligation named before work proceeds.
• Ask the assistant to state the seed data shadow before proposing changes.

Example clause:

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

105.2.65 [0951] serializable {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: serializable in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the serializable obligation named before work proceeds.

Shadow: misusing serializable at rune 0951 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name serializable when the prompt needs this obligation made explicit: serializable in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the serializable obligation named before work proceeds.
• Ask the assistant to state the serializable shadow before proposing changes.

Example clause:

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

105.2.66 [0952] sharding

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sharding is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the sharding obligation named before work proceeds.

Shadow: misusing sharding at rune 0952 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name sharding when the prompt needs this obligation made explicit: sharding is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the sharding obligation named before work proceeds.
• Ask the assistant to state the sharding shadow before proposing changes.

Example clause:

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

105.2.67 [0953] snapshot isolation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: snapshot isolation is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the snapshot isolation obligation named before work proceeds.

Shadow: misusing snapshot isolation at rune 0953 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name snapshot isolation when the prompt needs this obligation made explicit: snapshot isolation is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the snapshot isolation obligation named before work proceeds.
• Ask the assistant to state the snapshot isolation shadow before proposing changes.

Example clause:

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

105.2.68 [0954] sort key

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: sort key is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the sort key obligation named before work proceeds.

Shadow: misusing sort key at rune 0954 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name sort key when the prompt needs this obligation made explicit: sort key is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the sort key obligation named before work proceeds.
• Ask the assistant to state the sort key shadow before proposing changes.

Example clause:

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

105.2.69 [0955] stored procedure

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: stored procedure is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the stored procedure obligation named before work proceeds.

Shadow: misusing stored procedure at rune 0955 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name stored procedure when the prompt needs this obligation made explicit: stored procedure is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the stored procedure obligation named before work proceeds.
• Ask the assistant to state the stored procedure shadow before proposing changes.

Example clause:

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

105.2.70 [0956] table {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: table in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the table obligation named before work proceeds.

Shadow: misusing table at rune 0956 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name table when the prompt needs this obligation made explicit: table in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; 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.

105.2.71 [0957] table scan

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: table scan is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the table scan obligation named before work proceeds.

Shadow: misusing table scan at rune 0957 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name table scan when the prompt needs this obligation made explicit: table scan is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the table scan obligation named before work proceeds.
• Ask the assistant to state the table scan shadow before proposing changes.

Example clause:

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

105.2.72 [0958] tenant isolation

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: tenant isolation is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the tenant isolation obligation named before work proceeds.

Shadow: misusing tenant isolation at rune 0958 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name tenant isolation when the prompt needs this obligation made explicit: tenant isolation is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the tenant isolation obligation named before work proceeds.
• Ask the assistant to state the tenant isolation shadow before proposing changes.

Example clause:

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

105.2.73 [0959] transaction

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A unit of work meant to stand or fall together.

Shadow: misusing transaction at rune 0959 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name transaction when the prompt needs this obligation made explicit: A unit of work meant to stand or fall together.
• Ask the assistant to state the transaction shadow before proposing changes.

Example clause:

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

Pocket gloss: A unit of work meant to stand or fall together.

105.2.74 [0960] TTL

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: TTL is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the TTL obligation named before work proceeds.

Shadow: misusing TTL at rune 0960 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name TTL when the prompt needs this obligation made explicit: TTL is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the TTL obligation named before work proceeds.
• Ask the assistant to state the TTL shadow before proposing changes.

Example clause:

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

105.2.75 [0961] tuple {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: tuple in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the tuple obligation named before work proceeds.

Shadow: misusing tuple at rune 0961 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name tuple when the prompt needs this obligation made explicit: tuple in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; 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.

105.2.76 [0962] unique constraint

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: unique constraint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the unique constraint obligation named before work proceeds.

Shadow: misusing unique constraint at rune 0962 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name unique constraint when the prompt needs this obligation made explicit: unique constraint is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the unique constraint obligation named before work proceeds.
• Ask the assistant to state the unique constraint shadow before proposing changes.

Example clause:

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

105.2.77 [0963] upsert

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: upsert is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the upsert obligation named before work proceeds.

Shadow: misusing upsert at rune 0963 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name upsert when the prompt needs this obligation made explicit: upsert is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the upsert obligation named before work proceeds.
• Ask the assistant to state the upsert shadow before proposing changes.

Example clause:

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

105.2.78 [0964] vacuum

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: vacuum is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the vacuum obligation named before work proceeds.

Shadow: misusing vacuum at rune 0964 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name vacuum when the prompt needs this obligation made explicit: vacuum is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the vacuum obligation named before work proceeds.
• Ask the assistant to state the vacuum shadow before proposing changes.

Example clause:

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

105.2.79 [0965] view {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: view in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the view obligation named before work proceeds.

Shadow: misusing view at rune 0965 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name view when the prompt needs this obligation made explicit: view in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; 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.

105.2.80 [0966] WAL

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Write-ahead log: history recorded before dirty pages reach their final home.

Shadow: misusing WAL at rune 0966 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name WAL when the prompt needs this obligation made explicit: Write-ahead log: history recorded before dirty pages reach their final home.
• Ask the assistant to state the WAL shadow before proposing changes.

Example clause:

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

Pocket gloss: Write-ahead log: history recorded before dirty pages reach their final home.

105.2.81 [0967] warehouse model

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: warehouse model is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the warehouse model obligation named before work proceeds.

Shadow: misusing warehouse model at rune 0967 in the database lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name warehouse model when the prompt needs this obligation made explicit: warehouse model is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the warehouse model obligation named before work proceeds.
• Ask the assistant to state the warehouse model shadow before proposing changes.

Example clause:

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

105.2.82 [0968] write skew {DB}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: write skew in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the write skew obligation named before work proceeds.

Shadow: misusing write skew at rune 0968 in the DB lane can let durability can preserve the wrong truth longer than code remembers; verify by requiring the caster to state isolation, migration, rollback, and validation queries.

Prompt uses:

• Name write skew when the prompt needs this obligation made explicit: write skew in its DB sense is a databases and persistence rune for bind durable state, transactions, migrations, and time to explicit rules; use it when the artifact needs the write skew obligation named before work proceeds.
• Ask the assistant to state the write skew shadow before proposing changes.

Example clause:

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