<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/changelog/1x/branches-and-workspaces/">
  <id>https://docs.spec-kitty.ai/changelog/1x/branches-and-workspaces/</id>
  <title>1.x Branch and Workspace Model</title>
  <updated>2026-06-03T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/changelog/1x/branches-and-workspaces/"/>
  <summary>Historical Spec Kitty 1.x archive page for 1.x Branch and Workspace Model; use Spec Kitty 3.2 docs for current projects and upgrades.</summary>
  <content type="html">&lt;blockquote&gt;
&lt;p&gt;Archive notice: This page documents historical Spec Kitty behavior and is not the current 3.2 workflow. Start with &lt;a href=&quot;/context/&quot;&gt;Spec Kitty 3.2&lt;/a&gt; for current docs.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;span id=&quot;1x-branch-and-workspace-model&quot;&gt;&lt;/span&gt;
&lt;h2 id=&quot;feature-centric-branching&quot;&gt;Feature-Centric Branching&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Each feature is tracked as a branch-scoped workspace.&lt;/li&gt;
&lt;li&gt;Work packages are executed in isolated working directories.&lt;/li&gt;
&lt;li&gt;Merge operations close the feature workflow by integrating approved work.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;execution-discipline&quot;&gt;Execution Discipline&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Work packages should move through lane states in order.&lt;/li&gt;
&lt;li&gt;Planning artifacts are the contract for implementation and review.&lt;/li&gt;
&lt;li&gt;Charter principles are applied before final acceptance.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;typical-1x-paths&quot;&gt;Typical 1.x Paths&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Feature artifacts: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;feature&gt;/...&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Runtime/project state: &lt;code dir=&quot;auto&quot;&gt;.kittify/...&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Command templates and mission defaults from packaged mission/template roots (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/**&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/templates/**&lt;/code&gt;) and project overrides.&lt;/li&gt;
&lt;/ol&gt;</content>
</entry>
