---
type: "Changelog"
title: "3.3.x — Experience & surface: UX, dashboard, flows, SaaS + emergent-domain strangling"
description: "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."
status: "deprecated"
generated:
  by: "process:dockitty-export"
  at: "2026-09-30T00:00:00Z"
---

# 3.3.x — Experience & surface: UX, dashboard, flows, SaaS + emergent-domain strangling

> **Superseded.** 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 [4.0.0 roadmap](/plans/4-0-0-milestone-roadmap.md). Kept as a record of the cycle's intent.

**Milestone:** [`3.3.x`](https://github.com/Priivacy-ai/spec-kitty/milestone/5) (retired) ·
**Status:** retired 2026-08-23 (never shipped; historical record) · **Declared:** 2026-06-16 · **Advances:** #1619 (continued
domain extraction), the dashboard/SaaS surfaces.

## Theme

With the **core domains** strangled onto their SSOTs in 3.2.x, 3.3.x turns to the **experience and
outward surface** — how operators and users actually interact with Spec Kitty — while continuing to
**extract and strangle the *next* emergent domains** as they surface from the 3.2.x work. Same
discipline: no new shadow paths; route or extract, never duplicate.

## Goals

### G1 — UX & dashboard look-and-feel
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.)

### G2 — User flows
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.

### G3 — SaaS tie-in
Strengthen the hosted/SaaS integration — sync, tracker connectors, dossiers, auth — as a coherent
surface rather than a set of bolt-ons.

### G4 — Strangle the next emergent domains
Continue the #1619 decomposition into the domains that emerge once the core set is done (whatever the
3.2.x slices surface). **#1878 is no longer this cycle's example** — see the superseded note below.
Extract → route → enforce, as in 3.2.x.

## Carried in from 3.2.x

- Any core-domain slice that 3.2.x scoped but did not land.

> **Superseded (operator decision, see `3.2.x.md`):** 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.

## Non-goals

- Re-opening the 3.2.x core-domain SSOTs (they are the *foundation* 3.3.x builds the experience over).
- New product domains outside the SDD/runtime/dashboard/SaaS surface.

## Success criteria (placeholder — refine when the cycle activates)

- [ ] Dashboard UX pass shipped; identity/status legible and trustworthy (no re-derivation behind it).
- [ ] The core user flows have no dead-ends; "what next?" is always answerable in-product.
- [ ] SaaS tie-in is a coherent, documented surface.
- [ ] ≥1 emergent domain strangled onto its SSOT.

## Links

- Milestone: https://github.com/Priivacy-ai/spec-kitty/milestone/5 · Convention:
  [`README.md`](/changelog/release-goals.md) · Prior cycle: [`3.2.x.md`](/changelog/3.2.x.md)
- (Detailed scope is declared when 3.2.x nears close and 3.3.x activates.)

## Related

- [3.2.x — Doctrine-runtime depth · core-domain strangling · DevEx](/changelog/3.2.x.md)
- [Changelog](/changelog/index.md)
- [Release Goals — Declarations of Intent](/changelog/release-goals.md)

## Audience

- [Stakeholder Persona: Maintainer](/context/audience/internal/maintainer.md) - Written for the Maintainer reader.
