<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/changelog/3.3.x/">
  <id>https://docs.spec-kitty.ai/changelog/3.3.x/</id>
  <title>3.3.x — Experience &amp; surface: UX, dashboard, flows, SaaS + emergent-domain strangling</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/changelog/3.3.x/"/>
  <summary>Declaration of intent for the 3.3.x cycle: experience and outward surface (UX, dashboard, flows, SaaS) while strangling the next emergent domains onto their SSOTs.</summary>
  <content type="html">&lt;span id=&quot;33x--experience--surface-ux-dashboard-flows-saas--emergent-domain-strangling&quot;&gt;&lt;/span&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Superseded.&lt;/strong&gt; The 3.3.x cycle was retired on 2026-08-23 without shipping; its hosted and experience work was re-triaged into the 4.0.0 cycle. The active cycle is 4.0.0 — see the &lt;a href=&quot;/plans/4-0-0-milestone-roadmap/&quot;&gt;4.0.0 roadmap&lt;/a&gt;. Kept as a record of the cycle’s intent.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Milestone:&lt;/strong&gt; &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/milestone/5&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;3.3.x&lt;/code&gt;&lt;/a&gt; (retired) ·
&lt;strong&gt;Status:&lt;/strong&gt; retired 2026-08-23 (never shipped; historical record) · &lt;strong&gt;Declared:&lt;/strong&gt; 2026-06-16 · &lt;strong&gt;Advances:&lt;/strong&gt; #1619 (continued
domain extraction), the dashboard/SaaS surfaces.&lt;/p&gt;
&lt;h2 id=&quot;theme&quot;&gt;Theme&lt;/h2&gt;
&lt;p&gt;With the &lt;strong&gt;core domains&lt;/strong&gt; strangled onto their SSOTs in 3.2.x, 3.3.x turns to the &lt;strong&gt;experience and
outward surface&lt;/strong&gt; — how operators and users actually interact with Spec Kitty — while continuing to
&lt;strong&gt;extract and strangle the &lt;em&gt;next&lt;/em&gt; emergent domains&lt;/strong&gt; as they surface from the 3.2.x work. Same
discipline: no new shadow paths; route or extract, never duplicate.&lt;/p&gt;
&lt;h2 id=&quot;goals&quot;&gt;Goals&lt;/h2&gt;
&lt;h3 id=&quot;g1--ux--dashboard-look-and-feel&quot;&gt;G1 — UX &amp;#x26; dashboard look-and-feel&lt;/h3&gt;
&lt;p&gt;Polish the dashboard’s visual design and information architecture; make status, missions, lanes, and
identity legible at a glance. (Builds directly on the 3.2.x naming/identity SSOT — the dashboard
already consumes the read kernel; once it stops re-deriving, its data is trustworthy to design over.)&lt;/p&gt;
&lt;h3 id=&quot;g2--user-flows&quot;&gt;G2 — User flows&lt;/h3&gt;
&lt;p&gt;Smooth the end-to-end operator/user journeys (specify → plan → tasks → implement → review → merge →
retrospective, and the ad-hoc/dispatch paths) — reduce friction, dead-ends, and “which command now?”
moments.&lt;/p&gt;
&lt;h3 id=&quot;g3--saas-tie-in&quot;&gt;G3 — SaaS tie-in&lt;/h3&gt;
&lt;p&gt;Strengthen the hosted/SaaS integration — sync, tracker connectors, dossiers, auth — as a coherent
surface rather than a set of bolt-ons.&lt;/p&gt;
&lt;h3 id=&quot;g4--strangle-the-next-emergent-domains&quot;&gt;G4 — Strangle the next emergent domains&lt;/h3&gt;
&lt;p&gt;Continue the #1619 decomposition into the domains that emerge once the core set is done (whatever the
3.2.x slices surface). &lt;strong&gt;#1878 is no longer this cycle’s example&lt;/strong&gt; — see the superseded note below.
Extract → route → enforce, as in 3.2.x.&lt;/p&gt;
&lt;h2 id=&quot;carried-in-from-32x&quot;&gt;Carried in from 3.2.x&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Any core-domain slice that 3.2.x scoped but did not land.&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Superseded (operator decision, see &lt;code dir=&quot;auto&quot;&gt;3.2.x.md&lt;/code&gt;):&lt;/strong&gt; the #1878 coord/primary write-side strangler —
both placement-routing and commit/protected-branch durability — moved entirely into 3.2.x/G2. It is
no longer carried into this cycle; do not re-open it here without a fresh operator call.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;non-goals&quot;&gt;Non-goals&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Re-opening the 3.2.x core-domain SSOTs (they are the &lt;em&gt;foundation&lt;/em&gt; 3.3.x builds the experience over).&lt;/li&gt;
&lt;li&gt;New product domains outside the SDD/runtime/dashboard/SaaS surface.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;success-criteria-placeholder--refine-when-the-cycle-activates&quot;&gt;Success criteria (placeholder — refine when the cycle activates)&lt;/h2&gt;
&lt;ul class=&quot;contains-task-list&quot;&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; Dashboard UX pass shipped; identity/status legible and trustworthy (no re-derivation behind it).&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; The core user flows have no dead-ends; “what next?” is always answerable in-product.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; SaaS tie-in is a coherent, documented surface.&lt;/li&gt;
&lt;li class=&quot;task-list-item&quot;&gt;&lt;input type=&quot;checkbox&quot; disabled&gt; ≥1 emergent domain strangled onto its SSOT.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;links&quot;&gt;Links&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Milestone: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/milestone/5&quot;&gt;https://github.com/Priivacy-ai/spec-kitty/milestone/5&lt;/a&gt; · Convention:
&lt;a href=&quot;/changelog/release-goals/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;README.md&lt;/code&gt;&lt;/a&gt; · Prior cycle: &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;/li&gt;
&lt;li&gt;(Detailed scope is declared when 3.2.x nears close and 3.3.x activates.)&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
