The upgrade kit shows a corpus what it could adopt

actor

An adopter moving a corpus onto a newer Protocol commit, or the agent working for it.

problem

An adopter cannot see which capabilities its corpus already uses and where each could apply, so it hand-rolls the survey for every release and applies each new capability by hand.

outcome

Report, per Spec and Pack, the Protocol capabilities a corpus uses and where each could apply, and propose the edits as a change proposal an agent applies, never editing a carrier itself.

rule.reportsAndProposes line 30 · specs/consumers/upgrade-kit.sdp.md:30

The kit reports and proposes and never edits: its recipes read the graph and return data, and a change reaches a carrier only as an agent's or a person's edit, applied after the proposal check and recorded by git.

no example exercises it

rule.statesNoRung line 31 · specs/consumers/upgrade-kit.sdp.md:31

The kit states no rung, authors no fact and scores nothing: a capability it reports as unused is a place it could apply, never a finding, a gate or a quota.

no example exercises it

rule.upgradeGuide line 32 · specs/consumers/upgrade-kit.sdp.md:32

The package ships an upgrade guide for an adopter moving its corpus onto a newer commit: it measures the corpus with capability adoption, keys its rules with the rule-key proposal, and, for each capability the report lists, names the Spec that carries its law, with capability adoption as the recipe that measures it.

no example exercises it

rule.guideTeaches line 33 · specs/consumers/upgrade-kit.sdp.md:33

The guide teaches and states no law: each section names the Spec that carries what it teaches, and no section repeats that Spec's rules.

no example exercises it

0 unkeyed rules.

guideFile line 36 · specs/consumers/upgrade-kit.sdp.md:36

docs/agent-surface/upgrade-guide.md, shipped in the package beside the recipe catalog, listed in the package's files and named by sdp --help among the shipped on-ramps.

no citation recorded

guideSections line 37 · specs/consumers/upgrade-kit.sdp.md:37

in this order: re-pin the package and check sdp --version; measure the corpus with capability adoption (recipe 47); organize features in epics, reading the capability map (recipe 52) and citing spec:consumers.capability-map; Model upcoming work in the graph; keep review history in git and pull requests, a roadmap Pack read with recipes 53 and 55 and intended design proposed as a change proposal checked by recipe 38, citing spec:consumers.roadmap, with the guidance Unresolved intended design lives in open questions. Review disposition and acceptance remain in git and the pull request; neither becomes a graph field.; key the rules with the rule-key proposal (recipe 48), check the proposal with the proposal check (recipe 38) and apply it through an agent's edit; for every capability in recipe 47's answer, one subsection citing its carriedBy Spec and recipe 47 as the measurement, naming a further recipe only when the subsection teaches a distinct next action with it and otherwise sending the reader to the carrying Spec; move rules files onto shipped recipes, recipes 25, 26, 42, 50 and 51 and the recipes binding; read large Packs in parts and order the waiting statements, recipes 36 and 46; publish every root with sdp generate; and pass a recipe's subject as --params data, the recipe-caller guidance the README carries.

Verifier bindings

• test:protocol.upgrade-guide · anchored · test anchor binding present · test/upgrade-kit.test.ts:94

  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

Decisions

No decision record named.

• impl:protocol.upgrade-guide · realizes the shipped upgrade guide document · test/upgrade-kit.test.ts:87

  Uses

  None.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.