<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/changelog/release-goals/">
  <id>https://docs.spec-kitty.ai/changelog/release-goals/</id>
  <title>Release Goals — Declarations of Intent</title>
  <updated>2026-08-10T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/changelog/release-goals/"/>
  <summary>Explains the release-goals convention: one durable declaration of intent per emergent minor release milestone, scoped by minor cycle rather than by individual patch.</summary>
  <content type="html">&lt;span id=&quot;release-goals--declarations-of-intent&quot;&gt;&lt;/span&gt;
&lt;p&gt;This directory holds one &lt;strong&gt;declaration of intent&lt;/strong&gt; per &lt;em&gt;emergent release milestone&lt;/em&gt;. It is the
durable, version-controlled record of &lt;strong&gt;what a release cycle is trying to achieve and why&lt;/strong&gt; — the
counterpart to a sprint goal, scaled to a release cycle.&lt;/p&gt;
&lt;h2 id=&quot;the-emergent-release-milestones-model&quot;&gt;The “emergent release milestones” model&lt;/h2&gt;
&lt;p&gt;We scope by &lt;strong&gt;minor cycle&lt;/strong&gt;, not by individual patch:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A milestone is named for a minor cycle: &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;3.2.x&lt;/code&gt;&lt;/strong&gt;, &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;3.3.x&lt;/code&gt;&lt;/strong&gt; (plus a retroactive point-in-time
&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;3.2.0&lt;/code&gt;&lt;/strong&gt; for what already shipped).&lt;/li&gt;
&lt;li&gt;A minor cycle has &lt;strong&gt;one goal&lt;/strong&gt; (or a small coherent set). Multiple &lt;strong&gt;emergent patches&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;3.2.1&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.2.2&lt;/code&gt;, …) each advance that &lt;em&gt;same&lt;/em&gt; goal. The cycle’s milestone stays &lt;strong&gt;open until the
goal is structurally met&lt;/strong&gt; — then it closes and the next cycle is declared.&lt;/li&gt;
&lt;li&gt;This gives the freedom to split a minor cycle into as many patches as the work needs, without
re-litigating scope each time.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;three-surfaces-one-goal--and-how-they-connect&quot;&gt;Three surfaces, one goal — and how they connect&lt;/h2&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Surface&lt;/th&gt;&lt;th&gt;Role&lt;/th&gt;&lt;th&gt;Lives in&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Declaration of intent&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The full goal · rationale · scope · non-goals · success criteria · emergent-patch plan&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;docs/changelog/&amp;#x3C;minor&gt;.md&lt;/code&gt; (this section) — PR-reviewed, durable&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Milestone&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The burndown / “what’s left” tracking surface&lt;/td&gt;&lt;td&gt;GitHub milestone &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;minor&gt;&lt;/code&gt; — one-line goal + a link back here&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Mission&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The execution of a patch toward the goal&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/&lt;/code&gt; + its &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The declaration is the &lt;strong&gt;source of truth for intent&lt;/strong&gt;; the milestone description is a short pointer
(it is ephemeral, char-limited, and not reviewable). A mission’s &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; is the per-patch
closure ledger that rolls up into the milestone burndown.&lt;/p&gt;
&lt;h2 id=&quot;authoring-a-new-cycle&quot;&gt;Authoring a new cycle&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Write &lt;code dir=&quot;auto&quot;&gt;docs/changelog/&amp;#x3C;minor&gt;.md&lt;/code&gt; from the template shape (see &lt;a href=&quot;/changelog/3.2.x/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;3.2.x.md&lt;/code&gt;&lt;/a&gt;): &lt;strong&gt;Goal · Why now ·
Scope · Non-goals · Success criteria · Emergent patches · Links&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Create the GitHub milestone &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;minor&gt;&lt;/code&gt; (open); put the one-line goal in its description with a link
here. (Closed/retroactive milestones must be populated via the API by &lt;em&gt;number&lt;/em&gt; — &lt;code dir=&quot;auto&quot;&gt;gh issue edit --milestone&lt;/code&gt; only resolves &lt;em&gt;open&lt;/em&gt; milestones by title.)&lt;/li&gt;
&lt;li&gt;Attach the cycle’s in-flight issues to the milestone.&lt;/li&gt;
&lt;li&gt;As patches ship, keep the declaration’s success-criteria checklist honest; close the milestone +
declaration when the goal is structurally met.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;See &lt;a href=&quot;/operations/how-to-maintain/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;how-to-maintain.md&lt;/code&gt;&lt;/a&gt; for the tracker structure, priority levels, and
issue types this plugs into.&lt;/p&gt;
&lt;h2 id=&quot;declared-cycles&quot;&gt;Declared cycles&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/changelog/3.2.x/&quot;&gt;3.2.x goals&lt;/a&gt; — focus for the 3.2.x line.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/changelog/3.3.x/&quot;&gt;3.3.x goals&lt;/a&gt; — &lt;strong&gt;retired&lt;/strong&gt; (milestone closed 2026-08-23; work re-triaged into
4.0.0 or Product backlog). Kept as the historical declaration.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/changelog/4.0.0/&quot;&gt;4.0.0 goals&lt;/a&gt; — hosted collaboration + the open-core structural finish;
supersedes the 3.3.x hosted/experience declaration.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
