<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/development/reference/version-taxonomy/">
  <id>https://docs.spec-kitty.ai/development/reference/version-taxonomy/</id>
  <title>Version taxonomy</title>
  <updated>2026-09-30T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/development/reference/version-taxonomy/"/>
  <summary>The five version-relevance tags every docs page carries, what each means for the active release line, and how the leakage check enforces them.</summary>
  <content type="html">&lt;span id=&quot;version-taxonomy&quot;&gt;&lt;/span&gt;
&lt;p&gt;Every page in the docs inventory carries exactly one &lt;strong&gt;version tag&lt;/strong&gt;. The tag
answers one question for a reader: &lt;em&gt;does this page describe the Spec Kitty
release line I am running?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The tags are relative to the &lt;strong&gt;active release line&lt;/strong&gt;, the line &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; ships
from. That is currently 4.x. See the charter’s Branch and Release Strategy
section. When the active line changes, the tags keep their meaning, and no
page needs renaming.&lt;/p&gt;
&lt;p&gt;The enum lives in &lt;code dir=&quot;auto&quot;&gt;scripts/docs/_inventory.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;VersionTag&lt;/code&gt;). The generated
inventory is &lt;code dir=&quot;auto&quot;&gt;docs/development/page-inventory.yaml&lt;/code&gt;. The leakage check is
&lt;code dir=&quot;auto&quot;&gt;scripts/docs/version_leakage_check.py&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;the-five-tags&quot;&gt;The five tags&lt;/h2&gt;



































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Tag&lt;/th&gt;&lt;th&gt;Use it for&lt;/th&gt;&lt;th&gt;Banner&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;current&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Pages that describe the active release line: installed CLI behaviour, shipped doctrine, the mission workflow, the reference. New pages default here.&lt;/td&gt;&lt;td&gt;None. It must not carry an archive or migration banner.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;supported&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Pages written for the previous release line whose behaviour still holds, but that have not been re-audited for the active line.&lt;/td&gt;&lt;td&gt;None required. A short “last audited against X” note is recommended.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;archival&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Material from retired lines (1.x, 2.x and so on), kept for the record under &lt;code dir=&quot;auto&quot;&gt;docs/archive/&lt;/code&gt;.&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Required.&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;migration&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Pages whose main purpose is to move a reader from an earlier line to the active one (&lt;code dir=&quot;auto&quot;&gt;docs/migration/&lt;/code&gt;).&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Required.&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;internal&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Maintainer and contributor material (&lt;code dir=&quot;auto&quot;&gt;docs/development/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;docs/architecture/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;docs/plans/&lt;/code&gt;).&lt;/td&gt;&lt;td&gt;None. It is ignored on both sides of a link.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The required banner is a blockquote within the first 20 non-empty lines
that matches:&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;text&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;^&gt;\s*(?:Archive notice|Migration note)\b&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;h2 id=&quot;invariants&quot;&gt;Invariants&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Every inventoried page maps to exactly one tag.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;archival&lt;/code&gt; implies &lt;code dir=&quot;auto&quot;&gt;current_target: false&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;current&lt;/code&gt; implies &lt;code dir=&quot;auto&quot;&gt;current_target: true&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;internal&lt;/code&gt; pages are excluded from &lt;code dir=&quot;auto&quot;&gt;current_target&lt;/code&gt; validation.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;scripts/docs/_inventory.py&lt;/code&gt; enforces the invariants when the inventory is
loaded.&lt;/p&gt;
&lt;h2 id=&quot;how-the-leakage-check-uses-the-tags&quot;&gt;How the leakage check uses the tags&lt;/h2&gt;
&lt;p&gt;In-file frontmatter is the source of truth for each page. The inventory
is regenerated from it, and the &lt;code dir=&quot;auto&quot;&gt;INVENTORY-LOCKFILE-DRIFT&lt;/code&gt; gate in
&lt;code dir=&quot;auto&quot;&gt;scripts/docs/check_docs_freshness.py&lt;/code&gt; blocks drift between the two. The
leakage check then reports:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;LEAK-CURRENT-LINKS-ARCHIVAL&lt;/code&gt;: a &lt;code dir=&quot;auto&quot;&gt;current&lt;/code&gt; page links to an &lt;code dir=&quot;auto&quot;&gt;archival&lt;/code&gt;
page that has no migration banner.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;LEAK-MISSING-BANNER&lt;/code&gt;: an &lt;code dir=&quot;auto&quot;&gt;archival&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;migration&lt;/code&gt; page has no banner.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;LEAK-MISSING-INVENTORY&lt;/code&gt;: a markdown file under &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; is not in the
inventory.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;LEAK-MISSING-FILE&lt;/code&gt;: an inventory row points at a file that does not
exist.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;history&quot;&gt;History&lt;/h2&gt;
&lt;p&gt;The taxonomy was introduced by the 3.2 documentation mission
(&lt;code dir=&quot;auto&quot;&gt;spec-kitty-3-2-docs-01KS4KSZ&lt;/code&gt;, FR-001). It was made version-neutral on
2026-09-30, when the 4.x line became active. The mission’s &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;data-model.md&lt;/code&gt; keep the original 3.2-anchored wording.&lt;/p&gt;</content>
</entry>
