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

Milestone: 3.3.x (open) · Status: declared (not yet active) · 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 (e.g. the #1878 coord/primary WRITE/entry-side strangler — commit/protected-branch durability, characterization-first — and whatever the 3.2.x slices surface). Extract → route → enforce, as in 3.2.x.

Carried in from 3.2.x

#1878 write-side strangler (the marquee deferral — semantics-sensitive; the read-side was addressed in 3.2.x, the write/entry side is here).
Any core-domain slice that 3.2.x scoped but did not land.

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 (incl. the #1878 write-side) strangled onto its SSOT.