---
type: "Context"
title: "Context: Team Kitty and Zeitgeist"
description: "Glossary context for Team Kitty and Zeitgeist: the hosted surfaces were removed from open-core in #6164, what that leaves, and why 'sync' is a dead word."
status: "stable"
generated:
  by: "process:dockitty-export"
  at: "2026-11-13T00:00:00Z"
---

# Context: Team Kitty and Zeitgeist

> **Status (2026-10-14):** the hosted, sync and drain surfaces and their clients
> were **removed from open-core in #6164**. The removed code is preserved in
> `spec-kitty/event-router` (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.

## What was removed

**Team Kitty** is the hosted product. **Zeitgeist** 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 **moment** to the team's relay when an
opt-in called **drain** was on. All of that client code left this repository:

- the `auth`, `issue-search`, `live-work`, `moments`, `routes` and `zeitgeist` CLI entries;
- the hosted client packages: the Zeitgeist client, the SaaS client and the auth package;
- the drain posture module and the status bridge that published moments to the Zeitgeist relay.

Nothing hosted ships configured or gates a release. The SaaS and relay repositories are
separate and are not covered here.

## What stays

- **The produce seam.** `src/specify_cli/status/adapters.py` is the publish/subscribe
  surface for status events. Open-core ships no default handler, so every `fire_*` call
  is a no-op until a transport owner registers one. Producing an event never depends on a
  drain. `status/emit.py` still writes the canonical event log first.
- **The Mission Status Read API** (producer) and the consumer side built on it
  ("Multiplayer Mode": mission-ui, the pack composer). See
  [ADR 2026-10-01-2](/adr/4.x/2026-10-01-2-mission-status-read-api-and-dashboard-extraction.md)
  and the Amendment in
  [ADR 2026-10-06-1](/adr/4.x/2026-10-06-1-team-kitty-surfaces-are-hidden-unless-drain-is-on.md)
  (its drain and hiding mechanics are now historical).
- **One-way cleanup migrations.** For example `m_4_0_0_retired_hosted_target` deletes a
  stale `config.toml [sync].server_url` that names the retired `app.spec-kitty.ai`. It is
  self-contained and touches nothing else.

## "Sync" is dead

The transport called "sync" (a local daemon, an offline queue, a per-project consent
store, the `sync` command group, `api/v1/sync/*`) was deleted in August 2026, and its
Python package with it. `tests/architectural/test_no_retired_subsystems.py` 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 `charter sync` subcommand was unrelated to the
transport; it had become a no-op and was removed in #5828. The
`charter.activation.sync` module, which keeps the charter bundle fresh, is also
unrelated and stays.

## Canonical vocabulary

For where Team Kitty sits among the Spec Kitty Inc. product lines (Build Kitty, Brain Kitty), see [Product Lines](/context/product-lines.md).

| Term | Meaning | Do not say |
|---|---|---|
| **Team Kitty** | The hosted product (separate SaaS repository). Not part of open-core. | "the SaaS sync", "Spec Kitty Cloud" |
| **Zeitgeist** | The presence-and-gossip relay Team Kitty runs, one container per team. | "the event server", "sync server" |
| **Moment** | One content-agnostic, bounded status event published to a relay. | "sync event" |
| **Drain** | The former client-side opt-in for automatic outbound hosted interaction. Removed with the hosted surfaces. | "sync", "fan-out enabled" |

## Stale surfaces you will meet

Kept for history: the 2.x/3.x sync ADRs. The hosted and sync pages
(`project-sync-consent`, `team-kitty-saas`, `logged-out-teamspace`, `sync-daemon-orphan-cleanup` and
others) were archived under `docs/archive/` (#6932); `docs/operations/sync-drain.md` and
`docs/operations/ci-machine-auth.md` were deleted (#6219). The removed code lives in the
`spec-kitty/event-router` repository. ADR [hosted interaction is opt-in](/adr/3.x/2026-09-26-3-hosted-interaction-opt-in.md)
and [convergence retirement and client-repo inversion](/adr/3.x/2026-09-06-1-convergence-retirement-and-client-repo-inversion.md)
describe the earlier design. See also [system events](/context/system-events.md) for the canonical
event envelope.

## Related

- [ADR: Convergence Retirement and Client-Repo Inversion](/adr/3.x/2026-09-06-1-convergence-retirement-and-client-repo-inversion.md)
- [ADR: hosted interaction is opt-in, twice, with no packaged endpoint](/adr/3.x/2026-09-26-3-hosted-interaction-opt-in.md)
- [ADR: the Team Kitty surfaces are hidden unless hosted drain is on](/adr/4.x/2026-10-06-1-team-kitty-surfaces-are-hidden-unless-drain-is-on.md)
- [Configuration Reference](/api/configuration.md)
- [Environment Variables Reference](/api/environment-variables.md)
- [Context: Orchestration](/context/orchestration.md)
- [Context: System Events](/context/system-events.md)

## Audience

- [Stakeholder Persona: AI Collaboration Agent](/context/audience/internal/ai-collaboration-agent.md) - Read this before any work that mentions Team Kitty, Zeitgeist or sync, so you translate the old vocabulary instead of building on it.
- [Stakeholder Persona: System Architect](/context/audience/internal/system-architect.md) - Use this to see which hosted surfaces left open-core in
