Terms naming the product lines of Spec Kitty Inc. They are distinct from
Spec Kitty, the toolkit and CLI this repository ships. The October
2026 direction frames the open-core line as a producer side (Build Kitty and
Brain Kitty) and Team Kitty as the consumer side.
Build Kitty
Definition
The open-core producer line for governed mission delivery: the free CLI and its Mission Status Read API, the stable entry point to ledger and event data that consumers read across a public contract boundary.
Context
Product lines
Status
canonical
Applicable to
4.x
Do NOT use when
Naming the CLI package, an executable or a command (those are spec-kitty and its subcommands), or using it as a code identifier; it is a product-line name, not a runtime surface. For the hosted consumer side use Team Kitty.
The open-core governance and doctrine line: the charter, a producer-side open-core unit. The Python charter stays in core until it is retired; its offering reads cut over to the spec-kitty-charter service through charter.offering.api (the repository extraction of ADR 2026-10-12-2 is superseded, 2026-10-19).
Context
Product lines
Status
canonical
Applicable to
4.x
Do NOT use when
Naming the charter files, the charter command group or a Python package; use the charter terms in Governance. Do not use it as a code identifier.
The consumer line, framed as "Multiplayer Mode": the UI and multiplayer surfaces (mission-ui, the pack composer) that consume the open-core Mission Status Read API across its public contract, never reaching into CLI internals. The hosted collaboration product behind it is no longer actively supported; its model is in Team Kitty and Zeitgeist.
Context
Product lines
Status
canonical
Applicable to
4.x
Do NOT use when
Describing the open-core producer surfaces (Build Kitty, Brain Kitty), or the old "sync" transport; do not use it as a code identifier.