<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/context/team-kitty/">
  <id>https://docs.spec-kitty.ai/context/team-kitty/</id>
  <title>Context: Team Kitty and Zeitgeist</title>
  <updated>2026-11-13T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/context/team-kitty/"/>
  <summary>Glossary context for Team Kitty and Zeitgeist: the hosted surfaces were removed from open-core in #6164, what that leaves, and why &apos;sync&apos; is a dead word.</summary>
  <content type="html">&lt;span id=&quot;context-team-kitty-and-zeitgeist&quot;&gt;&lt;/span&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Status (2026-10-14):&lt;/strong&gt; the hosted, sync and drain surfaces and their clients
were &lt;strong&gt;removed from open-core in #6164&lt;/strong&gt;. The removed code is preserved in
&lt;code dir=&quot;auto&quot;&gt;spec-kitty/event-router&lt;/code&gt; (PR #45). This page is now a glossary and a map of what
is gone, so a reader who meets the old vocabulary can translate it. Do not build
toward hosted surfaces unless the operator asks.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;what-was-removed&quot;&gt;What was removed&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Team Kitty&lt;/strong&gt; is the hosted product. &lt;strong&gt;Zeitgeist&lt;/strong&gt; is the per-team presence-and-moments
relay it runs. Until #6164 the CLI shipped the client side of that: it authenticated,
minted a capability, and published each status &lt;strong&gt;moment&lt;/strong&gt; to the team’s relay when an
opt-in called &lt;strong&gt;drain&lt;/strong&gt; was on. All of that client code left this repository:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the &lt;code dir=&quot;auto&quot;&gt;auth&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;issue-search&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;live-work&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;moments&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;routes&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;zeitgeist&lt;/code&gt; CLI entries;&lt;/li&gt;
&lt;li&gt;the hosted client packages: the Zeitgeist client, the SaaS client and the auth package;&lt;/li&gt;
&lt;li&gt;the drain posture module and the status bridge that published moments to the Zeitgeist relay.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Nothing hosted ships configured or gates a release. The SaaS and relay repositories are
separate and are not covered here.&lt;/p&gt;
&lt;h2 id=&quot;what-stays&quot;&gt;What stays&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The produce seam.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/status/adapters.py&lt;/code&gt; is the publish/subscribe
surface for status events. Open-core ships no default handler, so every &lt;code dir=&quot;auto&quot;&gt;fire_*&lt;/code&gt; call
is a no-op until a transport owner registers one. Producing an event never depends on a
drain. &lt;code dir=&quot;auto&quot;&gt;status/emit.py&lt;/code&gt; still writes the canonical event log first.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The Mission Status Read API&lt;/strong&gt; (producer) and the consumer side built on it
(“Multiplayer Mode”: mission-ui, the pack composer). See
&lt;a href=&quot;/adr/4.x/2026-10-01-2-mission-status-read-api-and-dashboard-extraction/&quot;&gt;ADR 2026-10-01-2&lt;/a&gt;
and the Amendment in
&lt;a href=&quot;/adr/4.x/2026-10-06-1-team-kitty-surfaces-are-hidden-unless-drain-is-on/&quot;&gt;ADR 2026-10-06-1&lt;/a&gt;
(its drain and hiding mechanics are now historical).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One-way cleanup migrations.&lt;/strong&gt; For example &lt;code dir=&quot;auto&quot;&gt;m_4_0_0_retired_hosted_target&lt;/code&gt; deletes a
stale &lt;code dir=&quot;auto&quot;&gt;config.toml [sync].server_url&lt;/code&gt; that names the retired &lt;code dir=&quot;auto&quot;&gt;app.spec-kitty.ai&lt;/code&gt;. It is
self-contained and touches nothing else.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;sync-is-dead&quot;&gt;“Sync” is dead&lt;/h2&gt;
&lt;p&gt;The transport called “sync” (a local daemon, an offline queue, a per-project consent
store, the &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; command group, &lt;code dir=&quot;auto&quot;&gt;api/v1/sync/*&lt;/code&gt;) was deleted in August 2026, and its
Python package with it. &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_retired_subsystems.py&lt;/code&gt; refuses its
return. The word survives only as residue in identifiers, stale docs and
comments. When you read “sync” here, translate it: it is leftover naming, never design
against or “re-enable” it. The former &lt;code dir=&quot;auto&quot;&gt;charter sync&lt;/code&gt; subcommand was unrelated to the
transport; it had become a no-op and was removed in #5828. The
&lt;code dir=&quot;auto&quot;&gt;charter.activation.sync&lt;/code&gt; module, which keeps the charter bundle fresh, is also
unrelated and stays.&lt;/p&gt;
&lt;h2 id=&quot;canonical-vocabulary&quot;&gt;Canonical vocabulary&lt;/h2&gt;
&lt;p&gt;For where Team Kitty sits among the Spec Kitty Inc. product lines (Build Kitty, Brain Kitty), see &lt;a href=&quot;/context/product-lines/&quot;&gt;Product Lines&lt;/a&gt;.&lt;/p&gt;






























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Term&lt;/th&gt;&lt;th&gt;Meaning&lt;/th&gt;&lt;th&gt;Do not say&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Team Kitty&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The hosted product (separate SaaS repository). Not part of open-core.&lt;/td&gt;&lt;td&gt;“the SaaS sync”, “Spec Kitty Cloud”&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Zeitgeist&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The presence-and-gossip relay Team Kitty runs, one container per team.&lt;/td&gt;&lt;td&gt;“the event server”, “sync server”&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Moment&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;One content-agnostic, bounded status event published to a relay.&lt;/td&gt;&lt;td&gt;“sync event”&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Drain&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The former client-side opt-in for automatic outbound hosted interaction. Removed with the hosted surfaces.&lt;/td&gt;&lt;td&gt;“sync”, “fan-out enabled”&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;stale-surfaces-you-will-meet&quot;&gt;Stale surfaces you will meet&lt;/h2&gt;
&lt;p&gt;Kept for history: the 2.x/3.x sync ADRs. The hosted and sync pages
(&lt;code dir=&quot;auto&quot;&gt;project-sync-consent&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;team-kitty-saas&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;logged-out-teamspace&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;sync-daemon-orphan-cleanup&lt;/code&gt; and
others) were archived under &lt;code dir=&quot;auto&quot;&gt;docs/archive/&lt;/code&gt; (#6932); &lt;code dir=&quot;auto&quot;&gt;docs/operations/sync-drain.md&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;docs/operations/ci-machine-auth.md&lt;/code&gt; were deleted (#6219). The removed code lives in the
&lt;code dir=&quot;auto&quot;&gt;spec-kitty/event-router&lt;/code&gt; repository. ADR &lt;a href=&quot;/adr/3.x/2026-09-26-3-hosted-interaction-opt-in/&quot;&gt;hosted interaction is opt-in&lt;/a&gt;
and &lt;a href=&quot;/adr/3.x/2026-09-06-1-convergence-retirement-and-client-repo-inversion/&quot;&gt;convergence retirement and client-repo inversion&lt;/a&gt;
describe the earlier design. See also &lt;a href=&quot;/context/system-events/&quot;&gt;system events&lt;/a&gt; for the canonical
event envelope.&lt;/p&gt;</content>
</entry>
