<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-09-06-1-convergence-retirement-and-client-repo-inversion/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-09-06-1-convergence-retirement-and-client-repo-inversion/</id>
  <title>ADR: Convergence Retirement and Client-Repo Inversion</title>
  <updated>2026-09-06T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-09-06-1-convergence-retirement-and-client-repo-inversion/"/>
  <summary>The Convergence (#3881) retired the CLI→SaaS sync/daemon/delivery stack; this repo now inverts ownership as a client of upstream spec-kitty/zeitgeist and spec-kitty/saas.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;The Convergence merge (&lt;strong&gt;#3881&lt;/strong&gt;, &lt;code dir=&quot;auto&quot;&gt;converge/exp-main-20260905&lt;/code&gt;, landed 2026-09-05; Convergence Event
announcement &lt;strong&gt;#3824&lt;/strong&gt;, legacy-sync teardown holding pen &lt;strong&gt;#3801&lt;/strong&gt;) folded ~2000 commits from the
EXPERIMENTAL line onto public &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;. It did two things this ADR records as a governed decision.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. It retired the in-place CLI→SaaS sync subsystem.&lt;/strong&gt; Removed wholesale (0 git-tracked files remain;
an architectural gate — &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_retired_subsystems.py&lt;/code&gt; — plus a &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;
TID251 ban block keep them from silently returning):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the local sync transport: the &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync&lt;/code&gt; command family (22 subcommands) + daemon +
emitter / transport-attempts / batch / offline-queue / body-outbox;&lt;/li&gt;
&lt;li&gt;the delivery / event-journal &lt;strong&gt;emit&lt;/strong&gt; stack and the &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/saas/&lt;/code&gt; package;&lt;/li&gt;
&lt;li&gt;the &lt;code dir=&quot;auto&quot;&gt;websockets&lt;/code&gt; runtime dependency.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Mission status is now &lt;strong&gt;ephemeral by design&lt;/strong&gt;; team artifacts render &lt;strong&gt;server-side&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2. It inverted feature-ownership.&lt;/strong&gt; This core repo (&lt;code dir=&quot;auto&quot;&gt;Priivacy-ai/spec-kitty&lt;/code&gt;) is now merely a
&lt;strong&gt;CLIENT&lt;/strong&gt;. The &lt;strong&gt;authoritative repositories&lt;/strong&gt; are &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty/zeitgeist&lt;/code&gt;&lt;/strong&gt; (the ephemeral-status
service) and &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty/saas&lt;/code&gt;&lt;/strong&gt; (hosted team surface). In this repo,
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/zeitgeist_client/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/saas_client/&lt;/code&gt; are &lt;strong&gt;consumer code&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;saas_client&lt;/code&gt; is &lt;em&gt;generated&lt;/em&gt; — PR #3589 / saas#300). The rule is: &lt;strong&gt;pull + use + integrate the client
HERE; author + publish the API/client UPSTREAM.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Four Accepted ADRs still describe the pre-Convergence world and now govern deleted subsystems, which
actively misleads any reader who trusts the decision record.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mark the following four ADRs &lt;code dir=&quot;auto&quot;&gt;Superseded&lt;/code&gt;&lt;/strong&gt;, each pointing at this ADR:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-06-30-1-sync-daemon-identity-and-cleanup-classification.md&lt;/code&gt; — the sync daemon it
governs (identity/kill authority, &lt;code dir=&quot;auto&quot;&gt;owner.json&lt;/code&gt;, orphan reaping) is retired.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-04-11-1-saas-rollout-and-readiness.md&lt;/code&gt; — the &lt;code dir=&quot;auto&quot;&gt;specify_cli.saas&lt;/code&gt; rollout/readiness
package it governs is deleted; residual readiness re-homed to &lt;code dir=&quot;auto&quot;&gt;tracker/saas_readiness.py&lt;/code&gt;, the
SaaS-sync flag to &lt;code dir=&quot;auto&quot;&gt;core/saas_sync_config.py&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-08-09-1-project-sync-store-boundary.md&lt;/code&gt; — the &lt;code dir=&quot;auto&quot;&gt;ProjectSyncStore&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;sync/project_store.py&lt;/code&gt; boundary it governs is deleted with the sync transport.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;docs/adr/2.x/2026-02-27-1-cli-tracker-surface-gated-by-saas-sync-flag.md&lt;/code&gt; — the in-place sync
transport is gone; the &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC&lt;/code&gt; gate &lt;strong&gt;survives&lt;/strong&gt; only as an auth/hosted
visibility gate for the surviving &lt;code dir=&quot;auto&quot;&gt;tracker&lt;/code&gt; group, not as a sync-transport gate. Superseded to a
clarification, not a deletion of that env var.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Record the client-repo inversion&lt;/strong&gt; as the standing architectural fact: core = client; the
redesign/authoring of the SaaS/zeitgeist API lives &lt;strong&gt;upstream&lt;/strong&gt;; &lt;code dir=&quot;auto&quot;&gt;zeitgeist_client&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;saas_client&lt;/code&gt; are
consumer code integrated here.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Leave &lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-04-25-1-shared-package-boundary.md&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;Accepted&lt;/code&gt;.&lt;/strong&gt; This inversion is not a
reversal of it — it is the &lt;strong&gt;precedent it extends&lt;/strong&gt;. That ADR established that &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-tracker&lt;/code&gt; are external dependencies consumed via their public surface; the client-repo
inversion applies the same model to &lt;code dir=&quot;auto&quot;&gt;zeitgeist&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;saas&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The decision record stops asserting deleted designs; readers are routed to the retirement + inversion
from each superseded ADR.&lt;/li&gt;
&lt;li&gt;No zeitgeist/SaaS &lt;strong&gt;redesign or authoring&lt;/strong&gt; epic belongs in this repo — that work lives upstream in
&lt;code dir=&quot;auto&quot;&gt;spec-kitty/zeitgeist&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;spec-kitty/saas&lt;/code&gt;. The core-repo roadmap item is narrower: consume /
integrate / upgrade the published clients. Design-inputs from the retired surface (e.g. #3801’s
holding-pen inputs, #1800 / #3549 envelope &amp;#x26; durability lessons) feed the &lt;strong&gt;upstream&lt;/strong&gt; redesign.&lt;/li&gt;
&lt;li&gt;The surviving surfaces are unaffected and sanctioned by design: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/saas_client/&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tracker/saas_*&lt;/code&gt; (readiness/client/service), charter sync, and the &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SYNC_*&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC&lt;/code&gt; env vars.&lt;/li&gt;
&lt;li&gt;An ADR-hygiene gate (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_adr_hygiene_convergence_retirement.py&lt;/code&gt;) enforces this
ADR’s shape: the four are &lt;code dir=&quot;auto&quot;&gt;Superseded&lt;/code&gt; and link here; this ADR is &lt;code dir=&quot;auto&quot;&gt;Accepted&lt;/code&gt; and supersedes them;
&lt;code dir=&quot;auto&quot;&gt;2026-04-25-1&lt;/code&gt; remains &lt;code dir=&quot;auto&quot;&gt;Accepted&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
