<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-04-15-2-explicit-empty-charter-selections-remain-empty/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-04-15-2-explicit-empty-charter-selections-remain-empty/</id>
  <title>ADR 2026-04-15-2: Explicit Empty Charter Selections Remain Empty</title>
  <updated>2026-04-15T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-04-15-2-explicit-empty-charter-selections-remain-empty/"/>
  <summary>An empty paradigm, directive, or tool selection compiles to empty; the charter compiler may never silently expand an explicit empty list into shipped defaults.</summary>
  <content type="html">&lt;h2 id=&quot;context&quot;&gt;Context&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate&lt;/code&gt; compiles a project charter from
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/interview/answers.yaml&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;That interview schema includes explicit selection lists for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;selected_paradigms&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;selected_directives&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;available_tools&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;During emergency hardening of the charter flow, it became clear that the
compiler treated explicit empty selections as “apply all shipped defaults”.
That behavior is wrong.&lt;/p&gt;
&lt;p&gt;If the interview or the agent leaves one of these lists empty, that means one of
two things:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;no shipped doctrine/tooling cleanly fits the user’s needs yet, or&lt;/li&gt;
&lt;li&gt;the user deliberately does not want shipped doctrine/tooling imposed.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Broadening an explicit empty list into the full catalog force-feeds doctrine
that the user did not ask for, misrepresents the interview outcome, and makes
the generated charter less truthful than the source answers.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;p&gt;Explicit empty charter selections remain empty.&lt;/p&gt;
&lt;p&gt;Specifically:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;selected_paradigms: []&lt;/code&gt; stays &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;selected_directives: []&lt;/code&gt; stays &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;available_tools: []&lt;/code&gt; stays &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The compiler must not silently expand an explicit empty selection into mission
defaults or the full packaged catalog.&lt;/p&gt;
&lt;p&gt;Defaults remain valid only when the user explicitly asks for defaults or when a
bootstrap path generates non-empty default interview data before compilation.&lt;/p&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;h3 id=&quot;positive&quot;&gt;Positive&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The generated charter reflects the interview truthfully.&lt;/li&gt;
&lt;li&gt;Users are not force-fed shipped doctrine they did not ask for.&lt;/li&gt;
&lt;li&gt;Doctrine gaps can be represented honestly as project-specific charter policy.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.charter&lt;/code&gt; can safely say “do not force a near-match” and the
compiler will honor it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;negative&quot;&gt;Negative&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Some generated charters will be intentionally sparse until doctrine is added
or the user chooses concrete shipped selections.&lt;/li&gt;
&lt;li&gt;Existing assumptions that “empty means defaults” must not be reintroduced in
future compiler or CLI refactors.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;rules-going-forward&quot;&gt;Rules Going Forward&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Treat empty lists as an intentional state, not missing data.&lt;/li&gt;
&lt;li&gt;If defaults are desired, they must be made explicit before compilation.&lt;/li&gt;
&lt;li&gt;Any future charter compiler rewrite must preserve this invariant.&lt;/li&gt;
&lt;li&gt;Reviewers should reject changes that broaden explicit empty selections.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;implementation-notes&quot;&gt;Implementation Notes&lt;/h2&gt;
&lt;p&gt;The invariant is enforced in the charter compiler sanitization path and covered
by regression tests asserting that compiled selections and rendered charter
output preserve empty lists exactly.&lt;/p&gt;</content>
</entry>
