<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/2.x/2026-01-27-11-dual-repository-pattern/">
  <id>https://docs.spec-kitty.ai/adr/2.x/2026-01-27-11-dual-repository-pattern/</id>
  <title>Dual-Repository Pattern for Private spec-kitty-events Dependency</title>
  <updated>2026-01-27T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/2.x/2026-01-27-11-dual-repository-pattern/"/>
  <summary>Keeps the shared events library in its own private repository, consumed as a commit-pinned git dependency, so CI stays autonomous and the CLI repo stays public.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;Spec Kitty is transitioning from a local-only CLI tool to a distributed SaaS platform on the &lt;strong&gt;2.x branch&lt;/strong&gt; (see ADR-12: Two-Branch Strategy). The event sourcing library (&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;) built in Feature 003 must be shared between:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;spec-kitty CLI (2.x branch)&lt;/strong&gt; (public repository, private dependency during dev)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;spec-kitty Django&lt;/strong&gt; (future SaaS backend, private)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The library provides Lamport clocks, CRDT merge rules, and conflict detection - solving the Last-Write-Wins data loss problem discovered in Feature 002.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Branch Context:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;1.x/main branch&lt;/strong&gt;: Local-only CLI, NO spec-kitty-events dependency (YAML activity logs)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2.x branch&lt;/strong&gt;: SaaS transformation, HAS spec-kitty-events dependency (event sourcing)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Why separate&lt;/strong&gt;: Architectures are incompatible (cannot coexist in single branch)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Constraints:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;spec-kitty is PUBLIC (GitHub + PyPI)&lt;/li&gt;
&lt;li&gt;spec-kitty-events is PRIVATE (MVP phase, will open source later)&lt;/li&gt;
&lt;li&gt;Solo maintainer (no team coordination overhead)&lt;/li&gt;
&lt;li&gt;CI/CD must work autonomously (no laptop dependency)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2.x branch only&lt;/strong&gt; - This dependency applies ONLY to 2.x (SaaS transformation); 1.x/main remains dependency-free (local-only CLI)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Question:&lt;/strong&gt; How do we structure repositories and manage the private dependency for the 2.x branch while keeping 1.x simple?&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CI/CD autonomy&lt;/strong&gt; - Builds must work without developer’s laptop&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deterministic builds&lt;/strong&gt; - Same code every time (no “works on my machine”)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Private during MVP&lt;/strong&gt; - Events library hidden until stable&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;PyPI compatibility&lt;/strong&gt; - Public users can install spec-kitty-cli&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Future open source path&lt;/strong&gt; - Clean transition when events goes public&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Solo developer simplicity&lt;/strong&gt; - No complex infrastructure overhead&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Option 1:&lt;/strong&gt; Dual-repository with Git dependency + commit pinning&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option 2:&lt;/strong&gt; Monorepo (single repository for both)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option 3:&lt;/strong&gt; Git submodule&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option 4:&lt;/strong&gt; Private PyPI index (Gemfury, AWS CodeArtifact)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option 5:&lt;/strong&gt; Vendoring from day 1&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Chosen option:&lt;/strong&gt; “Dual-repository with Git dependency + commit pinning”, because it:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Enables CI/CD autonomy (no laptop needed)&lt;/li&gt;
&lt;li&gt;Provides deterministic builds (commit hash = exact behavior)&lt;/li&gt;
&lt;li&gt;Keeps events private while CLI is public&lt;/li&gt;
&lt;li&gt;Requires no infrastructure (no private PyPI)&lt;/li&gt;
&lt;li&gt;Has clean path to open source (just remove vendoring step)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;consequences&quot;&gt;Consequences&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;IMPORTANT&lt;/strong&gt;: This pattern applies to the &lt;strong&gt;2.x branch only&lt;/strong&gt;. The 1.x/main branch remains dependency-free (local-only tool). See ADR-12 for branch strategy.&lt;/p&gt;
&lt;h4 id=&quot;positive&quot;&gt;Positive&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CI/CD autonomy&lt;/strong&gt; - Deploy key + Git dependency = fully automated builds (2.x branch)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deterministic&lt;/strong&gt; - Commit hash pinning guarantees same behavior&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Explicit integration points&lt;/strong&gt; - You control when events updates land&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Private during MVP&lt;/strong&gt; - Events stays hidden, CLI remains public on PyPI&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clean transition&lt;/strong&gt; - Remove vendoring when events goes public&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shared library&lt;/strong&gt; - CLI (2.x) and Django use same logic (no code duplication)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;1.x unaffected&lt;/strong&gt; - Main branch stays simple (no private dependencies)&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Manual commit updates&lt;/strong&gt; - Each events change requires updating pyproject.toml&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SSH key management&lt;/strong&gt; - Deploy key needs rotation every 12 months&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Vendoring complexity&lt;/strong&gt; - PyPI release requires vendor script&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two-repo coordination&lt;/strong&gt; - Feature branches must be manually synchronized&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;No local pip -e&lt;/strong&gt; - Forces rigorous workflow but slows rapid iteration&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Git dependency size&lt;/strong&gt; - Clones full repo history (but small &amp;#x3C;5MB)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;confirmation&quot;&gt;Confirmation&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Validation signals:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;CI builds pass without manual intervention (autonomy achieved)&lt;/li&gt;
&lt;li&gt;No “works on my machine” bugs (determinism achieved)&lt;/li&gt;
&lt;li&gt;PyPI users can install without GitHub access (vendoring works)&lt;/li&gt;
&lt;li&gt;Clean transition when events goes public (no major refactor)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Confidence level:&lt;/strong&gt; High - Similar to how many open source projects handle private/vendored dependencies during development.&lt;/p&gt;
&lt;h2 id=&quot;pros-and-cons-of-the-options&quot;&gt;Pros and Cons of the Options&lt;/h2&gt;
&lt;h3 id=&quot;option-1-dual-repository--git-dependency&quot;&gt;Option 1: Dual-Repository + Git Dependency&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;CHOSEN OPTION&lt;/strong&gt; - Implemented on 2.x branch only.&lt;/p&gt;
&lt;p&gt;Git dependency in pyproject.toml with commit hash pinning:&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;toml&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# In pyproject.toml (2.x branch only)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#C5E478;--1:#3B61B0&quot;&gt;spec-kitty-events&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; = { &lt;/span&gt;&lt;span style=&quot;--0:#C5E478;--1:#3B61B0&quot;&gt;git&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; = &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;ssh://git@github.com/Priivacy-ai/spec-kitty-events.git&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#C5E478;--1:#3B61B0&quot;&gt;rev&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; = &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;abc1234...&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; }&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;Branch-Specific Implementation:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;2.x branch&lt;/strong&gt;: Has Git dependency (event sourcing architecture)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;1.x/main branch&lt;/strong&gt;: NO dependency (local-only, YAML logs)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Why separate&lt;/strong&gt;: Per ADR-12, architectures are incompatible (cannot coexist)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;CI/CD works autonomously (no local paths) - 2.x branch&lt;/li&gt;
&lt;li&gt;Deterministic builds (exact commit hash)&lt;/li&gt;
&lt;li&gt;No infrastructure costs ($0/month)&lt;/li&gt;
&lt;li&gt;Forces explicit integration points (good discipline)&lt;/li&gt;
&lt;li&gt;Clean path to open source&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;1.x simplicity preserved&lt;/strong&gt; - Main branch stays dependency-free&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Manual commit hash updates (2.x branch maintenance)&lt;/li&gt;
&lt;li&gt;SSH deploy key setup required (one-time per repo)&lt;/li&gt;
&lt;li&gt;Vendoring step for PyPI releases (deferred to 2.x release feature)&lt;/li&gt;
&lt;li&gt;Two-repo branch coordination (2.x feature branches only)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;option-2-monorepo&quot;&gt;Option 2: Monorepo&lt;/h3&gt;
&lt;p&gt;Single repository with both CLI and events as packages.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Single clone, easier local dev&lt;/li&gt;
&lt;li&gt;Atomic commits across components&lt;/li&gt;
&lt;li&gt;No Git dependency complications&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;❌ &lt;strong&gt;Cannot make events private while keeping CLI public&lt;/strong&gt; (deal-breaker)&lt;/li&gt;
&lt;li&gt;All contributors see events code (violates privacy requirement)&lt;/li&gt;
&lt;li&gt;Release complexity (two packages from one repo)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;option-3-git-submodule&quot;&gt;Option 3: Git Submodule&lt;/h3&gt;
&lt;p&gt;Events as submodule in &lt;code dir=&quot;auto&quot;&gt;external/spec-kitty-events/&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Explicit version pinning (commit in .gitmodules)&lt;/li&gt;
&lt;li&gt;No SSH setup for CI (submodule handles it)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;❌ Complex developer onboarding (&lt;code dir=&quot;auto&quot;&gt;git submodule update --init&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Easy to forget &lt;code dir=&quot;auto&quot;&gt;git submodule update&lt;/code&gt; (silent breakage)&lt;/li&gt;
&lt;li&gt;Path dependency breaks CI without submodule&lt;/li&gt;
&lt;li&gt;Still requires vendoring for PyPI&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;option-4-private-pypi-index&quot;&gt;Option 4: Private PyPI Index&lt;/h3&gt;
&lt;p&gt;Host spec-kitty-events on private PyPI (Gemfury, AWS CodeArtifact).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Standard pip/poetry workflow (no Git deps)&lt;/li&gt;
&lt;li&gt;Version ranges and semantic versioning&lt;/li&gt;
&lt;li&gt;Good for larger teams&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;❌ Infrastructure overhead (setup + maintenance)&lt;/li&gt;
&lt;li&gt;❌ Cost ($50-200/month hosted, $0-500/month AWS)&lt;/li&gt;
&lt;li&gt;❌ Auth setup for CI and developers&lt;/li&gt;
&lt;li&gt;❌ Overkill for solo developer&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;option-5-vendoring-from-day-1&quot;&gt;Option 5: Vendoring from Day 1&lt;/h3&gt;
&lt;p&gt;Copy events code into &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/_vendored/events/&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Zero external dependencies&lt;/li&gt;
&lt;li&gt;Works on PyPI without complications&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;❌ Loses version control for events&lt;/li&gt;
&lt;li&gt;❌ Hard to sync changes between CLI and Django&lt;/li&gt;
&lt;li&gt;❌ No shared test suite (divergence risk)&lt;/li&gt;
&lt;li&gt;❌ Violates DRY (code duplication)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;more-information&quot;&gt;More Information&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Implementation details:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Branch-Specific Application (CRITICAL):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;2.x branch&lt;/strong&gt;: Git dependency with spec-kitty-events (implemented in Feature 025)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Location: &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; on 2.x branch&lt;/li&gt;
&lt;li&gt;Created: 2026-01-27 (branch created from main at v0.13.7)&lt;/li&gt;
&lt;li&gt;Installs: &lt;code dir=&quot;auto&quot;&gt;poetry install&lt;/code&gt; on 2.x requires SSH access to spec-kitty-events&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;1.x/main branch&lt;/strong&gt;: NO dependency on spec-kitty-events (local-only, YAML logs)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Location: &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; on main does NOT include spec-kitty-events&lt;/li&gt;
&lt;li&gt;Installs: &lt;code dir=&quot;auto&quot;&gt;poetry install&lt;/code&gt; on main works without SSH key&lt;/li&gt;
&lt;li&gt;Future: main becomes 1.x maintenance branch (no event sourcing)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Why separate&lt;/strong&gt;: Per ADR-12, branches have incompatible architectures (event sourcing vs YAML logs)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Git Dependency Configuration (2.x branch only):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;File: &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; (2.x branch)&lt;/li&gt;
&lt;li&gt;Format: &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events = { git = &quot;ssh://git@github.com/Priivacy-ai/spec-kitty-events.git&quot;, rev = &quot;&amp;#x3C;commit-hash&gt;&quot; }&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Commit pinning: MUST use full 40-char hash (NOT branch name, NOT “main”)&lt;/li&gt;
&lt;li&gt;Deploy key: GitHub Settings &gt; Deploy Keys (read-only to spec-kitty-events)&lt;/li&gt;
&lt;li&gt;Secret name: &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_EVENTS_DEPLOY_KEY&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;CI workflow: &lt;code dir=&quot;auto&quot;&gt;.github/workflows/ci.yml&lt;/code&gt; on 2.x branch (SSH setup before pip install)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;PyPI Release Strategy (2.x branch, future):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Vendoring script: &lt;code dir=&quot;auto&quot;&gt;scripts/vendor_and_release.py&lt;/code&gt; (deferred to “2.x Release Preparation” feature, NOT Feature 025)&lt;/li&gt;
&lt;li&gt;Why needed: PyPI users don’t have GitHub access to private repo&lt;/li&gt;
&lt;li&gt;Process: Vendor events library into CLI → build wheel → publish to PyPI&lt;/li&gt;
&lt;li&gt;When: Not until 2.x approaches beta/stable release&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Documentation:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Charter: &lt;code dir=&quot;auto&quot;&gt;.kittify/memory/charter.md&lt;/code&gt; (Architecture: Private Dependency Pattern, lines 46-132)&lt;/li&gt;
&lt;li&gt;ADR-12: &lt;code dir=&quot;auto&quot;&gt;architecture/2.x/adr/2026-01-27-12-two-branch-strategy-for-saas-transformation.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Setup guide: &lt;code dir=&quot;auto&quot;&gt;docs/development/ssh-deploy-keys.md&lt;/code&gt; (created in Feature 025 WP01 T002)&lt;/li&gt;
&lt;li&gt;Dependency updates: &lt;code dir=&quot;auto&quot;&gt;CONTRIBUTING.md&lt;/code&gt; (documented in Feature 025 WP08 T044)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Related decisions:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;ADR-12&lt;/strong&gt;: Two-Branch Strategy for SaaS Transformation (defines why 2.x branch exists and why it’s separate from main)&lt;/li&gt;
&lt;li&gt;Feature 001: SaaS Transformation Research (validated 4-phase roadmap)&lt;/li&gt;
&lt;li&gt;Feature 002: Event Log Storage Research (identified LWW flaw requiring event sourcing)&lt;/li&gt;
&lt;li&gt;Feature 003: Event Log Library (built spec-kitty-events v0.1.0-alpha in separate repo)&lt;/li&gt;
&lt;li&gt;Feature 025: CLI Event Log Integration (implements this ADR on 2.x branch)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Branch workflow:&lt;/strong&gt;&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# For 2.x development (event sourcing features):&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;git&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;checkout&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;2.x&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;poetry&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;install&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;  &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# Requires SSH access to spec-kitty-events&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;
&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# For 1.x maintenance (stable fixes):&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;git&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;checkout&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;main&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;poetry&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;install&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;  &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# No private dependencies, works immediately&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;Future considerations:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Open source events library when stable (6+ months, no major bugs)&lt;/li&gt;
&lt;li&gt;Consider private PyPI if team grows beyond solo developer&lt;/li&gt;
&lt;li&gt;Alternatively, merge to monorepo if privacy requirement relaxes&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Code references:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;spec-kitty-events: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty-events&quot;&gt;https://github.com/Priivacy-ai/spec-kitty-events&lt;/a&gt; (private)&lt;/li&gt;
&lt;li&gt;pyproject.toml: Git dependency declaration&lt;/li&gt;
&lt;li&gt;.github/workflows/: CI configuration with deploy key setup&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
