113  Compound Forms, Prefixes, Suffixes, and Naming Runes

114 Compound Forms, Prefixes, Suffixes, and Naming Runes

Range: 1583-1645.

114.1 Completion

Status Count
authored 63

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

Sigil Term Completion Semantic Summary
1583 -able authored generated_draft -able is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -able obligation named before work proceeds.
1584 -aware authored reviewed Marks that something notices the surrounding condition it names.
1585 -by-design authored generated_draft -by-design is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -by-design obligation named before work proceeds.
1586 -centric authored generated_draft -centric is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -centric obligation named before work proceeds.
1587 -complete authored generated_draft -complete is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -complete obligation named before work proceeds.
1588 -driven authored reviewed Signals that behavior is organized around events or causes.
1589 -first authored reviewed Declares priority or design center: security-first, API-first, offline-first.
1590 -free authored generated_draft -free is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -free obligation named before work proceeds.
1591 -friendly authored generated_draft -friendly is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -friendly obligation named before work proceeds.
1592 -hard authored generated_draft -hard is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -hard obligation named before work proceeds.
1593 -less authored generated_draft -less is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -less obligation named before work proceeds.
1594 -local authored generated_draft -local is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -local obligation named before work proceeds.
1595 -native authored generated_draft -native is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -native obligation named before work proceeds.
1596 -of-record authored generated_draft -of-record is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -of-record obligation named before work proceeds.
1597 -oriented authored generated_draft -oriented is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -oriented obligation named before work proceeds.
1598 -safe authored reviewed Asserts a protected behavior such as memory-safe or thread-safe.
1599 -sensitive authored generated_draft -sensitive is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -sensitive obligation named before work proceeds.
1600 -shaped authored generated_draft -shaped is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -shaped obligation named before work proceeds.
1601 -soft authored generated_draft -soft is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -soft obligation named before work proceeds.
1602 -tolerant authored generated_draft -tolerant is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -tolerant obligation named before work proceeds.
1603 -wide authored generated_draft -wide is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -wide obligation named before work proceeds.
1604 actor model authored generated_draft actor model is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the actor model obligation named before work proceeds.
1605 API-first authored reviewed Design the interface surface before the implementations behind it.
1606 append-only authored reviewed History grows by addition rather than mutation.
1607 best-effort authored generated_draft best-effort is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the best-effort obligation named before work proceeds.
1608 branch-free authored generated_draft branch-free is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the branch-free obligation named before work proceeds.
1609 cloud-native authored generated_draft cloud-native is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the cloud-native obligation named before work proceeds.
1610 command-query authored generated_draft command-query is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the command-query obligation named before work proceeds.
1611 control plane {Rune} authored generated_draft control plane in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the control plane obligation named before work proceeds.
1612 copy-on-write {Rune} authored generated_draft copy-on-write in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the copy-on-write obligation named before work proceeds.
1613 crash-only authored reviewed Only live briefly, start fast, and recover by restart rather than repair.
1614 data plane {Rune} authored generated_draft data plane in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the data plane obligation named before work proceeds.
1615 data-driven authored generated_draft data-driven is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the data-driven obligation named before work proceeds.
1616 default-deny authored reviewed Access is forbidden unless explicitly granted.
1617 edge-native authored generated_draft edge-native is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the edge-native obligation named before work proceeds.
1618 event-driven authored reviewed Action propagates from events rather than from direct polling or command loops.
1619 eventually consistent authored generated_draft eventually consistent is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the eventually consistent obligation named before work proceeds.
1620 fail-fast authored reviewed Abort early when assumptions break instead of smearing damage forward.
1621 first-class authored generated_draft first-class is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the first-class obligation named before work proceeds.
1622 hot path {Rune} authored generated_draft hot path in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the hot path obligation named before work proceeds.
1623 infrastructure-as-code authored reviewed Operational change expressed as reviewable source.
1624 least-authority authored generated_draft least-authority is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the least-authority obligation named before work proceeds.
1625 lock-free {Rune} authored generated_draft lock-free in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the lock-free obligation named before work proceeds.
1626 machine-readable authored reviewed Structured so software, not only humans, can read it reliably.
1627 memory-safe {Rune} authored generated_draft memory-safe in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the memory-safe obligation named before work proceeds.
1628 multi-tenant authored generated_draft multi-tenant is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the multi-tenant obligation named before work proceeds.
1629 negative cache authored generated_draft negative cache is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the negative cache obligation named before work proceeds.
1630 object-capability authored generated_draft object-capability is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the object-capability obligation named before work proceeds.
1631 offline-first {Rune} authored reviewed Designed to keep working with poor or absent connectivity.
1632 policy-as-code authored reviewed Policy declared as versioned, testable code.
1633 queue-backed authored generated_draft queue-backed is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the queue-backed obligation named before work proceeds.
1634 read path authored generated_draft read path is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the read path obligation named before work proceeds.
1635 read-through cache authored generated_draft read-through cache is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the read-through cache obligation named before work proceeds.
1636 real-time {Rune} authored generated_draft real-time in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the real-time obligation named before work proceeds.
1637 rule-based authored generated_draft rule-based is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the rule-based obligation named before work proceeds.
1638 side-effect-free {Rune} authored generated_draft side-effect-free in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the side-effect-free obligation named before work proceeds.
1639 single source of truth authored reviewed One canonical place others are expected to mirror.
1640 soft delete authored generated_draft soft delete is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the soft delete obligation named before work proceeds.
1641 statefulset authored generated_draft statefulset is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the statefulset obligation named before work proceeds.
1642 write path authored generated_draft write path is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the write path obligation named before work proceeds.
1643 write-through cache authored generated_draft write-through cache is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the write-through cache obligation named before work proceeds.
1644 zero-downtime authored reviewed Change introduced without taking the service dark.
1645 zero-knowledge authored generated_draft zero-knowledge is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the zero-knowledge obligation named before work proceeds.

114.2 Entries

114.2.1 [1583] -able

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -able is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -able obligation named before work proceeds.

Shadow: misusing -able at rune 1583 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -able when the prompt needs this obligation made explicit: -able is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -able obligation named before work proceeds.
  • Ask the assistant to state the -able shadow before proposing changes.

Example clause:

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

114.2.2 [1584] -aware

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Marks that something notices the surrounding condition it names.

Shadow: misusing -aware at rune 1584 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -aware when the prompt needs this obligation made explicit: Marks that something notices the surrounding condition it names.
  • Ask the assistant to state the -aware shadow before proposing changes.

Example clause:

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

Pocket gloss: Marks that something notices the surrounding condition it names.

114.2.3 [1585] -by-design

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -by-design is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -by-design obligation named before work proceeds.

Shadow: misusing -by-design at rune 1585 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -by-design when the prompt needs this obligation made explicit: -by-design is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -by-design obligation named before work proceeds.
  • Ask the assistant to state the -by-design shadow before proposing changes.

Example clause:

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

114.2.4 [1586] -centric

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -centric is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -centric obligation named before work proceeds.

Shadow: misusing -centric at rune 1586 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -centric when the prompt needs this obligation made explicit: -centric is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -centric obligation named before work proceeds.
  • Ask the assistant to state the -centric shadow before proposing changes.

Example clause:

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

114.2.5 [1587] -complete

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -complete is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -complete obligation named before work proceeds.

Shadow: misusing -complete at rune 1587 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -complete when the prompt needs this obligation made explicit: -complete is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -complete obligation named before work proceeds.
  • Ask the assistant to state the -complete shadow before proposing changes.

Example clause:

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

114.2.6 [1588] -driven

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Signals that behavior is organized around events or causes.

Shadow: misusing -driven at rune 1588 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -driven when the prompt needs this obligation made explicit: Signals that behavior is organized around events or causes.
  • Ask the assistant to state the -driven shadow before proposing changes.

Example clause:

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

Pocket gloss: Signals that behavior is organized around events or causes.

114.2.7 [1589] -first

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Declares priority or design center: security-first, API-first, offline-first.

Shadow: misusing -first at rune 1589 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -first when the prompt needs this obligation made explicit: Declares priority or design center: security-first, API-first, offline-first.
  • Ask the assistant to state the -first shadow before proposing changes.

Example clause:

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

Pocket gloss: Declares priority or design center: security-first, API-first, offline-first.

114.2.8 [1590] -free

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -free is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -free obligation named before work proceeds.

Shadow: misusing -free at rune 1590 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -free when the prompt needs this obligation made explicit: -free is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -free obligation named before work proceeds.
  • Ask the assistant to state the -free shadow before proposing changes.

Example clause:

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

114.2.9 [1591] -friendly

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -friendly is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -friendly obligation named before work proceeds.

Shadow: misusing -friendly at rune 1591 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -friendly when the prompt needs this obligation made explicit: -friendly is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -friendly obligation named before work proceeds.
  • Ask the assistant to state the -friendly shadow before proposing changes.

Example clause:

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

114.2.10 [1592] -hard

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -hard is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -hard obligation named before work proceeds.

Shadow: misusing -hard at rune 1592 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -hard when the prompt needs this obligation made explicit: -hard is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -hard obligation named before work proceeds.
  • Ask the assistant to state the -hard shadow before proposing changes.

Example clause:

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

114.2.11 [1593] -less

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -less is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -less obligation named before work proceeds.

Shadow: misusing -less at rune 1593 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -less when the prompt needs this obligation made explicit: -less is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -less obligation named before work proceeds.
  • Ask the assistant to state the -less shadow before proposing changes.

Example clause:

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

114.2.12 [1594] -local

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -local is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -local obligation named before work proceeds.

Shadow: misusing -local at rune 1594 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -local when the prompt needs this obligation made explicit: -local is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -local obligation named before work proceeds.
  • Ask the assistant to state the -local shadow before proposing changes.

Example clause:

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

114.2.13 [1595] -native

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -native is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -native obligation named before work proceeds.

Shadow: misusing -native at rune 1595 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -native when the prompt needs this obligation made explicit: -native is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -native obligation named before work proceeds.
  • Ask the assistant to state the -native shadow before proposing changes.

Example clause:

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

114.2.14 [1596] -of-record

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -of-record is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -of-record obligation named before work proceeds.

Shadow: misusing -of-record at rune 1596 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -of-record when the prompt needs this obligation made explicit: -of-record is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -of-record obligation named before work proceeds.
  • Ask the assistant to state the -of-record shadow before proposing changes.

Example clause:

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

114.2.15 [1597] -oriented

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -oriented is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -oriented obligation named before work proceeds.

Shadow: misusing -oriented at rune 1597 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -oriented when the prompt needs this obligation made explicit: -oriented is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -oriented obligation named before work proceeds.
  • Ask the assistant to state the -oriented shadow before proposing changes.

Example clause:

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

114.2.16 [1598] -safe

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Asserts a protected behavior such as memory-safe or thread-safe.

Shadow: misusing -safe at rune 1598 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -safe when the prompt needs this obligation made explicit: Asserts a protected behavior such as memory-safe or thread-safe.
  • Ask the assistant to state the -safe shadow before proposing changes.

Example clause:

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

Pocket gloss: Asserts a protected behavior such as memory-safe or thread-safe.

114.2.17 [1599] -sensitive

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -sensitive is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -sensitive obligation named before work proceeds.

Shadow: misusing -sensitive at rune 1599 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -sensitive when the prompt needs this obligation made explicit: -sensitive is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -sensitive obligation named before work proceeds.
  • Ask the assistant to state the -sensitive shadow before proposing changes.

Example clause:

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

114.2.18 [1600] -shaped

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -shaped is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -shaped obligation named before work proceeds.

Shadow: misusing -shaped at rune 1600 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -shaped when the prompt needs this obligation made explicit: -shaped is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -shaped obligation named before work proceeds.
  • Ask the assistant to state the -shaped shadow before proposing changes.

Example clause:

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

114.2.19 [1601] -soft

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -soft is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -soft obligation named before work proceeds.

Shadow: misusing -soft at rune 1601 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -soft when the prompt needs this obligation made explicit: -soft is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -soft obligation named before work proceeds.
  • Ask the assistant to state the -soft shadow before proposing changes.

Example clause:

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

114.2.20 [1602] -tolerant

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -tolerant is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -tolerant obligation named before work proceeds.

Shadow: misusing -tolerant at rune 1602 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -tolerant when the prompt needs this obligation made explicit: -tolerant is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -tolerant obligation named before work proceeds.
  • Ask the assistant to state the -tolerant shadow before proposing changes.

Example clause:

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

114.2.21 [1603] -wide

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: -wide is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -wide obligation named before work proceeds.

Shadow: misusing -wide at rune 1603 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name -wide when the prompt needs this obligation made explicit: -wide is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the -wide obligation named before work proceeds.
  • Ask the assistant to state the -wide shadow before proposing changes.

Example clause:

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

114.2.22 [1604] actor model

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: actor model is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the actor model obligation named before work proceeds.

Shadow: misusing actor model at rune 1604 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name actor model when the prompt needs this obligation made explicit: actor model is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the actor model obligation named before work proceeds.
  • Ask the assistant to state the actor model shadow before proposing changes.

Example clause:

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

114.2.23 [1605] API-first

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Design the interface surface before the implementations behind it.

Shadow: misusing API-first at rune 1605 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name API-first when the prompt needs this obligation made explicit: Design the interface surface before the implementations behind it.
  • Ask the assistant to state the API-first shadow before proposing changes.

Example clause:

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

Pocket gloss: Design the interface surface before the implementations behind it.

114.2.24 [1606] append-only

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: History grows by addition rather than mutation.

Shadow: misusing append-only at rune 1606 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name append-only when the prompt needs this obligation made explicit: History grows by addition rather than mutation.
  • Ask the assistant to state the append-only shadow before proposing changes.

Example clause:

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

Pocket gloss: History grows by addition rather than mutation.

114.2.25 [1607] best-effort

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: best-effort is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the best-effort obligation named before work proceeds.

Shadow: misusing best-effort at rune 1607 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name best-effort when the prompt needs this obligation made explicit: best-effort is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the best-effort obligation named before work proceeds.
  • Ask the assistant to state the best-effort shadow before proposing changes.

Example clause:

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

114.2.26 [1608] branch-free

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: branch-free is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the branch-free obligation named before work proceeds.

Shadow: misusing branch-free at rune 1608 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name branch-free when the prompt needs this obligation made explicit: branch-free is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the branch-free obligation named before work proceeds.
  • Ask the assistant to state the branch-free shadow before proposing changes.

Example clause:

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

114.2.27 [1609] cloud-native

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cloud-native is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the cloud-native obligation named before work proceeds.

Shadow: misusing cloud-native at rune 1609 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name cloud-native when the prompt needs this obligation made explicit: cloud-native is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the cloud-native obligation named before work proceeds.
  • Ask the assistant to state the cloud-native shadow before proposing changes.

Example clause:

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

114.2.28 [1610] command-query

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: command-query is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the command-query obligation named before work proceeds.

Shadow: misusing command-query at rune 1610 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name command-query when the prompt needs this obligation made explicit: command-query is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the command-query obligation named before work proceeds.
  • Ask the assistant to state the command-query shadow before proposing changes.

Example clause:

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

114.2.29 [1611] control plane {Rune}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: control plane in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the control plane obligation named before work proceeds.

Shadow: misusing control plane at rune 1611 in the Rune lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name control plane when the prompt needs this obligation made explicit: control plane in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the control plane obligation named before work proceeds.
  • Ask the assistant to state the control plane shadow before proposing changes.

Example clause:

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

114.2.30 [1612] copy-on-write {Rune}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: copy-on-write in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the copy-on-write obligation named before work proceeds.

Shadow: misusing copy-on-write at rune 1612 in the Rune lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name copy-on-write when the prompt needs this obligation made explicit: copy-on-write in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the copy-on-write obligation named before work proceeds.
  • Ask the assistant to state the copy-on-write shadow before proposing changes.

Example clause:

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

114.2.31 [1613] crash-only

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Only live briefly, start fast, and recover by restart rather than repair.

Shadow: misusing crash-only at rune 1613 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name crash-only when the prompt needs this obligation made explicit: Only live briefly, start fast, and recover by restart rather than repair.
  • Ask the assistant to state the crash-only shadow before proposing changes.

Example clause:

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

Pocket gloss: Only live briefly, start fast, and recover by restart rather than repair.

114.2.32 [1614] data plane {Rune}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: data plane in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the data plane obligation named before work proceeds.

Shadow: misusing data plane at rune 1614 in the Rune lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name data plane when the prompt needs this obligation made explicit: data plane in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the data plane obligation named before work proceeds.
  • Ask the assistant to state the data plane shadow before proposing changes.

Example clause:

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

114.2.33 [1615] data-driven

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: data-driven is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the data-driven obligation named before work proceeds.

Shadow: misusing data-driven at rune 1615 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name data-driven when the prompt needs this obligation made explicit: data-driven is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the data-driven obligation named before work proceeds.
  • Ask the assistant to state the data-driven shadow before proposing changes.

Example clause:

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

114.2.34 [1616] default-deny

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Access is forbidden unless explicitly granted.

Shadow: misusing default-deny at rune 1616 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name default-deny when the prompt needs this obligation made explicit: Access is forbidden unless explicitly granted.
  • Ask the assistant to state the default-deny shadow before proposing changes.

Example clause:

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

Pocket gloss: Access is forbidden unless explicitly granted.

114.2.35 [1617] edge-native

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: edge-native is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the edge-native obligation named before work proceeds.

Shadow: misusing edge-native at rune 1617 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name edge-native when the prompt needs this obligation made explicit: edge-native is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the edge-native obligation named before work proceeds.
  • Ask the assistant to state the edge-native shadow before proposing changes.

Example clause:

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

114.2.36 [1618] event-driven

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Action propagates from events rather than from direct polling or command loops.

Shadow: misusing event-driven at rune 1618 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name event-driven when the prompt needs this obligation made explicit: Action propagates from events rather than from direct polling or command loops.
  • Ask the assistant to state the event-driven shadow before proposing changes.

Example clause:

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

Pocket gloss: Action propagates from events rather than from direct polling or command loops.

114.2.37 [1619] eventually consistent

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: eventually consistent is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the eventually consistent obligation named before work proceeds.

Shadow: misusing eventually consistent at rune 1619 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name eventually consistent when the prompt needs this obligation made explicit: eventually consistent is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the eventually consistent obligation named before work proceeds.
  • Ask the assistant to state the eventually consistent shadow before proposing changes.

Example clause:

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

114.2.38 [1620] fail-fast

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Abort early when assumptions break instead of smearing damage forward.

Shadow: misusing fail-fast at rune 1620 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name fail-fast when the prompt needs this obligation made explicit: Abort early when assumptions break instead of smearing damage forward.
  • Ask the assistant to state the fail-fast shadow before proposing changes.

Example clause:

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

Pocket gloss: Abort early when assumptions break instead of smearing damage forward.

114.2.39 [1621] first-class

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: first-class is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the first-class obligation named before work proceeds.

Shadow: misusing first-class at rune 1621 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name first-class when the prompt needs this obligation made explicit: first-class is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the first-class obligation named before work proceeds.
  • Ask the assistant to state the first-class shadow before proposing changes.

Example clause:

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

114.2.40 [1622] hot path {Rune}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: hot path in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the hot path obligation named before work proceeds.

Shadow: misusing hot path at rune 1622 in the Rune lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name hot path when the prompt needs this obligation made explicit: hot path in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the hot path obligation named before work proceeds.
  • Ask the assistant to state the hot path shadow before proposing changes.

Example clause:

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

114.2.41 [1623] infrastructure-as-code

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Operational change expressed as reviewable source.

Shadow: misusing infrastructure-as-code at rune 1623 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name infrastructure-as-code when the prompt needs this obligation made explicit: Operational change expressed as reviewable source.
  • Ask the assistant to state the infrastructure-as-code shadow before proposing changes.

Example clause:

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

Pocket gloss: Operational change expressed as reviewable source.

114.2.42 [1624] least-authority

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: least-authority is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the least-authority obligation named before work proceeds.

Shadow: misusing least-authority at rune 1624 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name least-authority when the prompt needs this obligation made explicit: least-authority is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the least-authority obligation named before work proceeds.
  • Ask the assistant to state the least-authority shadow before proposing changes.

Example clause:

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

114.2.43 [1625] lock-free {Rune}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: lock-free in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the lock-free obligation named before work proceeds.

Shadow: misusing lock-free at rune 1625 in the Rune lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name lock-free when the prompt needs this obligation made explicit: lock-free in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the lock-free obligation named before work proceeds.
  • Ask the assistant to state the lock-free shadow before proposing changes.

Example clause:

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

114.2.44 [1626] machine-readable

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Structured so software, not only humans, can read it reliably.

Shadow: misusing machine-readable at rune 1626 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name machine-readable when the prompt needs this obligation made explicit: Structured so software, not only humans, can read it reliably.
  • Ask the assistant to state the machine-readable shadow before proposing changes.

Example clause:

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

Pocket gloss: Structured so software, not only humans, can read it reliably.

114.2.45 [1627] memory-safe {Rune}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: memory-safe in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the memory-safe obligation named before work proceeds.

Shadow: misusing memory-safe at rune 1627 in the Rune lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name memory-safe when the prompt needs this obligation made explicit: memory-safe in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the memory-safe obligation named before work proceeds.
  • Ask the assistant to state the memory-safe shadow before proposing changes.

Example clause:

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

114.2.46 [1628] multi-tenant

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: multi-tenant is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the multi-tenant obligation named before work proceeds.

Shadow: misusing multi-tenant at rune 1628 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name multi-tenant when the prompt needs this obligation made explicit: multi-tenant is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the multi-tenant obligation named before work proceeds.
  • Ask the assistant to state the multi-tenant shadow before proposing changes.

Example clause:

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

114.2.47 [1629] negative cache

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: negative cache is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the negative cache obligation named before work proceeds.

Shadow: misusing negative cache at rune 1629 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name negative cache when the prompt needs this obligation made explicit: negative cache is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the negative cache obligation named before work proceeds.
  • Ask the assistant to state the negative cache shadow before proposing changes.

Example clause:

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

114.2.48 [1630] object-capability

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: object-capability is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the object-capability obligation named before work proceeds.

Shadow: misusing object-capability at rune 1630 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name object-capability when the prompt needs this obligation made explicit: object-capability is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the object-capability obligation named before work proceeds.
  • Ask the assistant to state the object-capability shadow before proposing changes.

Example clause:

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

114.2.49 [1631] offline-first {Rune}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Designed to keep working with poor or absent connectivity.

Shadow: misusing offline-first at rune 1631 in the Rune lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name offline-first when the prompt needs this obligation made explicit: Designed to keep working with poor or absent connectivity.
  • Ask the assistant to state the offline-first shadow before proposing changes.

Example clause:

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

Pocket gloss: Designed to keep working with poor or absent connectivity.

114.2.50 [1632] policy-as-code

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Policy declared as versioned, testable code.

Shadow: misusing policy-as-code at rune 1632 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name policy-as-code when the prompt needs this obligation made explicit: Policy declared as versioned, testable code.
  • Ask the assistant to state the policy-as-code shadow before proposing changes.

Example clause:

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

Pocket gloss: Policy declared as versioned, testable code.

114.2.51 [1633] queue-backed

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: queue-backed is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the queue-backed obligation named before work proceeds.

Shadow: misusing queue-backed at rune 1633 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name queue-backed when the prompt needs this obligation made explicit: queue-backed is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the queue-backed obligation named before work proceeds.
  • Ask the assistant to state the queue-backed shadow before proposing changes.

Example clause:

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

114.2.52 [1634] read path

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: read path is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the read path obligation named before work proceeds.

Shadow: misusing read path at rune 1634 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name read path when the prompt needs this obligation made explicit: read path is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the read path obligation named before work proceeds.
  • Ask the assistant to state the read path shadow before proposing changes.

Example clause:

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

114.2.53 [1635] read-through cache

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: read-through cache is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the read-through cache obligation named before work proceeds.

Shadow: misusing read-through cache at rune 1635 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name read-through cache when the prompt needs this obligation made explicit: read-through cache is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the read-through cache obligation named before work proceeds.
  • Ask the assistant to state the read-through cache shadow before proposing changes.

Example clause:

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

114.2.54 [1636] real-time {Rune}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: real-time in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the real-time obligation named before work proceeds.

Shadow: misusing real-time at rune 1636 in the Rune lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name real-time when the prompt needs this obligation made explicit: real-time in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the real-time obligation named before work proceeds.
  • Ask the assistant to state the real-time shadow before proposing changes.

Example clause:

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

114.2.55 [1637] rule-based

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: rule-based is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the rule-based obligation named before work proceeds.

Shadow: misusing rule-based at rune 1637 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name rule-based when the prompt needs this obligation made explicit: rule-based is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the rule-based obligation named before work proceeds.
  • Ask the assistant to state the rule-based shadow before proposing changes.

Example clause:

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

114.2.56 [1638] side-effect-free {Rune}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: side-effect-free in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the side-effect-free obligation named before work proceeds.

Shadow: misusing side-effect-free at rune 1638 in the Rune lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name side-effect-free when the prompt needs this obligation made explicit: side-effect-free in its Rune sense is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the side-effect-free obligation named before work proceeds.
  • Ask the assistant to state the side-effect-free shadow before proposing changes.

Example clause:

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

114.2.57 [1639] single source of truth

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: One canonical place others are expected to mirror.

Shadow: misusing single source of truth at rune 1639 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name single source of truth when the prompt needs this obligation made explicit: One canonical place others are expected to mirror.
  • Ask the assistant to state the single source of truth shadow before proposing changes.

Example clause:

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

Pocket gloss: One canonical place others are expected to mirror.

114.2.58 [1640] soft delete

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: soft delete is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the soft delete obligation named before work proceeds.

Shadow: misusing soft delete at rune 1640 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name soft delete when the prompt needs this obligation made explicit: soft delete is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the soft delete obligation named before work proceeds.
  • Ask the assistant to state the soft delete shadow before proposing changes.

Example clause:

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

114.2.59 [1641] statefulset

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: statefulset is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the statefulset obligation named before work proceeds.

Shadow: misusing statefulset at rune 1641 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name statefulset when the prompt needs this obligation made explicit: statefulset is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the statefulset obligation named before work proceeds.
  • Ask the assistant to state the statefulset shadow before proposing changes.

Example clause:

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

114.2.60 [1642] write path

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: write path is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the write path obligation named before work proceeds.

Shadow: misusing write path at rune 1642 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name write path when the prompt needs this obligation made explicit: write path is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the write path obligation named before work proceeds.
  • Ask the assistant to state the write path shadow before proposing changes.

Example clause:

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

114.2.61 [1643] write-through cache

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: write-through cache is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the write-through cache obligation named before work proceeds.

Shadow: misusing write-through cache at rune 1643 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name write-through cache when the prompt needs this obligation made explicit: write-through cache is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the write-through cache obligation named before work proceeds.
  • Ask the assistant to state the write-through cache shadow before proposing changes.

Example clause:

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

114.2.62 [1644] zero-downtime

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Change introduced without taking the service dark.

Shadow: misusing zero-downtime at rune 1644 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name zero-downtime when the prompt needs this obligation made explicit: Change introduced without taking the service dark.
  • Ask the assistant to state the zero-downtime shadow before proposing changes.

Example clause:

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

Pocket gloss: Change introduced without taking the service dark.

114.2.63 [1645] zero-knowledge

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: zero-knowledge is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the zero-knowledge obligation named before work proceeds.

Shadow: misusing zero-knowledge at rune 1645 in the naming lane can let the modifier can imply a guarantee the base design has not earned; verify by requiring the caster to state the base term, modifier, and exact guarantee being added.

Prompt uses:

  • Name zero-knowledge when the prompt needs this obligation made explicit: zero-knowledge is a compound naming and modifiers rune for make naming modifiers precise enough to carry engineering force; use it when the artifact needs the zero-knowledge obligation named before work proceeds.
  • Ask the assistant to state the zero-knowledge shadow before proposing changes.

Example clause:

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