<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/4.x/2026-10-19-1-activation-ledger-persists-deactivation/">
  <id>https://docs.spec-kitty.ai/adr/4.x/2026-10-19-1-activation-ledger-persists-deactivation/</id>
  <title>ADR: one activation ledger persists deactivation, and nothing silently reinstalls it</title>
  <updated>2026-11-01T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/4.x/2026-10-19-1-activation-ledger-persists-deactivation/"/>
  <summary>Activation state moves to one git-tracked file, .kittify/charter/activation.yaml, with a persistent deny-list so a deactivated charter artifact stays deactivated.</summary>
  <content type="html">&lt;h2 id=&quot;one-activation-ledger-persists-deactivation-and-nothing-silently-reinstalls-it&quot;&gt;One activation ledger persists deactivation, and nothing silently reinstalls it&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted (2026-10-19); amended 2026-10-20, 2026-10-25, 2026-10-31 and 2026-11-01 (see the amendments at the end).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-10-19&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Stijn Dejongh (operator).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt; the core side of spec-kitty-charter ADR-0013 (“Deactivation persists in one
activation ledger, and nothing silently reinstalls it”), steps
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/62&quot;&gt;#62&lt;/a&gt;,
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/63&quot;&gt;#63&lt;/a&gt;,
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/64&quot;&gt;#64&lt;/a&gt;,
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/66&quot;&gt;#66&lt;/a&gt; and
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/67&quot;&gt;#67&lt;/a&gt;. Step
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/65&quot;&gt;#65&lt;/a&gt; (projection and resolution
filtering in the Java offering) belongs to the Java offering and is not decided here. Mission:
&lt;a href=&quot;../../../kitty-specs/persistent-deactivation-ledger-01M59YAA/spec.md&quot;&gt;spec&lt;/a&gt;,
&lt;a href=&quot;../../../kitty-specs/persistent-deactivation-ledger-01M59YAA/plan.md&quot;&gt;plan&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Reader:&lt;/strong&gt; a core maintainer who reads, writes or migrates charter activation state, or who
reviews a change to the activation seam.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Supersedes / amends:&lt;/strong&gt; supersedes &lt;strong&gt;Decision 2 only&lt;/strong&gt; (“&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; OWNS activation”) of
&lt;a href=&quot;/adr/3.x/2026-07-18-1-charter-yaml-authoring-authority-and-extractor-retirement/&quot;&gt;ADR 2026-07-18-1&lt;/a&gt;;
amends &lt;a href=&quot;/adr/4.x/2026-10-03-1-charter-read-write-service-strangler/&quot;&gt;ADR 2026-10-03-1&lt;/a&gt; (the activation
write target) and
&lt;a href=&quot;/adr/4.x/2026-10-06-2-charter-offering-active-charter-and-activation-presets/&quot;&gt;ADR 2026-10-06-2&lt;/a&gt;
(presets, synthesis). Related: &lt;a href=&quot;/adr/4.x/2026-10-17-1-explicit-migration-ledger/&quot;&gt;ADR 2026-10-17-1&lt;/a&gt; (the
Migration Ledger, a different ledger), &lt;a href=&quot;/adr/4.x/2026-10-16-1-extract-charter-offering-first-activation-rework-post-ga/&quot;&gt;ADR 2026-10-16-1&lt;/a&gt;
(activation rework is post-GA work; the operator brought this slice forward, constraint C-010).&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;A user who runs &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter deactivate directive D&lt;/code&gt; expects D to stay gone. Today it does
not, for four reasons.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Deactivation only edits an allow-list.&lt;/strong&gt; It removes the id from &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt;. When that
key is absent (which means “every artifact is in force”), there is nothing to remove from, and
the command raises &lt;code dir=&quot;auto&quot;&gt;NoActivationRestrictionsError&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Several paths quietly bring the artifact back.&lt;/strong&gt; The cascade walk activates every artifact it
reaches. The one-time rc6 cutover reset turns a list equal to the default back into “absent”.
The interview and promotion writers append ids they select or that an org pack requires.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activation state has several homes.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; its pointer
names, and &lt;code dir=&quot;auto&quot;&gt;answers.selected_*&lt;/code&gt; all carry some of it, and the read and write paths each pick one.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A required artifact can be “deactivated” with no effect.&lt;/strong&gt; The org &lt;code dir=&quot;auto&quot;&gt;required_&amp;#x3C;kind&gt;&lt;/code&gt; union
overrides the user’s intent without saying so.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;An allow-list cannot hold an exclusion under “absent = all”: the exclusion has to be stored as its
own fact. That needs one authoritative home, and a way to reach it for projects that already exist.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A deactivation must survive every later command, upgrade, interview and regeneration, until the
user explicitly activates the artifact again.&lt;/li&gt;
&lt;li&gt;One file must answer “what is active here”, and doctor must report any surface that disagrees.&lt;/li&gt;
&lt;li&gt;No runtime fallback to legacy surfaces: ambiguity is resolved by migration, not by guessing.&lt;/li&gt;
&lt;li&gt;Shipped migrations must behave byte-for-byte as before (DIRECTIVE_044, constraint C-001).&lt;/li&gt;
&lt;li&gt;The activation layer is being extracted into its own repository, so layering must hold
(&lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; never imports activation; &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; reaches it through
&lt;code dir=&quot;auto&quot;&gt;charter.activation.api&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A. Store exclusions inside the allow-list.&lt;/strong&gt; Rejected: under “absent = all” there is no list to
remove from, and every writer that rebuilds a list can re-add the id.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;B. A separate deny file beside the existing surfaces.&lt;/strong&gt; Rejected: a third home for activation
state, with the same drift problem.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;C. One activation ledger holding allow and deny state, with a migration into it.&lt;/strong&gt; Chosen.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Chosen option: C&lt;/strong&gt;, recorded as the seven decisions below.&lt;/p&gt;
&lt;h3 id=&quot;decision-1-one-ledger&quot;&gt;Decision 1: one ledger&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt; (git-tracked) is the single authority for activation. It is a
flat mapping, and every key is optional:&lt;/p&gt;






























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Key&lt;/th&gt;&lt;th&gt;Absent means&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt; means&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;activated_kinds&lt;/code&gt;&lt;/td&gt;&lt;td&gt;every kind&lt;/td&gt;&lt;td&gt;no kind&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt;&lt;/td&gt;&lt;td&gt;none in force&lt;/td&gt;&lt;td&gt;none&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;plural&gt;&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the kind’s &lt;code dir=&quot;auto&quot;&gt;ArtifactKind.effective_when_absent&lt;/code&gt; default (&lt;code dir=&quot;auto&quot;&gt;&quot;all&quot;&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;&quot;required&quot;&lt;/code&gt; for &lt;code dir=&quot;auto&quot;&gt;skill&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;nothing (fail-closed empty)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;deactivated_&amp;#x3C;plural&gt;&lt;/code&gt;&lt;/td&gt;&lt;td&gt;no exclusion&lt;/td&gt;&lt;td&gt;treated as absent, never written&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;An empty &lt;code dir=&quot;auto&quot;&gt;deactivated_&amp;#x3C;plural&gt;&lt;/code&gt; is omitted from the file. The key set derives from
&lt;code dir=&quot;auto&quot;&gt;ArtifactKind.activatable&lt;/code&gt;, never from a hand-written list (constraint C-004). An unknown
non-deny key fails closed with &lt;code dir=&quot;auto&quot;&gt;ActiveCharterConfigError&lt;/code&gt;. An unknown &lt;code dir=&quot;auto&quot;&gt;deactivated_&amp;#x3C;x&gt;&lt;/code&gt; key (a
kind a later CLI added) is preserved, ignored by readers and reported by doctor as a warning.
&lt;code dir=&quot;auto&quot;&gt;deactivated_*&lt;/code&gt; keys never appear in &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; (C-003).&lt;/p&gt;
&lt;p&gt;The ledger is an optional tracked member of the charter bundle and an optional member of its
content hash, so an edit made outside the CLI reads as stale, and a project without a ledger keeps
its hash. Every successful ledger write restamps the bundle hash.&lt;/p&gt;
&lt;p&gt;Every other surface derives from the ledger or is checked against it. &lt;code dir=&quot;auto&quot;&gt;answers.selected_*&lt;/code&gt; stays
provenance only (ADR 2026-07-18-1); a denied id listed there produces a doctor warning, not a
different answer.&lt;/p&gt;
&lt;h3 id=&quot;decision-2-the-effective-set-algebra&quot;&gt;Decision 2: the effective-set algebra&lt;/h3&gt;
&lt;p&gt;For a kind &lt;em&gt;k&lt;/em&gt;, with &lt;code dir=&quot;auto&quot;&gt;Avail(k)&lt;/code&gt; the artifacts available across the built-in, org-chain and project
layers, &lt;code dir=&quot;auto&quot;&gt;R(k)&lt;/code&gt; the required floor (Decision 6) and &lt;code dir=&quot;auto&quot;&gt;D(k)&lt;/code&gt; the ledger’s deny-list:&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;D*(k)   = resolve_deny(D(k)) − R(k)            effective deny, in identity space&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;base(k) = S                          if the allow state is the list S&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;        &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;= ∅                          if the allow state is []&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;        &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;= Avail(k)                   if absent and effective_when_absent = &quot;all&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;        &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;= R(k) (+ built-in defaults) if absent and effective_when_absent = &quot;required&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;E(k)    = base(k) − D*(k)                       the effective set&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;Sel(k)  = (selected_&amp;#x3C;k&gt; ∪ R(k)) − D*(k)         the governance selection overlay&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;Identity space.&lt;/strong&gt; A deny entry is a stem, but an allow entry may be a declared id (for example
&lt;code dir=&quot;auto&quot;&gt;PROC_CANVAS_REVIEW&lt;/code&gt; for stem &lt;code dir=&quot;auto&quot;&gt;canvas-review&lt;/code&gt;), and a DRG node is a URN. &lt;code dir=&quot;auto&quot;&gt;resolve_deny&lt;/code&gt; expands
each entry into all three spellings (&lt;code dir=&quot;auto&quot;&gt;DenySet&lt;/code&gt;: stems, declared ids, URNs), and membership is
tested against any of them. Without this, a stem in the deny-list would fail to subtract the
declared id in the allow-list.&lt;/p&gt;
&lt;p&gt;The effective set is computed once, in &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt;. Core readers reach it through the
&lt;code dir=&quot;auto&quot;&gt;PackContext.admits&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;effective_ids&lt;/code&gt; accessors, and a gate forbids raw &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;plural&gt;&lt;/code&gt;
membership checks outside the seam. Required artifacts are never subtracted: a stale deny entry
for a required id is inert and doctor reports it.&lt;/p&gt;
&lt;h3 id=&quot;decision-3-source-resolution&quot;&gt;Decision 3: source resolution&lt;/h3&gt;
&lt;p&gt;One resolver in the kernel (&lt;code dir=&quot;auto&quot;&gt;kernel.activation_ledger_store.resolve_activation_source&lt;/code&gt;) decides
where activation is read from and written to. The kernel never raises an activation-domain error;
it returns the source and the raw data, and each caller keeps its own error text.&lt;/p&gt;









































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Ledger file&lt;/th&gt;&lt;th&gt;Upgrade scope&lt;/th&gt;&lt;th&gt;Legacy keys&lt;/th&gt;&lt;th&gt;Result&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;exists&lt;/td&gt;&lt;td&gt;any&lt;/td&gt;&lt;td&gt;none&lt;/td&gt;&lt;td&gt;the ledger&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;exists&lt;/td&gt;&lt;td&gt;any&lt;/td&gt;&lt;td&gt;present&lt;/td&gt;&lt;td&gt;the ledger; the stray keys are reported (below)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;absent&lt;/td&gt;&lt;td&gt;inside&lt;/td&gt;&lt;td&gt;any&lt;/td&gt;&lt;td&gt;legacy surface, byte-for-byte as before the ledger&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;absent&lt;/td&gt;&lt;td&gt;outside&lt;/td&gt;&lt;td&gt;present&lt;/td&gt;&lt;td&gt;fail closed: &lt;code dir=&quot;auto&quot;&gt;ActiveCharterConfigError&lt;/code&gt; naming &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;absent&lt;/td&gt;&lt;td&gt;outside&lt;/td&gt;&lt;td&gt;none&lt;/td&gt;&lt;td&gt;the ledger (a fresh project; the first write creates the file)&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;“Upgrade scope” is a kernel &lt;code dir=&quot;auto&quot;&gt;ContextVar&lt;/code&gt; that matches the resolved and the canonical root. It is
entered by &lt;code dir=&quot;auto&quot;&gt;BaseMigration&lt;/code&gt; for every public project-path method a subclass defines, by
&lt;code dir=&quot;auto&quot;&gt;MigrationRegistry.get_applicable&lt;/code&gt;, by the &lt;code dir=&quot;auto&quot;&gt;MigrationRunner&lt;/code&gt; selection points, by
&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate ledger&lt;/code&gt; and by the &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; command body. That keeps shipped
migrations that write through the seam before the ledger migration unchanged (C-001).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Stray legacy keys beside a ledger.&lt;/strong&gt; An ordinary command prints one warning per process naming
the keys and saying the ledger wins; &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; reports them as an error
(&lt;code dir=&quot;auto&quot;&gt;LEGACY_KEYS_PRESENT&lt;/code&gt;) from the resolver’s data, without going through a raising read.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; writes the ledger&lt;/strong&gt; (provisioning &lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt;), so a fresh
project is never “unmigrated” and the upgrade stays a no-op on it.&lt;/p&gt;
&lt;h3 id=&quot;decision-4-only-explicit-choices-change-a-deny-list&quot;&gt;Decision 4: only explicit choices change a deny-list&lt;/h3&gt;
&lt;p&gt;Five paths, and no others, may change a &lt;code dir=&quot;auto&quot;&gt;deactivated_&amp;#x3C;plural&gt;&lt;/code&gt; list:&lt;/p&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Path&lt;/th&gt;&lt;th&gt;Effect on the deny-list&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter deactivate &amp;#x3C;kind&gt; &amp;#x3C;id&gt;&lt;/code&gt;&lt;/td&gt;&lt;td&gt;adds the id&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt;&lt;/code&gt; (including &lt;code dir=&quot;auto&quot;&gt;--only&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;removes the id&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate ... --cascade ... --include-deactivated&lt;/code&gt;&lt;/td&gt;&lt;td&gt;removes the ids the walk reaches&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --preset X --force&lt;/code&gt;&lt;/td&gt;&lt;td&gt;removes the ids the preset lists, and reports them&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;the project-intent rename (&lt;code dir=&quot;auto&quot;&gt;#6443&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#6565&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter resynthesize&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;moves&lt;/strong&gt; an entry from &lt;code dir=&quot;auto&quot;&gt;NNN-mission-type-scope-directive&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;NNN-project-intent-directive&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The rename adds and removes nothing. It rewrites the id the user’s own &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt;
recorded, so the same artifact stays excluded after its artifact is renamed. Leaving the entry
stale — reported as &lt;code dir=&quot;auto&quot;&gt;DENY_UNKNOWN_ID&lt;/code&gt;, with the artifact back in force — is the defect this closes.
It runs only on the activation ledger — a hand-written legacy deny key on &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; is left where it is, because a legacy surface’s deny key is never applied — and only
when a legacy stem is actually present, so a project that never had one performs no deny write.&lt;/p&gt;
&lt;p&gt;Presets without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;, the interview, org-required promotion, mission-type seeding and every
migration never touch deny keys. Synthesis reaches a deny key only through the rename above, which
moves the one legacy stem and nothing else. A denied id they list stays subtracted and is named in
a warning. Ids dropped by &lt;code dir=&quot;auto&quot;&gt;--only&lt;/code&gt; narrowing get no deny entry; only an id the user names in
&lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; is added.&lt;/p&gt;
&lt;p&gt;The guard is structural. The ledger write takes a &lt;code dir=&quot;auto&quot;&gt;deny_change&lt;/code&gt; keyword (&lt;code dir=&quot;auto&quot;&gt;DenyListChoice&lt;/code&gt;:
&lt;code dir=&quot;auto&quot;&gt;activate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;cascade-include-deactivated&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;preset-force&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;rename&lt;/code&gt;). A write that
changes a deny-list (compared as normalised sets, so absent, &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt; are equal) without one
raises &lt;code dir=&quot;auto&quot;&gt;DenyListWriteRefused&lt;/code&gt; and writes nothing. A gate over every registered migration and
built-in preset proves that none removes a deny entry other than by the pinned rename: a static
scan, plus a dynamic run of each activation-touching migration on a fixture where it applies, made
non-vacuous by a self-mutation test. The &lt;code dir=&quot;auto&quot;&gt;rename&lt;/code&gt; origin is pinned to its one function in both
directions, and because it is the only allowance in that gate, the gate carries a positive control
that the rename does carry one entry — and only that one.&lt;/p&gt;
&lt;h3 id=&quot;decision-5-the-cascade-stops-at-a-denied-node&quot;&gt;Decision 5: the cascade stops at a denied node&lt;/h3&gt;
&lt;p&gt;Operator ruling &lt;code dir=&quot;auto&quot;&gt;cascade_walk_through_denied&lt;/code&gt;. A cascade activation walk skips a denied node,
reports it, and &lt;strong&gt;does not expand it&lt;/strong&gt;: nothing reachable only through a denied node is activated.
A node that is also reachable over a path that avoids every denied node is still reached.
&lt;code dir=&quot;auto&quot;&gt;--include-deactivated&lt;/code&gt; restores the full walk, activates the denied nodes and clears their
exclusions.&lt;/p&gt;
&lt;p&gt;The result gains two buckets beside &lt;code dir=&quot;auto&quot;&gt;skipped_by_scope&lt;/code&gt;: &lt;strong&gt;skipped, deactivated&lt;/strong&gt; (each entry says
whether it was reached over a &lt;code dir=&quot;auto&quot;&gt;REQUIRES&lt;/code&gt; edge and from which parents) and &lt;strong&gt;unreached&lt;/strong&gt; (reachable
only behind a denied node). Every node of the full walk lands in exactly one bucket, and scope is
decided before deny.&lt;/p&gt;
&lt;p&gt;A cascade &lt;em&gt;deactivation&lt;/em&gt; records only the id the user named; children removed with it lose their
allow-list entry but get no deny entry (the shared-reference skip, C-007, is unchanged). Under an
absent allow-list the children stay active, and the output says so (“still active: no allow-list;
only P was excluded”).&lt;/p&gt;
&lt;h3 id=&quot;decision-6-a-required-artifact-cannot-be-deactivated&quot;&gt;Decision 6: a required artifact cannot be deactivated&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; on an id that any declared org pack requires exits non-zero, names the
requiring pack and the &lt;code dir=&quot;auto&quot;&gt;required_&amp;#x3C;kind&gt;&lt;/code&gt; policy, and records nothing. The required floor is the
&lt;strong&gt;union of &lt;code dir=&quot;auto&quot;&gt;required_&amp;#x3C;plural&gt;&lt;/code&gt; over every declared org pack and each pack’s &lt;code dir=&quot;auto&quot;&gt;extends:&lt;/code&gt; chain&lt;/strong&gt;,
read by one iterator. Precedence never decides whether an id is required, so the org-pack
precedence work in the parallel workstream is untouched (C-005).&lt;/p&gt;
&lt;p&gt;The read is strict. An unreadable or malformed declared pack, an &lt;code dir=&quot;auto&quot;&gt;extends:&lt;/code&gt; cycle or a dangling
base raises &lt;code dir=&quot;auto&quot;&gt;ActiveCharterConfigError&lt;/code&gt;; it never widens the answer. The floor is always read for
deactivation and promotion, and on reads only when a deny-list is non-empty (the only case where
the floor changes the answer). One refusal seam, &lt;code dir=&quot;auto&quot;&gt;check_deactivation_permitted&lt;/code&gt;, raises
&lt;code dir=&quot;auto&quot;&gt;RequiredArtifactDeactivationError&lt;/code&gt;, a &lt;code dir=&quot;auto&quot;&gt;DeactivationRefused&lt;/code&gt; subtype that a later &lt;code dir=&quot;auto&quot;&gt;locked&lt;/code&gt;
mutability level can join. &lt;code dir=&quot;auto&quot;&gt;NoActivationRestrictionsError&lt;/code&gt; is deleted, with no alias (C-008).&lt;/p&gt;
&lt;h3 id=&quot;decision-7-the-migration&quot;&gt;Decision 7: the migration&lt;/h3&gt;
&lt;p&gt;A new migration, &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_activation_ledger&lt;/code&gt; (tracked partition, &lt;code dir=&quot;auto&quot;&gt;clone_local_effect = False&lt;/code&gt;,
listed in &lt;code dir=&quot;auto&quot;&gt;order_manifest.txt&lt;/code&gt; after the rc7 entries), moves every activation key from the pointer
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, a no-pointer legacy &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt;, or a leftover &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; copy into the
ledger, preserving three-state values including &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Refuses divergence&lt;/strong&gt;, naming the key and both files and changing nothing, when two surfaces
disagree on a key. This includes a stray &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; copy of a key the authoritative
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; lacks (operator ruling &lt;code dir=&quot;auto&quot;&gt;stray_config_copy&lt;/code&gt;). A legacy &lt;code dir=&quot;auto&quot;&gt;deactivated_*&lt;/code&gt; key is also
refused, because no legacy surface can hold one.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Re-runnable after a crash.&lt;/strong&gt; The order is ledger write, strip &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, strip
&lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt;, restamp the bundle hash. A re-run with a ledger present strips legacy keys equal
to it, so an interruption at any point is recovered by running again.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Idempotent.&lt;/strong&gt; A second run changes zero bytes.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Dogfood path&lt;/strong&gt; (operator ruling &lt;code dir=&quot;auto&quot;&gt;dogfood_migration_path&lt;/code&gt;). A full &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; on this
repository has no populated migration ledger and would select the whole manifest, so the
repository could not move its own keys narrowly. &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate activation-ledger [--dry-run] [--json]&lt;/code&gt; runs only this migration’s planner and apply, with the same refusals, and is
how this repository, and any project an older CLI wrote legacy keys into again, gets its ledger.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A second, narrow writer of the Migration Ledger.&lt;/strong&gt; ADR 2026-10-17-1 names &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;
as the Migration Ledger’s only writer. &lt;code dir=&quot;auto&quot;&gt;migrate activation-ledger&lt;/code&gt; becomes a second one. It
appends the &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_activation_ledger&lt;/code&gt; success row only when &lt;code dir=&quot;auto&quot;&gt;.kittify/migration-ledger.jsonl&lt;/code&gt;
already exists, and builds the row through the ledger module’s own record builder. The reason is a
narrow re-run path for one cheap, idempotent move: where no migration ledger exists, the command
moves the keys and reports &lt;code dir=&quot;auto&quot;&gt;not_recorded&lt;/code&gt;, so it never adopts the ledger for a project that has
not chosen to.&lt;/p&gt;
&lt;h3 id=&quot;consequences&quot;&gt;Consequences&lt;/h3&gt;
&lt;h4 id=&quot;positive&quot;&gt;Positive&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;A deactivation holds under “absent = all”, across the interview, presets, synthesis, cascade and
upgrades.&lt;/li&gt;
&lt;li&gt;One file answers “what is active here”; doctor reports every divergent surface.&lt;/li&gt;
&lt;li&gt;Deactivating a required artifact fails loudly instead of being silently ineffective.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Downgrade hazard&lt;/strong&gt; (operator ruling &lt;code dir=&quot;auto&quot;&gt;older_cli_downgrade&lt;/code&gt;). The activation keys leave
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;. An older CLI reads no &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; keys there, so it treats every kind as
absent, which means &lt;strong&gt;everything is in force&lt;/strong&gt;. A project moved to the ledger and then opened
with an older CLI silently widens its activation, and a deactivation made under the new CLI is
ignored. We accept this and mitigate it: the changelog’s Upgrade Notes and this ADR state it,
and doctor flags activation keys that reappear in &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt;. No unknown
keys are added to &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;A merged branch or an older CLI can write legacy keys after the ledger exists. They are ignored
(the ledger wins), warned about once per process, and reported by doctor as an error. A
reconcile command that merges them is deferred.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SPDD probe residual (decision D-07).&lt;/strong&gt; The offering-side SPDD activation probe reads through
the kernel resolver and applies &lt;code dir=&quot;auto&quot;&gt;allow and not deny&lt;/code&gt;, but &lt;strong&gt;applies no org required floor&lt;/strong&gt;,
because the floor lives in activation and &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; must not import it (C-002). A
stale deny entry for an org-required id can therefore make the probe read the artifact as
inactive while the resolver-served context, which applies the floor, serves it. The resolver
path is the authority, and doctor warns on the stale entry (&lt;code dir=&quot;auto&quot;&gt;DENY_REQUIRED_ID&lt;/code&gt;). We accept the
residual rather than replicate the org scan in the offering.&lt;/li&gt;
&lt;li&gt;Fail-open callers (&lt;code dir=&quot;auto&quot;&gt;gate_bindings&lt;/code&gt;, the mission-step contract executor, preflight) now let
&lt;code dir=&quot;auto&quot;&gt;ActiveCharterConfigError&lt;/code&gt; propagate instead of serving an unfiltered graph.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The selection overlay gains requirements inherited through &lt;code dir=&quot;auto&quot;&gt;extends:&lt;/code&gt;, because the floor that
is subtracted from deny and the floor that is unioned into &lt;code dir=&quot;auto&quot;&gt;selected_*&lt;/code&gt; must be the same set.
This is a behaviour alignment, announced in the changelog.&lt;/li&gt;
&lt;li&gt;The &lt;code dir=&quot;auto&quot;&gt;deny_change&lt;/code&gt; guard is a plain keyword, not a minted token; the static gate gives the
structural protection.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;confirmation&quot;&gt;Confirmation&lt;/h3&gt;
&lt;p&gt;Portable, data-driven acceptance cases (&lt;code dir=&quot;auto&quot;&gt;activation-ledger-conformance/1&lt;/code&gt;) pin the fixed answers:
the effective set under deny, identity-space matching, the cascade report, the required refusal
and the migration move. Per operator ruling &lt;code dir=&quot;auto&quot;&gt;conformance_corpus&lt;/code&gt;, the cases live in the ported test cases and are meant to port to the open-packs content and the Java offering; there is no separate export script. The FR-014 gate covers every registered migration and built-in preset. A
dogfood run of &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate activation-ledger&lt;/code&gt; on this repository moves its own keys.&lt;/p&gt;
&lt;h2 id=&quot;revisit-triggers&quot;&gt;Revisit Triggers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;locked&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;enforced&lt;/code&gt; mutability levels (spec-kitty-charter ADR-0012) land in core: they join
the refusal seam of Decision 6.&lt;/li&gt;
&lt;li&gt;The Java offering’s filtering (#65) ships: re-check that the SPDD probe residual still holds.&lt;/li&gt;
&lt;li&gt;Users hit stray legacy keys in practice: build the deferred reconcile command.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;out-of-scope&quot;&gt;Out of Scope&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;spec-kitty-charter ADR-0013 Decision 7 (activation as an additive contract set on the charter
API): a later contract-set change in spec-kitty-charter.&lt;/li&gt;
&lt;li&gt;Changes in the spec-kitty-charter repository (C-006); this ADR only cites it.&lt;/li&gt;
&lt;li&gt;Project-charter &lt;code dir=&quot;auto&quot;&gt;required_directives&lt;/code&gt;, mission types and &lt;code dir=&quot;auto&quot;&gt;activated_kinds&lt;/code&gt;, which are not
artifact kinds and get no deny-list.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;more-information&quot;&gt;More Information&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Source ADR: spec-kitty-charter ADR-0013, and issues
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/62&quot;&gt;#62&lt;/a&gt;,
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/63&quot;&gt;#63&lt;/a&gt;,
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/64&quot;&gt;#64&lt;/a&gt;,
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/66&quot;&gt;#66&lt;/a&gt;,
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/67&quot;&gt;#67&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Mission artifacts: &lt;a href=&quot;../../../kitty-specs/persistent-deactivation-ledger-01M59YAA/spec.md&quot;&gt;spec&lt;/a&gt;,
&lt;a href=&quot;../../../kitty-specs/persistent-deactivation-ledger-01M59YAA/plan.md&quot;&gt;plan&lt;/a&gt;,
&lt;a href=&quot;../../../kitty-specs/persistent-deactivation-ledger-01M59YAA/research.md&quot;&gt;research&lt;/a&gt;,
&lt;a href=&quot;../../../kitty-specs/persistent-deactivation-ledger-01M59YAA/data-model.md&quot;&gt;data model&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Glossary: &lt;a href=&quot;/context/charter/#activation-ledger&quot;&gt;Activation ledger&lt;/a&gt;,
&lt;a href=&quot;/context/charter/#exclusion&quot;&gt;Exclusion&lt;/a&gt;,
&lt;a href=&quot;/context/charter/#effective-deny&quot;&gt;Effective deny&lt;/a&gt;,
&lt;a href=&quot;/context/charter/#required-floor&quot;&gt;Required floor&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-10-20-the-reduced-flip-option-b-and-the-charter-contract-rulings&quot;&gt;Amendment 2026-10-20: the reduced flip (Option B) and the charter-contract rulings&lt;/h2&gt;
&lt;p&gt;Operator rulings of 2026-10-20, recorded as Mission decisions, after the charter-contract
impact assessment (&lt;a href=&quot;/architecture/activation-ledger-and-charter-contract/&quot;&gt;Activation Ledger and the Charter Contract&lt;/a&gt;).
Decisions 1, 2, 4, 5 and 6 stand. This amendment changes Decision 3 for unmigrated projects,
records the contract rulings and the residuals, and corrects one detail of Decision 7.&lt;/p&gt;
&lt;h3 id=&quot;mission_pivot_option_b-the-reduced-flip&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;mission_pivot_option_b&lt;/code&gt;: the reduced flip&lt;/h3&gt;
&lt;p&gt;The ledger flip shipped reduced; the work packages that would have swept every test fixture
onto the ledger were canceled.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Reads on an unmigrated project stay on the legacy allow keys.&lt;/strong&gt; The Decision 3 row
“absent | outside | present → fail closed” is superseded: such a project resolves to the
legacy surface, flagged &lt;code dir=&quot;auto&quot;&gt;unmigrated&lt;/code&gt;, and its &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;activated_kinds&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt; are read as before. A &lt;code dir=&quot;auto&quot;&gt;deactivated_&amp;#x3C;kind&gt;&lt;/code&gt; key found there is
never applied: each command warns once, doctor reports &lt;code dir=&quot;auto&quot;&gt;LEGACY_DENY_KEY&lt;/code&gt; (an error), and the
migration refuses it. A legacy save leaves a hand-written deny key it does not change where
it is.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deny writes on an unmigrated project refuse&lt;/strong&gt;, before any write and before the
required-floor read, naming &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate activation-ledger&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;refuse_unmigrated_deny_write&lt;/code&gt;). A cascade deactivation is refused as a whole. A
&lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt; deactivation records no deny entry and keeps the legacy target. Allow-only
writes (&lt;code dir=&quot;auto&quot;&gt;activate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--only&lt;/code&gt;, presets, a cascade that clears nothing) still succeed on the
legacy surface.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No ledger is created beside legacy keys.&lt;/strong&gt; Only the migration creates it there; a new
ledger beside them would strand the keys and widen the project to “absent = all”.
&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; and a fresh project write the ledger. A dangling &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; pointer stays
legacy, as on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;There is one mode.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ACTIVATION_STRICT&lt;/code&gt; and the tolerant/strict split are
deleted, and a gate asserts no reference remains.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Moved to the alignment epic&lt;/strong&gt; (epic child #6535, retire the legacy activation reader): the
strict fail-closed read of an unmigrated project, the full fixture sweep, removal of the
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; bootstrap allow-key copy (kept until then, copying allow keys only and only
when the source is legacy) and removal of the &lt;code dir=&quot;auto&quot;&gt;CharterYaml&lt;/code&gt; activation fields (kept so
unmigrated &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; files keep validating).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;contract_document_scope&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;contract_document_scope&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;activation.yaml&lt;/code&gt; does not hold the charter contract’s full &lt;code dir=&quot;auto&quot;&gt;ActivationConfig&lt;/code&gt;. Packs,
languages and context activations stay in their current homes, and a future anti-corruption
layer maps those homes onto the contract’s schema. Content alignment matters, not shape.&lt;/p&gt;
&lt;h3 id=&quot;required_always_active_divergence&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;required_always_active_divergence&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Core keeps its semantics: a required artifact is never subtracted by a deny, and is not added
under an explicit allow list that omits it. The difference from the charter service (required
and locked are always active on read) is logged as a divergence and settled before the remote
cutover. Doctor and &lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt; report such an omission (&lt;code dir=&quot;auto&quot;&gt;REQUIRED_OMITTED_BY_ALLOW_LIST&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;required_not_in_force&lt;/code&gt;), per R12.&lt;/p&gt;
&lt;h3 id=&quot;contract_rulings_r2_r12&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;contract_rulings_r2_r12&lt;/code&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;R2.&lt;/strong&gt; ADR &lt;a href=&quot;/adr/4.x/2026-10-16-1-extract-charter-offering-first-activation-rework-post-ga/&quot;&gt;2026-10-16-1&lt;/a&gt;
gains a dated amendment: after the 1.0.0 remote cutover the charter service is
authoritative and core’s file is the mapped local copy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;R3.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; accepts a declared id (#6423), folded into the cascade and activate
work; the allow list keeps one stem spelling per artifact.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;R4.&lt;/strong&gt; A deny choice for a whole-document register is deferred to the alignment epic.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;R5.&lt;/strong&gt; Unknown and stale deny entries stay inert in core and are dropped on export.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;R6.&lt;/strong&gt; NFR-003 is restated as no regression against the base; repository-scale latency is
#6506.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;R7.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--preset X --force&lt;/code&gt; clearing exclusions is logged as a divergence (the contract has no
force, and a preset never removes a deny entry).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;R8.&lt;/strong&gt; Core keeps its CLI verbs. They now map 1:1: spec-kitty-charter
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/issues/125&quot;&gt;#125&lt;/a&gt; answered core’s request 4,
so the contract’s &lt;code dir=&quot;auto&quot;&gt;select&lt;/code&gt; clears the named id’s own exclusion and &lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt; records the
exclusion and unselects. That is aligned, not a divergence, and needs no adapter composition.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;R9.&lt;/strong&gt; An &lt;code dir=&quot;auto&quot;&gt;appliedPresets&lt;/code&gt; sidecar belongs to the alignment epic.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;R10.&lt;/strong&gt; Export emits authored languages only.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;R11.&lt;/strong&gt; Core stores stems, emits declared ids, and refuses unknown tokens on export.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;R12.&lt;/strong&gt; Doctor and &lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt; warn about a required id that an explicit allow list omits.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;contract_epic_ga_milestone&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;contract_epic_ga_milestone&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Switching to the charter surface is a 4.0 deliverable: the alignment epic and all its children
go on the GA milestone (#11), whose target date is removed. This supersedes the post-GA timing
of ADR 2026-10-16-1 for the activation rework.&lt;/p&gt;
&lt;h3 id=&quot;mission_type_cascade_source&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;mission_type_cascade_source&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;A mission type is a cascade source: &lt;code dir=&quot;auto&quot;&gt;charter activate mission-type X --cascade&lt;/code&gt; walks the
mission type’s references with the same scope, skip and stop-at-deny rules (Decision 5). It was
folded into the cascade work package; the decision record’s “a new WP” wording is superseded.&lt;/p&gt;
&lt;h3 id=&quot;replies-to-spec-kitty-charter-adr-0020-requests-to-core&quot;&gt;Replies to spec-kitty-charter ADR-0020 “Requests to core”&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Item 1&lt;/strong&gt; (stop the flat file rejecting the document): answered “mapped at the seam”. Under
&lt;code dir=&quot;auto&quot;&gt;contract_document_scope&lt;/code&gt; the file never holds contract keys, so the ledger keeps its
unknown-key refusal.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The id-spelling request:&lt;/strong&gt; answered by R3 and R11.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The amendment to ADR 2026-10-16-1:&lt;/strong&gt; R2.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Select and deactivate (request 4):&lt;/strong&gt; aligned 1:1 (R8, spec-kitty-charter #125).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;the-divergence-register&quot;&gt;The divergence register&lt;/h3&gt;
&lt;p&gt;Every divergence that is not aligned, ruled or open, is data: the &lt;code dir=&quot;auto&quot;&gt;divergences:&lt;/code&gt; section of
&lt;a href=&quot;../../../tests/charter/conformance/activation_ledger_cases.yaml&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;tests/charter/conformance/activation_ledger_cases.yaml&lt;/code&gt;&lt;/a&gt;,
each naming its conformance cases. Aligned rows (Activate, Deactivate) are not divergences and
live only in the
&lt;a href=&quot;/architecture/activation-ledger-and-charter-contract/#divergence-register&quot;&gt;divergence register&lt;/a&gt;
of the architecture page, which also carries each ruling’s status.&lt;/p&gt;
&lt;h3 id=&quot;decision-7-corrected&quot;&gt;Decision 7, corrected&lt;/h3&gt;
&lt;p&gt;The apply order is the ledger write, then each legacy file’s strip, authority first. The
synthesis manifest is stamped with the bundle’s post-strip hash just &lt;em&gt;before&lt;/em&gt; the &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;
strip, not as a last step, so a run that stops between the two writes still has legacy keys on
disk and the re-run finishes the move. A lagging manifest stamp alone is not this migration’s
business. A malformed or changed-meanwhile project fails the narrow command with
&lt;code dir=&quot;auto&quot;&gt;ACTIVATION_LEDGER_MIGRATION_FAILED&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;residuals&quot;&gt;Residuals&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The legacy &lt;code dir=&quot;auto&quot;&gt;.kittify/profiles&lt;/code&gt; overlay still serves a denied agent-profile id. It is outside the
activation model (C-002, FR-007).&lt;/li&gt;
&lt;li&gt;A hand-edited deny entry spelled as a declared id is not matched by the shipped
&lt;code dir=&quot;auto&quot;&gt;m_unify_charter_activation&lt;/code&gt; promotion, which compares raw spellings. Shipped migrations are not
edited (DIRECTIVE_044).&lt;/li&gt;
&lt;li&gt;The SPDD probe residual (decision D-07) is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;del&gt;The project-intent rename (#6443) renames the legacy &lt;code dir=&quot;auto&quot;&gt;mission-type-scope-directive&lt;/code&gt; in the
allow lists only.&lt;/del&gt; &lt;strong&gt;Closed by #6565&lt;/strong&gt; (Amendment 2026-10-31): the rename carries the deny entry
too, through one narrowing &lt;code dir=&quot;auto&quot;&gt;DenyListChoice.RENAME&lt;/code&gt;. FR-014 stays absolute for every other path.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-10-25-6629-an-upgrade-never-writes-an-absent-activation-key&quot;&gt;Amendment 2026-10-25 (#6629): an upgrade never writes an absent activation key&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Decision.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;unify_charter_activation_promote_answers&lt;/code&gt; seeded an absent &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; key
with the kind’s whole in-force set before it appended the interview selections. It is now a
recorded no-op, superseded by &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_promote_interview_selections&lt;/code&gt; (ADR 2026-10-17-1,
Amendment 2026-10-25, #6629). The successor:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;writes through the one activation write target (&lt;code dir=&quot;auto&quot;&gt;resolve_activation_write_target&lt;/code&gt;): the
activation ledger once &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_activation_ledger&lt;/code&gt; has moved the keys, and the legacy source in
place on a project not yet migrated;&lt;/li&gt;
&lt;li&gt;appends only to a present list;&lt;/li&gt;
&lt;li&gt;never writes an absent key.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;So after an upgrade, an absent key still means “every available artifact is in force, and no
operator chose a list”. &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; keeps its fresh-project seed and does not demand a
companion tactic per directive.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Residual closed.&lt;/strong&gt; The deny-spelling residual above (the shipped promotion compared deny entries
as raw spellings) is closed. The successor leaves the deny check to the promotion primitive, which
applies the effective deny in identity space (less the org required floor), so a deny entry
spelled by its declared id is honoured.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Narrower scope, known.&lt;/strong&gt; The successor resolves interview selections against the built-in pack
only, as the shipped step did. An interview id that only an org pack declares is reported as
unresolved and not promoted.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Residual kept (closed by Amendment 2026-10-31).&lt;/strong&gt; Two operator-time writers still turn an absent key into the full in-force set
when they add to it:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter interview&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;--narrow-activation&lt;/code&gt;;&lt;/li&gt;
&lt;li&gt;a first &lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt;&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;--only&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Running either after the upgrade brings the #6629 synthesis behaviour back. #6408 owns those
writers. This amendment changes only what an upgrade writes.&lt;/p&gt;
&lt;h2 id=&quot;amendment-2026-10-31-6685-no-writer-fills-an-absent-activation-key&quot;&gt;Amendment 2026-10-31 (#6685): no writer fills an absent activation key&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Decision.&lt;/strong&gt; One rule: an absent &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; key of a kind with
&lt;code dir=&quot;auto&quot;&gt;effective_when_absent: all&lt;/code&gt; means every available artifact is in force, so no writer fills it.
&lt;code dir=&quot;auto&quot;&gt;charter interview&lt;/code&gt; (without &lt;code dir=&quot;auto&quot;&gt;--narrow-activation&lt;/code&gt;) and a first &lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt;&lt;/code&gt;
(without &lt;code dir=&quot;auto&quot;&gt;--only&lt;/code&gt;) join the upgrade promotion of #6629 and #6683. This reverses #4253’s
materialise-on-first-activate: writing the in-force set froze the catalogue and, read by
&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; as an operator’s activation, blocked &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;synthesized_drg missing&lt;/code&gt;. Both writers now say what they left absent and how to write a list.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Exceptions.&lt;/strong&gt; The rule does not apply to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt;, whose absent key puts nothing in force;&lt;/li&gt;
&lt;li&gt;kinds with &lt;code dir=&quot;auto&quot;&gt;effective_when_absent: required&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;skill&lt;/code&gt;), whose absent key puts only the
org-required set in force: their selection is written;&lt;/li&gt;
&lt;li&gt;an id that is not in the resolved effective set, which &lt;code dir=&quot;auto&quot;&gt;activate&lt;/code&gt; materialises as before;&lt;/li&gt;
&lt;li&gt;an unresolved effective set: &lt;code dir=&quot;auto&quot;&gt;activate&lt;/code&gt; cannot prove the id is in force and writes a list. The
interview decides per kind, not per id (its ids are resolved against the catalogue), so it leaves
the key absent;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--only&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--narrow-activation&lt;/code&gt;, which are the explicit choice to write a list;&lt;/li&gt;
&lt;li&gt;a key that already holds a list, which is appended to.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Home.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;absent_key_stays_implicit(effective_when_absent, *, key_present)&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;charter.activation.activation_engine&lt;/code&gt;, re-exported by &lt;code dir=&quot;auto&quot;&gt;charter.activation.api&lt;/code&gt;. The activate
planner, the interview split and the org-required seed (&lt;code dir=&quot;auto&quot;&gt;_INTERVIEW_SEEDED_KIND_FIELDS&lt;/code&gt;) call it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Consequence for cascade.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter deactivate &amp;#x3C;kind&gt; &amp;#x3C;id&gt; --cascade&lt;/code&gt; removes a child only from a
kind with a written list. Children of a kind with none stay in force, and each is reported with its
&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter deactivate &amp;#x3C;kind&gt; &amp;#x3C;id&gt;&lt;/code&gt; command (#6873).&lt;/p&gt;
&lt;h2 id=&quot;amendment-2026-10-31-6565-the-project-intent-rename-carries-an-exclusion&quot;&gt;Amendment 2026-10-31 (#6565): the project-intent rename carries an exclusion&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Decision.&lt;/strong&gt; The project-intent rename (&lt;code dir=&quot;auto&quot;&gt;#6443&lt;/code&gt;) now rewrites the legacy
&lt;code dir=&quot;auto&quot;&gt;NNN-mission-type-scope-directive&lt;/code&gt; stem in the activation ledger’s deny lists as well as its allow
lists, so an exclusion the user recorded by the old stem keeps applying once the artifact is renamed.&lt;/p&gt;
&lt;p&gt;The window it closes is narrow but reachable (the residual recorded under the 2026-10-20 amendment):
the rename is refused or skipped (for example &lt;code dir=&quot;auto&quot;&gt;#6539&lt;/code&gt;, no git repository), the project moves to the
ledger, the user runs &lt;code dir=&quot;auto&quot;&gt;charter deactivate directive &amp;#x3C;NNN&gt;-mission-type-scope-directive&lt;/code&gt;, and the
rename runs later through an upgrade retry, &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;charter resynthesize&lt;/code&gt;. The deny
entry then named a stem that no longer existed, was reported as &lt;code dir=&quot;auto&quot;&gt;DENY_UNKNOWN_ID&lt;/code&gt;, and the renamed
&lt;code dir=&quot;auto&quot;&gt;project-intent-directive&lt;/code&gt; was back in force.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Where.&lt;/strong&gt; The one rename helper (&lt;code dir=&quot;auto&quot;&gt;charter/activation/synthesizer/legacy_rename.py&lt;/code&gt;) carries it, in
the same single ledger write as the allow rename, reusing the helper’s own old→new stem mapping.
There is no second mapping and no raw deny write.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;How much authority.&lt;/strong&gt; One new &lt;code dir=&quot;auto&quot;&gt;DenyListChoice.RENAME&lt;/code&gt;, minted in that helper and nowhere else. It
moves one entry between two spellings of the same artifact; it never adds and never removes a
denial. The deny-list gate pins the origin in both directions and carries a positive control, so the
allowance is provably used and cannot widen silently.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Where it does not apply.&lt;/strong&gt; Only the activation ledger. A hand-written legacy deny key on
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; is left where it is (it was never applied there, and the legacy save
refuses a deny change), and a deny entry spelled by a declared id (&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_003&lt;/code&gt;) is untouched
because ids are not renamed.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Rejected alternative.&lt;/strong&gt; Refusing the rename while a deny entry names the old stem. It would fail
&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; and leave &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; permanently broken on a project whose state the
user cannot see, for a deactivation that is still theirs to keep.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Residual kept.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;#6539&lt;/code&gt; (the rename skipped when a project has no git repository) is not fixed
here; this amendment makes that state harmless on the next run rather than removing the trigger.&lt;/p&gt;
&lt;h2 id=&quot;amendment-2026-11-01-6684-the-seeded-list-warning-covers-a-released-preset-seed&quot;&gt;Amendment 2026-11-01 (#6684): the seeded-list warning covers a released-preset seed&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Decision.&lt;/strong&gt; No follow-up migration resets an activation list an earlier build filled. &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; keeps reporting such a list and never narrows it, so a deliberate activate-all (#6499) is never
silently undone. The &lt;em&gt;warning’s&lt;/em&gt; known gap is fixed instead: a list an earlier build wrote from a
&lt;strong&gt;released&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;default&lt;/code&gt; activation preset is recognised even though the catalogue has grown since.&lt;/p&gt;
&lt;p&gt;The gap: &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_promote_interview_selections&lt;/code&gt; recognised a machine-written list by set-equality with
&lt;strong&gt;today’s&lt;/strong&gt; in-force set. &lt;code dir=&quot;auto&quot;&gt;unify_charter_activation_promote_answers&lt;/code&gt; seeded an absent key from the
released &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt; of the CLI that ran it (&lt;code dir=&quot;auto&quot;&gt;charter.default_pack.load_default_pack_activation_ids&lt;/code&gt;,
3.2.6rc1 through the #4400 effective-set rewrite), so a project seeded then holds that release’s preset
ids (19 directives, not today’s 38). Equality with today’s set fails, and the upgrade said nothing while
&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; still demanded a companion tactic per listed directive.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;What the warning compares against.&lt;/strong&gt; Two provenances, one per key: today’s whole in-force set (as
before), and the released preset lists frozen in
&lt;code dir=&quot;auto&quot;&gt;upgrade/migrations/_charter_pack_cutover_snapshots.DEFAULT_SNAPSHOTS&lt;/code&gt; — the same comparand
&lt;code dir=&quot;auto&quot;&gt;_charter_pack_cutover_resets&lt;/code&gt; already uses. The preset provenance accepts the preset itself and the
preset plus interview ids the preset lacks (the shape the superseded seeding produced), and rejects a
hand-picked list that merely overlaps it or holds an id no longer in force. Nothing is written; the
warning names &lt;code dir=&quot;auto&quot;&gt;charter interview --narrow-activation&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt; --only&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Why not a reset.&lt;/strong&gt; Set-equality cannot tell a seeded list from an operator’s deliberate one, and no
provenance is recorded: the activation ledger’s L1 validation refuses a provenance key, and a key
added now could not be backfilled for lists already written. A reset would therefore silently undo
#6499’s choice. The provenance question is answered in synthesis, by the #6685 amendment above, not by
rewriting activation state during an upgrade.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Home.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;_seeded_list_hints&lt;/code&gt; and its message &lt;code dir=&quot;auto&quot;&gt;_SEEDED_PRESET_HINT&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;m_4_0_0rc8_promote_interview_selections.py&lt;/code&gt;; the released lists stay owned by the frozen snapshot
module, never a live preset file.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Residual kept.&lt;/strong&gt; A list an earlier build seeded from a &lt;em&gt;whole-catalogue&lt;/em&gt; effective set is matched only
while the catalogue is unchanged: the comparison is today’s in-force set, because no per-release catalogue
snapshot is kept. That case is not reachable with any released CLI today — the effective-set seeding era
(4.0.0rc6/4.0.0rc7) shipped the same catalogue as now for every kind. If a future release grows the
catalogue, a project seeded by 4.0.0rc6/rc7 would fall into the gap; the fix then is a frozen
per-release catalogue set beside the preset snapshots, not a reset.&lt;/p&gt;</content>
</entry>
