Two rules that coin one key stay apart, and a rule with no ASCII word stays unkeyed

outcome

Execute the uniqueness and unkeyable rules on a probe Spec whose first two rules coin the same key and whose third holds no ASCII word.

assumptions

• The world writes the probe corpus of the applies-clean example with the three rules the step lists, the third written in Greek letters, and reads the shipped rule-key proposal file's answer as that example does.

Examples

Given a probe Spec whose unkeyed rules read {rules: "A part fits the budget. / Every part fits the budget again. / Ο κανόνας ισχύει."}
When the rule-key proposal runs for it at a commit and the proposal check reads it against the graph of that commit
Then the proposal adds the keys {keys: "partFitsBudget, partFitsBudget2"}
Then the proposal leaves {unkeyable: 1} entries unkeyed
Then the proposal check reports {moved: 0} moved changes and {problems: 0} schema problems

Verifier bindings

• test:protocol.rule-key-proposal.collision-and-unkeyable · anchored · test anchor binding present · test/upgrade-kit.test.ts:483

  External run evidence from test/upgrade-kit.test.ts

  Test anchors: test:protocol.capability-adoption.counts-a-corpus, test:protocol.rule-key-proposal.collision-and-unkeyable, test:protocol.rule-key-proposal.proposal-applies-clean, test:protocol.upgrade-guide. Specs verified by those bindings: spec:consumers.upgrade-kit, spec:consumers.upgrade-kit.capability-adoption, spec:consumers.upgrade-kit.capability-adoption.counts-a-corpus, spec:consumers.upgrade-kit.rule-key-proposal, spec:consumers.upgrade-kit.rule-key-proposal.collision-and-unkeyable, spec:consumers.upgrade-kit.rule-key-proposal.proposal-applies-clean.

  Run 1: external run evidence from vitest 4.1.10

  Build: CI 391 · Branch: cursor/media-plan-and-articles-09b1 · Commit: 076cd4f1f85640d8236e5cca1bffffa68ab79a33 · Start: 2026-10-31T15:32:20.471Z · Stop: 2026-10-31T15:34:02.073Z

  Name	Suite	Result	Duration
  applies unchanged scopes while sending only moved changes to a person	upgrade kit	passed	2.69 ms
  names a carrying Spec in every guide section	upgrade kit	passed	0.66 ms
  teaches the upgrade steps in the pinned order	upgrade kit	passed	1.11 ms
  teaches epic reparenting and advisory roadmap adoption	upgrade kit	passed	0.5 ms
  runs the guide's rules file on a clean corpus with no address parameters	upgrade kit	passed	22.82 ms
  names the recipes' carrying Specs and teaches rule-key proposal as the rule-key action	upgrade kit	passed	1.68 ms
  ships the guide and names every reported capability's law and measurement	upgrade kit	passed	13.26 ms
  counts rules, reasons and unknown external perspectives	upgrade kit	passed	7.81 ms
  coins collisions and lists an unkeyable entry	upgrade kit	passed	4.95 ms
  executes the bound example against a fresh world	Capability adoption counts keyed rules and reasoned relations (spec:consumers.upgrade-kit.capability-adoption.counts-a-corpus)	passed	7.51 ms
  executes the bound example against a fresh world	A rule-key proposal passes the proposal check and validates once applied (spec:consumers.upgrade-kit.rule-key-proposal.proposal-applies-clean)	passed	14.93 ms
  executes the bound example against a fresh world	Two rules that coin one key stay apart, and a rule with no ASCII word stays unkeyed (spec:consumers.upgrade-kit.rule-key-proposal.collision-and-unkeyable)	passed	13.14 ms
  counts distinct step skeletons and vocabulary keys inherited through refines	capability adoption details	passed	14.92 ms
  counts distinct step skeletons and vocabulary keys inherited through verifies	capability adoption details	passed	5.93 ms
  counts repeated vocabulary and example steps once per skeleton within a Spec	capability adoption details	passed	1.83 ms
  counts all capabilities and deduplicates shared components and repeated Pack members	capability adoption details	passed	14.29 ms
  diagnoses detail null	capability adoption details	passed	3.74 ms
  diagnoses detail 1	capability adoption details	passed	2.14 ms
  diagnoses detail "all"	capability adoption details	passed	1.93 ms
  diagnoses detail {}	capability adoption details	passed	1.91 ms
  diagnoses detail "spec:missing"	capability adoption details	passed	1.91 ms
  diagnoses detail true	capability adoption details	passed	1.85 ms
  drops possessives and apostrophes before coining keys	rule-key proposal details	passed	2.22 ms
  preserves scope and entry order and skips existing keys and tags	rule-key proposal details	passed	12.48 ms
  diagnoses both scopes even when each resolves	rule-key proposal details	passed	2.12 ms
  diagnoses invalid parameters {}	rule-key proposal details	passed	1.94 ms
  diagnoses invalid parameters {"commit":""}	rule-key proposal details	passed	1.99 ms
  diagnoses invalid parameters {"commit":1}	rule-key proposal details	passed	1.91 ms
  diagnoses invalid parameters {"commit":"abc","pack":"pack:missing"}	rule-key proposal details	passed	1.81 ms
  diagnoses invalid parameters {"commit":"abc","specs":["spec:missing"]}	rule-key proposal details	passed	1.85 ms
  diagnoses invalid parameters {"commit":"abc","specs":[],"pack":"pack:missing"}	rule-key proposal details	passed	3.9 ms
  diagnoses invalid parameters {"commit":"abc","specs":"all"}	rule-key proposal details	passed	1.84 ms
  drops leading digit words before checking word repeats	not recorded	passed	1.97 ms

Requirement drawing

• Satisfying or referencing units: no recorded binding.

Decisions

No decision record named.

No implementation neighborhood recorded.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.