<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/plans/4-0-0-milestone-roadmap/">
  <id>https://docs.spec-kitty.ai/plans/4-0-0-milestone-roadmap/</id>
  <title>4.0.0 Milestone — Roadmap</title>
  <updated>2026-11-01T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/plans/4-0-0-milestone-roadmap/"/>
  <summary>Roadmap for the 4.0.0 cycle: release posture, what still gates GA, dependency spine, exit criteria and risks. Re-anchored 2026-10-12 to the October direction.</summary>
  <content type="html">&lt;span id=&quot;400-milestone--roadmap&quot;&gt;&lt;/span&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Status note (2026-11-01, #6915).&lt;/strong&gt; The Mission Status Read API’s Java service and the &lt;code dir=&quot;auto&quot;&gt;mission-status&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;mission-write&lt;/code&gt; contracts now live in &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;service/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt;; ADR &lt;a href=&quot;/adr/4.x/2026-10-29-1-the-events-domain-and-its-java-services-live-in-spec-kitty-events/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;2026-10-29-1&lt;/code&gt;&lt;/a&gt;), which releases them on the &lt;code dir=&quot;auto&quot;&gt;service-v*&lt;/code&gt; line. Core pins the read service (&lt;code dir=&quot;auto&quot;&gt;pins/read-service.source.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;service-v0.1.0-rc.1&lt;/code&gt;) for CI conformance only, and core’s &lt;code dir=&quot;auto&quot;&gt;services/&lt;/code&gt; copy is removed. Where this document says the service is in-repo or is to start in-repo, read it as history.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;em&gt;Planner synthesis, first written 2026-09-14 against the old &lt;code dir=&quot;auto&quot;&gt;4.0.0&lt;/code&gt; milestone (GitHub
milestone 8, since renamed &lt;strong&gt;4.x Work&lt;/strong&gt;). &lt;strong&gt;Re-synthesized 2026-10-06&lt;/strong&gt; against the GA gate,
the &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;4.0.0 release scope&lt;/a&gt; milestone
(read with &lt;code dir=&quot;auto&quot;&gt;gh api repos/spec-kitty/spec-kitty/milestones/11&lt;/code&gt; and its issue list), the
2026-10-01 direction update below, and the CI debrief of 2026-10-05. The durable “why” is the
declaration of intent, &lt;a href=&quot;/changelog/4.0.0/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;4.0.0.md&lt;/code&gt;&lt;/a&gt;. This roadmap is the authority for
the &lt;strong&gt;active&lt;/strong&gt; 4.0.0 cycle; the prior &lt;a href=&quot;/plans/3-2-x-milestone-roadmap/&quot;&gt;3.2.x milestone roadmap&lt;/a&gt;
points here (see its
&lt;a href=&quot;/plans/3-2-x-milestone-roadmap/#addendum-2026-09-14--4x-is-now-the-active-cycle-authority-moved&quot;&gt;Addendum 2026-09-14&lt;/a&gt;).
A summary for decision owners is in the &lt;a href=&quot;/plans/4-x-executive-overview/&quot;&gt;4.x Executive Overview&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&quot;intent-of-400&quot;&gt;Intent of 4.0.0&lt;/h2&gt;
&lt;p&gt;4.0.0 was declared on 2026-09-04 as the &lt;strong&gt;hosted-collaboration + structural-finish&lt;/strong&gt; cycle:
&lt;strong&gt;G1 hosted collaboration (Team Kitty)&lt;/strong&gt;, &lt;strong&gt;G2 next-generation product capabilities&lt;/strong&gt;, and
&lt;strong&gt;G3 the open-core structural strangler finish&lt;/strong&gt;. The 2026-10-01 direction update made GA a
&lt;strong&gt;local CLI integrity&lt;/strong&gt; release. The &lt;strong&gt;2026-10-12 direction update&lt;/strong&gt; (below) &lt;strong&gt;expands the GA
gate&lt;/strong&gt; beyond local integrity to also gate on two pieces of the open-core structural finish:
&lt;strong&gt;charter modular extraction&lt;/strong&gt; (#645) and the &lt;strong&gt;mission-status API backend&lt;/strong&gt; (the open-core
producer surface). GA now ships &lt;strong&gt;“done when done” — it is not date-gated&lt;/strong&gt; (see “Release
posture”). The four operator-stated goal themes keep their numbering:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Stability.&lt;/strong&gt; The CLI never reports success while it loses, overwrites or strands local
work. Failures are named, not swallowed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Maturity.&lt;/strong&gt; One canonical local event store, honestly reported; large modules split
into owned seams.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Extensibility.&lt;/strong&gt; A governed front door and a stable, versioned application API, so
CLI, UI, MCP and SDK consumers build against one surface. Two of its pieces — charter
modular extraction and the mission-status API backend — are now on the GA gate (Theme 3,
below).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Team Kitty enablers.&lt;/strong&gt; Re-framed 2026-10-12 as &lt;strong&gt;“Multiplayer Mode” — the consumer side&lt;/strong&gt;
of the open-core producer API. The hosted &lt;em&gt;backend&lt;/em&gt; lane stays frozen, but consumer-side
UI/multiplayer on the mission-status API and the produce/drain adapter seam are no longer
blocked (see “Direction update (2026-10-12)”).&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Same discipline as the prior cycles: &lt;strong&gt;no new shadow paths&lt;/strong&gt;. Route or extract onto an
existing authority; never build a parallel one.&lt;/p&gt;
&lt;h2 id=&quot;direction-update-2026-10-12-ga-is-done-when-done-and-the-gate-expands&quot;&gt;Direction update (2026-10-12): GA is done-when-done, and the gate expands&lt;/h2&gt;
&lt;p&gt;The operator ratified six adjustments on 2026-10-12. They &lt;strong&gt;extend&lt;/strong&gt; the 2026-10-01 update
below (which still holds where this one is silent); where the two differ, this one wins.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;4.0.0 GA is no longer date-gated.&lt;/strong&gt; GA ships &lt;strong&gt;“done when done.”&lt;/strong&gt; Release candidates
keep shipping to early adopters off &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; in the meantime, and &lt;strong&gt;red-CI-no-release&lt;/strong&gt;
(charter Standing Order #9) still holds &lt;strong&gt;per release candidate&lt;/strong&gt;. The milestone-11
identity of the gate is unchanged; only the fixed due date is dropped. (The GitHub
milestone object’s own due date is handled outside this roadmap.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The GA gate expands beyond local integrity.&lt;/strong&gt; It is now local CLI integrity &lt;strong&gt;plus&lt;/strong&gt;
(a) &lt;strong&gt;charter modular extraction&lt;/strong&gt; and (b) the &lt;strong&gt;mission-status API backend&lt;/strong&gt;. The
“re-synthesized to local-integrity-only” framing from 2026-10-06 is superseded: those two
structural pieces move from “4.x after GA” onto the gate.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter modular extraction → its own repository, and it is GA-gating.&lt;/strong&gt; The charter
(&lt;code dir=&quot;auto&quot;&gt;src/charter/offering/&lt;/code&gt;, or all of &lt;code dir=&quot;auto&quot;&gt;src/charter/&lt;/code&gt;) becomes an independently-released unit
consumed through its public surface, like &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;. Its
precondition, &lt;strong&gt;#645&lt;/strong&gt; (move the ~129 &lt;code dir=&quot;auto&quot;&gt;specify_cli → charter&lt;/code&gt; imports onto the stable API),
is now GA-gating. Grounded in #3101, ADR
&lt;a href=&quot;/adr/3.x/2026-08-02-1-charter-wheel-assessment/&quot;&gt;2026-08-02-1&lt;/a&gt; and ADR
&lt;a href=&quot;/adr/3.x/2026-04-25-1-shared-package-boundary/&quot;&gt;2026-04-25-1&lt;/a&gt;. The repository
extraction itself is recorded in ADR
&lt;a href=&quot;/adr/4.x/2026-10-12-2-charter-extraction-to-its-own-repository/&quot;&gt;2026-10-12-2&lt;/a&gt;; the
extraction mechanics ride with a dedicated epic (to be filed).
&lt;strong&gt;Superseded 2026-10-19 (operator ruling): the Python charter stays in core until it is retired and nothing Python moves to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt;; offering reads cut over to the &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; service through &lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt;, and the GA leg is a frozen seam plus a green conformance corpus, not an extraction. ADR 2026-10-12-2 is superseded by &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; ADR-0008 and ADR-0010; see ADR &lt;a href=&quot;/adr/4.x/2026-10-16-1-extract-charter-offering-first-activation-rework-post-ga/&quot;&gt;2026-10-16-1&lt;/a&gt;, Amendment 2026-10-19.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The mission-status read API is the open-core producer surface&lt;/strong&gt; (internally “Build
Kitty”), not a Team Kitty surface. Its Java implementation (&lt;code dir=&quot;auto&quot;&gt;services/mission-status-api/&lt;/code&gt;,
epic #5528) is to &lt;strong&gt;start in-repo as a modular component&lt;/strong&gt; and be &lt;strong&gt;extracted as needed as
an open-core surface&lt;/strong&gt; — never into a Team Kitty repository (the service directory is
in-repo and the read service is substantially built). &lt;code dir=&quot;auto&quot;&gt;contracts/mission-status/&lt;/code&gt; and the conformance fixtures
already ship and stay canonical beside the Python reducer
(&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;,
Accepted). Its backend is the GA-gating piece from rule 2.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Team Kitty = “Multiplayer Mode,” the consumer side.&lt;/strong&gt; UI/multiplayer surfaces
(mission-ui, the pack composer) &lt;strong&gt;consume&lt;/strong&gt; the open-core producer
API across its contract boundary. The “do not build toward Team Kitty” rule is
&lt;strong&gt;scoped-lifted&lt;/strong&gt; for (i) consumer-side UI/multiplayer built on that API and (ii) the
event-dispatch / produce-drain adapter seam (&lt;code dir=&quot;auto&quot;&gt;status/adapters.py&lt;/code&gt;). Everything else hosted
(zeitgeist auth, the hosted backend, the SaaS surface) stays frozen unless the operator
asks (&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;,
Amendment 2026-10-12).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The packs source home moves to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-open-packs&lt;/code&gt;.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;packs/internal/&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; here are fetched, pinned copies (pins in &lt;code dir=&quot;auto&quot;&gt;packs/&amp;#x3C;pack&gt;.source.yaml&lt;/code&gt;, placed by &lt;code dir=&quot;auto&quot;&gt;make sync-packs&lt;/code&gt;); the source is authored in
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-open-packs&lt;/code&gt;. This is a source-location move only: the no-bundle invariant is
unchanged and ADR &lt;a href=&quot;/adr/3.x/2026-08-16-3-spec-kitty-internal-is-a-public-org-pack-not-force-shipped/&quot;&gt;2026-08-16-3&lt;/a&gt; is not reversed.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;direction-update-2026-10-01-hosted-collaboration-is-off-the-critical-path&quot;&gt;Direction update (2026-10-01): hosted collaboration is off the critical path&lt;/h2&gt;
&lt;p&gt;The CEO, CPO and CTO froze Team Kitty / SaaS work and deprioritised it while the commercial
vision is reviewed. This section overrides anything below that treats hosted collaboration,
auth or Zeitgeist as release-gating. Four rules follow for the rest of the 4.x line:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;4.0.0 GA is the &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;4.0.0 release scope&lt;/a&gt;
milestone and nothing else.&lt;/strong&gt; No Team Kitty, Zeitgeist or hosted-auth item gates it. The
hosted-facing epics (#3892 zeitgeist-client auth, and the auth P1 residuals) stay on
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/8&quot;&gt;4.x Work&lt;/a&gt; and wait for the freeze to
lift. The retired sync transport stays retired.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;All external interaction flows through the adapter module.&lt;/strong&gt; The CLI core writes its
events and does not know where they go. The status fan-out in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/status/adapters.py&lt;/code&gt; is that seam, and it is the starting point for the
envisioned publish/subscribe system. Zeitgeist is one possible consumer; a local UI is
another. No other module talks to an external system directly.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Producing and draining are two separate concerns, each behind its own toggle.&lt;/strong&gt;
Producing an event (writing it to the bus) never depends on whether a drain is enabled,
and a producer never knows which system a drain feeds. Today the code couples them: the
fan-out functions check &lt;code dir=&quot;auto&quot;&gt;drain_posture()&lt;/code&gt; before any handler runs, and the hosted-posture
contract (&lt;code dir=&quot;auto&quot;&gt;kitty-specs/hosted-opt-in-drain-ledger-01M3FFEV/contracts/hosted-posture.md&lt;/code&gt;)
silences producers when drain is off. Decoupling them amends
&lt;a href=&quot;/adr/3.x/2026-09-26-3-hosted-interaction-opt-in/&quot;&gt;ADR 2026-09-26-3&lt;/a&gt; and needs a 4.x
ADR of its own.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The charter ships on its own, in its own repository.&lt;/strong&gt; Charter content that tells users
to run the CLI is acceptable. The strangler blocker is code coupling: &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; imports
&lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; internals directly (129 files at &lt;code dir=&quot;auto&quot;&gt;8a581be1&lt;/code&gt;), and those imports must move onto a
stable API (#645) before the charter can be packaged separately. &lt;strong&gt;As of the 2026-10-12
update, #645 is GA-gating and the charter becomes an independently-released external
contract package in its own repository&lt;/strong&gt; (not just “shippable alone”).
&lt;strong&gt;Superseded 2026-10-19:&lt;/strong&gt; the charter does not ship from its own repository as a Python
package; see the note under direction item 3 above.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Theme 4’s hosted &lt;em&gt;backend&lt;/em&gt; lane is frozen; its &lt;strong&gt;consumer side was re-scoped on 2026-10-12&lt;/strong&gt;
(Team Kitty = “Multiplayer Mode,” above). The Stability and Maturity themes apply to the
&lt;strong&gt;local&lt;/strong&gt; CLI.&lt;/p&gt;
&lt;h2 id=&quot;release-posture&quot;&gt;Release posture&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Read 2026-10-06. Verify live state with &lt;code dir=&quot;auto&quot;&gt;gh issue view &amp;#x3C;n&gt; --repo spec-kitty/spec-kitty&lt;/code&gt;
before acting; milestones and counts move between release candidates.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Five release candidates have shipped; rc6 is open on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;.&lt;/strong&gt; PyPI upload dates: rc1
2026-09-13, rc2 09-14, rc3 09-17, rc4 09-21, rc5 10-02. &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; carries the unreleased
&lt;code dir=&quot;auto&quot;&gt;4.0.0rc6&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;[Unreleased]&lt;/code&gt; in &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/CHANGELOG.md&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;CHANGELOG.md&lt;/code&gt;&lt;/a&gt;, &lt;code dir=&quot;auto&quot;&gt;version&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;rc5 shipped under a waiver.&lt;/strong&gt; The release workflow requires a green nightly on the release
commit (#5034). No nightly has been green since 2026-09-15, so on 2026-10-02 a &lt;code dir=&quot;auto&quot;&gt;skip_nightly&lt;/code&gt;
input was added to manual release runs and rc5 was published with the gate skipped and the
waiver logged. rc5 also carried defects in &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;; their fixes are on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; and reach
users only with rc6.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The GA gate, &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;milestone 11&lt;/a&gt;:&lt;/strong&gt; 14 open,
210 closed (201 issues, 119 of them P0). &lt;strong&gt;GA is done-when-done — no fixed due date&lt;/strong&gt; (see the
2026-10-12 direction update); the milestone object’s own date field is managed outside this
roadmap. Of the 16 issues open on 2026-10-01, every one except #5419 has closed. 58 issues
closed on the milestone from 2026-10-01 to 2026-10-06, 29 of them P0. This milestone is local
integrity; the two other GA-gating pieces (charter modular extraction #645, and the
mission-status API backend) are tracked on their own epics — see the dependency spine.&lt;/p&gt;
&lt;p&gt;The 14 open issues, by kind:&lt;/p&gt;



































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Kind&lt;/th&gt;&lt;th&gt;Issues&lt;/th&gt;&lt;th&gt;Gates GA because&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Nightly&lt;/td&gt;&lt;td&gt;&lt;strong&gt;#5419&lt;/strong&gt; (P0, performance suite)&lt;/td&gt;&lt;td&gt;The 2026-10-06 nightly passed 56 of 57 jobs; this is the one red. rc6 needs it green or another waiver.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Correctness residuals&lt;/td&gt;&lt;td&gt;#5638 (rollback leaves coordination status files dirty), #5704 (protected &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; create leaves a scaffold without &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;), #5726 (timing-dependent error code when &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; re-runs)&lt;/td&gt;&lt;td&gt;P2 bugs in the landing and create paths.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Agent integration&lt;/td&gt;&lt;td&gt;#702 (P1, Codex &lt;code dir=&quot;auto&quot;&gt;.agents/skills&lt;/code&gt; drift)&lt;/td&gt;&lt;td&gt;The one open P1.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Docs&lt;/td&gt;&lt;td&gt;#5428 (P2)&lt;/td&gt;&lt;td&gt;Docs cleanup after the 4.x re-anchor; this re-synthesis is part of it.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Structural hygiene&lt;/td&gt;&lt;td&gt;#2560, #2561, #2562 (&lt;code dir=&quot;auto&quot;&gt;runtime_bridge&lt;/code&gt; strangler slices), #3732 (doctrine packs → charter packs rename), #4836 (doctrine→charter drift in operator surfaces), #5538 (residual kind-vocabulary mirror), #5629 (&lt;code dir=&quot;auto&quot;&gt;tasks_move_task.py&lt;/code&gt; split), #5715 (last CLI import in the lanes seam)&lt;/td&gt;&lt;td&gt;P2/P3 debt. Each is a candidate to move to CLI 4.x stable if it does not land before GA.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;strong&gt;Not on milestone 11, but raised as GA questions (2026-10-06):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#5780&lt;/strong&gt; and &lt;strong&gt;#5758&lt;/strong&gt; (P0, no milestone, no owner). &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt;
read only local branches, so a teammate’s pushed rejection of a work package is ignored in a
multi-clone team.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#5722&lt;/strong&gt; and &lt;strong&gt;#5603&lt;/strong&gt; (P1, no milestone). &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; has no
reconciliation gate and no rollback, and it force-deletes the mission or coordination branch.
Automation that lands work through the API does not get the protections &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; has.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Milestone routing.&lt;/strong&gt; Milestone 11 is the local-integrity leg; the charter-extraction (#645)
and mission-status API legs are tracked on their epics.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;&lt;strong&gt;4.0.0 release scope&lt;/strong&gt;&lt;/a&gt; (11): the GA
gate.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/12&quot;&gt;&lt;strong&gt;CLI 4.x stable&lt;/strong&gt;&lt;/a&gt; (12): stable 4.x
work after GA, including deferrals out of the gate (229 open).&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/8&quot;&gt;&lt;strong&gt;4.x Work&lt;/strong&gt;&lt;/a&gt; (8): the former &lt;code dir=&quot;auto&quot;&gt;4.0.0&lt;/code&gt;
milestone; hosted and product work planned beyond the stabilization release, including the
frozen hosted lane (81 open).&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/15&quot;&gt;&lt;strong&gt;Infra &amp;#x26; Enablers 4.x&lt;/strong&gt;&lt;/a&gt; (15): CI,
tooling and quality-debt work, including #1928 and the CI follow-ups #5652 and #5624 (76 open).&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/13&quot;&gt;&lt;strong&gt;Live Work NOW (post-launch)&lt;/strong&gt;&lt;/a&gt; (13):
five open, including the auth residual #2941.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;drift-since-the-declaration&quot;&gt;Drift since the declaration&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&quot;/changelog/4.0.0/&quot;&gt;4.0.0 declaration&lt;/a&gt; was written on 2026-09-04, two days before the
Convergence (#3881) retired the local sync transport and made this repository a &lt;strong&gt;client&lt;/strong&gt; of
&lt;code dir=&quot;auto&quot;&gt;spec-kitty/zeitgeist&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty/saas&lt;/code&gt;
(&lt;a href=&quot;/adr/3.x/2026-09-06-1-convergence-retirement-and-client-repo-inversion/&quot;&gt;ADR 2026-09-06-1&lt;/a&gt;),
and four weeks before hosted work was frozen. Every epic it names has since moved:&lt;/p&gt;

















































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Declared advance (2026-09-04)&lt;/th&gt;&lt;th&gt;State (2026-10-06)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1800&lt;/strong&gt; SaaS sync &amp;#x26; event-envelope hardening&lt;/td&gt;&lt;td&gt;Closed.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1091&lt;/strong&gt; Team Kitty launch gate&lt;/td&gt;&lt;td&gt;Closed 2026-09-13 (milestone 3.2.7).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#3322&lt;/strong&gt; CLI auth &amp;#x26; token lifecycle&lt;/td&gt;&lt;td&gt;Closed; the client-side successor &lt;strong&gt;#3892&lt;/strong&gt; is open on 4.x Work and frozen.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#3549&lt;/strong&gt; event-log integrity&lt;/td&gt;&lt;td&gt;Closed; the local successor &lt;strong&gt;#3893&lt;/strong&gt; is open on 4.x Work.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#3278&lt;/strong&gt; P0 sync false success&lt;/td&gt;&lt;td&gt;Closed as not planned (the sync transport is gone).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#3178&lt;/strong&gt; P0 wrong-authority egress&lt;/td&gt;&lt;td&gt;Closed as completed.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#2519&lt;/strong&gt; charter authoring &amp;#x26; lifecycle&lt;/td&gt;&lt;td&gt;Open on CLI 4.x stable.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#2173&lt;/strong&gt; infrastructure-to-logic ports&lt;/td&gt;&lt;td&gt;Closed 2026-09-27 on milestone 11.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1619&lt;/strong&gt; one execution context&lt;/td&gt;&lt;td&gt;Open on CLI 4.x stable (31 of 44 sub-issues closed on 2026-10-01).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#1797&lt;/strong&gt; degod / unshim delivery&lt;/td&gt;&lt;td&gt;Closed as not planned.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Never design against or “re-enable” the old sync path; see
&lt;a href=&quot;/context/team-kitty/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/context/team-kitty.md&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;the-dependency-spine&quot;&gt;The dependency spine&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Re-anchored 2026-10-12. GA is done-when-done; the gate now has three legs.&lt;/em&gt;&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;plaintext&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;   &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;THE GA GATE (done when done — red CI == no release, per release candidate)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;     &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;┌ LOCAL INTEGRITY (milestone 11)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;     &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│    green nightly (#5419, 1 of 57 jobs red) · landing+create residuals (#5638 #5704 #5726)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;     &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│    agent integration (#702) · docs (#5428) · structural hygiene (#2560-2 #3732 #4836 #5538 ...)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;     &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│    UNDECIDED: pushed-rejection P0s (#5780 #5758), orchestrator-api gate+rollback (#5722 #5603)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;     &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;├ CHARTER SEAM (offering reads — ADR 2026-10-16-1, Amendment 2026-10-19)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;     &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│    #6188 imports onto charter.offering.api (DONE) ──▶ #6099 frozen seam + green conformance corpus&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;     &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│    ──▶ offering stays in core, replaced in place by the spec-kitty-charter service (no extraction)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;     &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;└ MISSION-STATUS API BACKEND + READ SURFACE (open-core producer surface, &quot;Build Kitty&quot;)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;          &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;#5528 Mission Status Read API (contract `1.0.0-SNAPSHOT` in-repo, unreleased; services/mission-status-api/ in-repo, read service substantially built)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;          &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;──▶ #957 mission detail (GA) ; #5532 readers re-point / #5533 routes rehome (OFF-GATE, CLI 4.x stable)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;                                                                     &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;──▶  4.0.0 GA&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;   &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;OFF-GATE 4.x STRUCTURAL (continues after GA)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;       &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;produce / drain decoupling (ADR tbd) ──▶ adapter seam as pub/sub (consumer side unblocked 2026-10-12)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;       &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;charter.activation drain (236 reaches) + activation rework (CLI 4.x stable — ADR 2026-10-16-1)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;       &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;#2519 later Java charter writes (CLI 4.x stable) · #1619 one execution context (CLI 4.x stable)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;       &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;Team Kitty = &quot;Multiplayer Mode&quot;: consumer UI/multiplayer on the producer API&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;   &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;FROZEN (hosted backend — waits for the commercial review)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;       &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;#3892 zeitgeist-client auth · auth residual #2941 · hosted backend · SaaS surface&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;   &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;QUALITY DEBT (Infra &amp;#x26; Enablers 4.x, OUTSIDE the blocking graph)&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 class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;       &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;#1928 ──▶ #4304 #4305 #2970 (security and BLOCKER findings still open)&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;Reading order:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;The nightly closes the release.&lt;/strong&gt; Every consolidation-safety and coordination-status P0
that was open on 2026-10-01 has closed. #5419 is the only P0 left on the gate, and a green
nightly is also what rc6 needs without a waiver.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two decisions sit outside the gate.&lt;/strong&gt; The pushed-rejection P0s (#5780, #5758) and the
unguarded API landing path (#5722, #5603) are in the same “says success, did the wrong
thing” class as the defects the cycle fixed. Either pull them onto milestone 11 or record
why GA ships without them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two structural pieces are now on the GA gate (2026-10-12).&lt;/strong&gt; Charter modular extraction —
scoped to &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt;&lt;/strong&gt; (ADR 2026-10-16-1) — is &lt;strong&gt;GA-gating&lt;/strong&gt; via epic #6099 (four
offering-extraction phases). Its import-move precondition #6188 is &lt;strong&gt;done&lt;/strong&gt; and #645 is closed
&lt;code dir=&quot;auto&quot;&gt;not_planned&lt;/code&gt;; the &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; drain is &lt;strong&gt;post-GA&lt;/strong&gt; (CLI 4.x stable). The mission-status API
&lt;strong&gt;backend&lt;/strong&gt; — the open-core producer surface
(&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;,
Accepted) — is also &lt;strong&gt;GA-gating&lt;/strong&gt;: the bundled dashboard is already removed (#5530) and the
contract is in-repo as &lt;code dir=&quot;auto&quot;&gt;1.0.0-SNAPSHOT&lt;/code&gt;, unreleased (&lt;code dir=&quot;auto&quot;&gt;contracts/mission-status/&lt;/code&gt;). The Java read service
&lt;code dir=&quot;auto&quot;&gt;services/mission-status-api/&lt;/code&gt; is &lt;strong&gt;in-repo and substantially built&lt;/strong&gt; (read-only, loopback). The
value-bearing read surface (epic #5528 + #957 mission detail) is GA-gating; the ledger already has
live readers, so the reader-consolidation refactors #5532/#5533 stay &lt;strong&gt;off-gate&lt;/strong&gt; (CLI 4.x stable),
per ADR 2026-10-16-1. What stays &lt;strong&gt;off&lt;/strong&gt; the GA
gate and continues on the 4.x line: produce/drain decoupling
(the precondition for any external &lt;em&gt;consumer&lt;/em&gt;), the consumer-side UI/multiplayer (“Multiplayer
Mode”), the charter read/write service strangler
(&lt;a href=&quot;/adr/4.x/2026-10-03-1-charter-read-write-service-strangler/&quot;&gt;ADR 2026-10-03-1&lt;/a&gt;,
Proposed; starts only after callers move onto #645), and #1619.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The hosted backend is frozen, not cancelled.&lt;/strong&gt; Nothing on that lane is deleted; it waits.
Its &lt;em&gt;consumer&lt;/em&gt; side (UI/multiplayer on the producer API) and the produce/drain adapter seam
were scoped back in on 2026-10-12 — see the direction update.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Quality debt is a standing campsite epic&lt;/strong&gt;, outside the blocking graph. It burns down
per touched file and never gates a release candidate.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;per-theme-progress-and-scope&quot;&gt;Per-theme progress and scope&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;State read 2026-10-06. An issue can serve more than one theme; it is listed under its primary
theme.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&quot;theme-1--stability-local-integrity&quot;&gt;Theme 1 — Stability (local integrity)&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;The bulk of the cycle, and nearly done for GA.&lt;/strong&gt; 119 of the 201 closed milestone-11 issues
were P0. The recurring defect was a command that exited 0 while it deleted, overwrote or
dropped something.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Landing work (&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;).&lt;/strong&gt; Since rc5: canceled work no longer lands through a
dependent lane (#5569); a resumed run no longer drops a lane (#5571); commits made after
approval are refused until the work package is approved again (#5668,
&lt;a href=&quot;/adr/4.x/2026-10-04-5-approval-stamp-bounds-the-approved-claim/&quot;&gt;ADR 2026-10-04-5&lt;/a&gt;);
a rollback keeps a teammate’s commit (#5666); &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; reports what it could not restore
(#5686); approved code missing from the target fails and rolls back (#5788). Before rc5:
ignored local files are no longer overwritten or deleted (#5392, #5400) and every exit after
the first mutation rolls back through one authority (#5385).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Workflow and coordination status.&lt;/strong&gt; Status and decision events no longer split between
two checkouts (#5519, #5513, #5440); a work package prompt no longer contradicts
&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; (#3931); a copied project no longer moves the original’s cursor (#5390);
&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; missions have no lanes (#5100).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Open on the gate:&lt;/strong&gt; #5638, #5704, #5726 (P2).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Open off the gate:&lt;/strong&gt; #5780, #5758 (P0), #5722, #5603 (P1). See “Release posture”.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Record:&lt;/strong&gt; the sync-era reliability items closed before 2026-09-14 (#3723, #3700, #2736,
#2665, #2264 and others) belong to the retired transport.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Progress:&lt;/strong&gt; heavy. The new behaviour adds refusals: a mission approved before rc5 stops at
&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;APPROVAL_STAMP_MISSING&lt;/code&gt; until each work package is reviewed again or
attested. The rc6 upgrade notes must say so.&lt;/p&gt;
&lt;h3 id=&quot;theme-2--maturity-one-honest-local-store-owned-seams&quot;&gt;Theme 2 — Maturity (one honest local store, owned seams)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Done:&lt;/strong&gt; six of the largest modules were split after rc5 (&lt;code dir=&quot;auto&quot;&gt;mission_finalize.py&lt;/code&gt; 5,145 →
1,454 lines, &lt;code dir=&quot;auto&quot;&gt;consolidation/executor.py&lt;/code&gt; 4,145 → 833, &lt;code dir=&quot;auto&quot;&gt;orchestrator_api/commands.py&lt;/code&gt; 4,097 →
511, &lt;code dir=&quot;auto&quot;&gt;tasks_move_task.py&lt;/code&gt; 3,786 → 1,887, &lt;code dir=&quot;auto&quot;&gt;cli/commands/implement.py&lt;/code&gt; 2,304 → 443,
&lt;code dir=&quot;auto&quot;&gt;core/mission_creation.py&lt;/code&gt; 2,173 → 742).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Open:&lt;/strong&gt; &lt;strong&gt;#3893&lt;/strong&gt; (local event-log integrity, 4.x Work), #3887 (&lt;code dir=&quot;auto&quot;&gt;doctor.py&lt;/code&gt; residue, 4.x
Work), and on the gate #5629 (finish the &lt;code dir=&quot;auto&quot;&gt;tasks_move_task.py&lt;/code&gt; split) and #2560–#2562
(&lt;code dir=&quot;auto&quot;&gt;runtime_bridge&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Closed as not planned:&lt;/strong&gt; #2955 (the Team Kitty envelope producers it would have folded
are frozen).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;theme-3--extensibility-governed-front-door--stable-api&quot;&gt;Theme 3 — Extensibility (governed front door + stable API)&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Two of its pieces are now GA-gating (2026-10-12).&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;GA-gating (2026-10-12):&lt;/strong&gt; &lt;strong&gt;#645&lt;/strong&gt; (stable application API) as the precondition for
&lt;strong&gt;charter modular extraction&lt;/strong&gt; into its own externally-released repository; and the
&lt;strong&gt;mission-status API backend&lt;/strong&gt; — the open-core &lt;strong&gt;producer&lt;/strong&gt; surface (ADR
&lt;a href=&quot;/adr/4.x/2026-10-01-2-mission-status-read-api-and-dashboard-extraction/&quot;&gt;2026-10-01-2&lt;/a&gt;,
Accepted), epic &lt;strong&gt;#5528&lt;/strong&gt;, &lt;code dir=&quot;auto&quot;&gt;services/mission-status-api/&lt;/code&gt; slated to start in-repo (direction;
the directory does not exist yet — &lt;code dir=&quot;auto&quot;&gt;contracts/mission-status/&lt;/code&gt; does), extracted when its
contract freezes (never into a Team Kitty repo).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Open (off-gate, 4.x line):&lt;/strong&gt; &lt;strong&gt;#901&lt;/strong&gt; (governed front door, 4.x Work), #5532 and #5533
(reader re-point / route rehome, CLI 4.x stable), and the consumer-side “Multiplayer Mode”
UI/multiplayer that &lt;em&gt;consumes&lt;/em&gt; the producer API.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Done:&lt;/strong&gt; the bundled dashboard is removed (#5530); the Mission Status contract is in-repo as
&lt;code dir=&quot;auto&quot;&gt;1.0.0-SNAPSHOT&lt;/code&gt; (unreleased), with lint, breaking-change checks and a test against every mission
in the repository; teams can share agent commands as pack skills
(&lt;a href=&quot;/adr/3.x/2026-09-27-1-pack-skills-share-commands-through-charter-packs/&quot;&gt;ADR 2026-09-27-1&lt;/a&gt;);
org packs carry their own built-in override sanction
(&lt;a href=&quot;/adr/4.x/2026-10-05-3-org-packs-ship-their-builtin-override-sanction/&quot;&gt;ADR 2026-10-05-3&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;On milestone 11:&lt;/strong&gt; #3732 and #4836 (the doctrine → charter vocabulary), #5538.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Progress:&lt;/strong&gt; the producer API has a contract in-repo (unreleased) and a planned in-repo service build; its
backend and the charter extraction are now gate items, and the governed front door and the
consumer UI remain 4.x-line work.&lt;/p&gt;
&lt;h3 id=&quot;theme-4--team-kitty--multiplayer-mode-consumer-side-backend-frozen&quot;&gt;Theme 4 — Team Kitty = “Multiplayer Mode” (consumer side; backend frozen)&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Re-scoped 2026-10-12.&lt;/strong&gt; Team Kitty is the &lt;strong&gt;consumer&lt;/strong&gt; side of the open-core producer API
(mission-ui, the pack composer). The &lt;strong&gt;backend&lt;/strong&gt; lane stays frozen and
nothing on it gates GA; the &lt;strong&gt;consumer&lt;/strong&gt; side (UI/multiplayer on the mission-status API) and
the produce/drain adapter seam (&lt;code dir=&quot;auto&quot;&gt;status/adapters.py&lt;/code&gt;) are no longer blocked (ADR
&lt;a href=&quot;/adr/4.x/2026-10-06-1-team-kitty-surfaces-are-hidden-unless-drain-is-on/&quot;&gt;2026-10-06-1&lt;/a&gt;,
Amendment 2026-10-12). Everything hosted below stays frozen unless the operator asks.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Open (frozen backend):&lt;/strong&gt; &lt;strong&gt;#3892&lt;/strong&gt; (zeitgeist-client auth, 4.x Work), #2941 (widen bypasses
renewable CLI auth, Live Work NOW), #4195 (review of the #4121 charter forward-port, 4.x Work).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Closed:&lt;/strong&gt; #1091, #3322, #3233, #3980, #3277, #1621.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Closed as not planned:&lt;/strong&gt; #3196, #3197, #3198 (sync consent and identity, retired with the
transport), #2520 (charter events to SaaS; a hosted charter signal would need a new issue
built on Zeitgeist).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;cross-cutting--sonar--quality-debt&quot;&gt;Cross-cutting — Sonar / quality debt&lt;/h3&gt;
&lt;p&gt;Parent &lt;strong&gt;#1928&lt;/strong&gt; is on Infra &amp;#x26; Enablers 4.x. The finding-class children #4299–#4303 were closed
as not planned (the charter’s Sonar standing orders handle them per touched file), and #2969
was fixed.&lt;/p&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Issue&lt;/th&gt;&lt;th&gt;Finding class&lt;/th&gt;&lt;th&gt;State&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#4304&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;S6350 ×17 and other &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; security findings&lt;/td&gt;&lt;td&gt;Open, P1&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#4305&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;S3516 constant-return BLOCKER in &lt;code dir=&quot;auto&quot;&gt;core/file_lock.py&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Open, P1&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;#2970&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;4 BLOCKER S2083 path-injection findings (≥1 likely false positive)&lt;/td&gt;&lt;td&gt;Open, P2&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;strong&gt;Progress:&lt;/strong&gt; deliberately post-GA. Adjudicate the security children before remediating, and
record false-positive rulings.&lt;/p&gt;
&lt;h2 id=&quot;exit-criteria-for-400&quot;&gt;Exit criteria for 4.0.0&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Re-anchored 2026-10-12. GA is done-when-done; the gate has three legs (criteria 1, 5, 6).&lt;/em&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Local integrity: milestone 11 is closed.&lt;/strong&gt; Every issue on
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;4.0.0 release scope&lt;/a&gt; is closed or
re-milestoned with a rationale.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The nightly is green on the release commit.&lt;/strong&gt; Red CI means no release (charter Standing
Order 9), &lt;strong&gt;per release candidate&lt;/strong&gt;. A &lt;code dir=&quot;auto&quot;&gt;skip_nightly&lt;/code&gt; waiver is an operator decision,
recorded each time; rc5 used one.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The CLI never reports success while losing or stranding local work.&lt;/strong&gt; This is what the
consolidation, status and workflow P0s test. #5780 and #5758 are in this class and need an
explicit in-or-out decision.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No new shadow path.&lt;/strong&gt; Every landing routes onto an existing authority. No re-introduction
of the retired sync transport, and no module other than the adapter seam talks to an
external system.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter seam — offering leg (GA-gating; ADR 2026-10-16-1, Amendment 2026-10-19).&lt;/strong&gt; The
import move (#6188) is done and #645 is closed &lt;code dir=&quot;auto&quot;&gt;not_planned&lt;/code&gt;. The GA leg is a &lt;strong&gt;frozen
&lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt; seam and a green conformance corpus&lt;/strong&gt; (epic #6099, re-scoped), not an
extraction: the Python offering stays in core and is replaced in place by the
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; service (&lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; ADR-0008, ADR-0010). The
&lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; drain/rework is &lt;strong&gt;post-GA&lt;/strong&gt; (CLI 4.x stable).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mission-status API backend + read surface (GA-gating; ADR 2026-10-01-2, 2026-10-16-1).&lt;/strong&gt;
The open-core producer surface ships its backend (contract canonical beside the Python reducer,
&lt;code dir=&quot;auto&quot;&gt;services/mission-status-api/&lt;/code&gt; in-repo) and the value-bearing read surface that realizes event
value (epic #5528 + #957 mission detail). The ledger already has live readers; the
reader-consolidation refactors #5532/#5533 stay off-gate (CLI 4.x stable).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(Post-GA) Off-gate structural dispositioned.&lt;/strong&gt; The produce/drain decoupling, #901, #1619
and the consumer-side “Multiplayer Mode” UI land or are re-milestoned on the 4.x line with a
rationale.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(Post-GA) Security debt adjudicated.&lt;/strong&gt; #4304, #4305 and #2970 close or carry recorded
false-positive rulings.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;risks--watch-items&quot;&gt;Risks / watch items&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;rc5 is the newest release and has known landing defects.&lt;/strong&gt; Users get the fixes only with
rc6. Four rc5 fixes were found not to hold one day after release; the window between a fix
on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; and a release is user exposure.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The nightly has not been green since 2026-09-15.&lt;/strong&gt; The 2026-10-06 run had one red job of
57. Most reds came from suites only the nightly runs, which fell behind changes that merged
green; the commit-recipe check now runs per PR (#5708), but the performance, Python 3.13 and
integration suites have not moved. Tests that no CI job runs (#5652) hide pinned reds.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The release gate depends on a token.&lt;/strong&gt; It fails closed without
&lt;code dir=&quot;auto&quot;&gt;RELEASE_NIGHTLY_DISPATCH_TOKEN&lt;/code&gt;; the new dedicated token’s scope is not yet written down
(see &lt;code dir=&quot;auto&quot;&gt;RELEASE_CHECKLIST.md&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The gate refills.&lt;/strong&gt; Milestone 11 went from 11 open (2026-09-30) to 16 (2026-10-01) to 14
(2026-10-06) while 58 issues closed. 159 issues were opened in the four days after rc5
against 90 closed, 33 of them new open P1s. With GA now done-when-done (no fixed due date),
the cut-off is a judgment call at each release candidate, not a calendar date: a P2/P3
hygiene item that is not GA-gating moves to CLI 4.x stable with a one-line rationale rather
than holding the release.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review depends on one person.&lt;/strong&gt; 60 of the 66 PRs merged after rc5 have one author.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The API landing path is unguarded.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; lacks the
reconciliation gate and rollback (#5722, #5603).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Client-repo inversion.&lt;/strong&gt; Auth and event work for the hosted path is authored upstream in
&lt;code dir=&quot;auto&quot;&gt;spec-kitty/zeitgeist&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty/saas&lt;/code&gt;. A PR that edits a retired local-sync surface is
designing against a dead subsystem; flag it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor.py&lt;/code&gt; residue (#3887).&lt;/strong&gt; #1623 closed without shrinking the module; keep the
follow-up tracked.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;immediate-next-steps&quot;&gt;Immediate next steps&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Green the nightly (#5419)&lt;/strong&gt;, then cut rc6 without a waiver.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Decide #5780 and #5758&lt;/strong&gt;: on milestone 11, or GA ships without them with the reason
recorded.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Decide #5722 and #5603&lt;/strong&gt;: fix the API landing path for GA, or document that automation
must use &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; until it is.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Judge the cut-off per release candidate, not by calendar date (GA is done-when-done).&lt;/strong&gt;
Move any non-GA-gating P2/P3 hygiene item to CLI 4.x stable with a one-line rationale.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Write the produce/drain ADR&lt;/strong&gt; (4.x), amending ADR 2026-09-26-3, then split the toggles in
&lt;code dir=&quot;auto&quot;&gt;status/adapters.py&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;core/hosted_posture.py&lt;/code&gt;. The adapter seam is now unblocked for the
consumer side (2026-10-12).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Move the &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; imports onto #645&lt;/strong&gt; so the charter can be extracted
into its own externally-released repository — &lt;strong&gt;this is now GA-gating&lt;/strong&gt;. Per
&lt;a href=&quot;/adr/4.x/2026-09-30-1-allowlist-ratchets-are-priced-debt/&quot;&gt;ADR 2026-09-30-1&lt;/a&gt;, drain
them rather than holding them in an allowlist. File the charter-repo-extraction epic/ADR.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ratified 2026-10-12:&lt;/strong&gt; ADR 2026-10-01-2 is now &lt;strong&gt;Accepted&lt;/strong&gt; (open-core producer surface;
the service is to start in-repo and be extracted when frozen). ADR 2026-10-03-1 (charter
read/write service strangler)
remains Proposed and off-gate.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Re-run this synthesis at each rc bump.&lt;/strong&gt; Read
&lt;code dir=&quot;auto&quot;&gt;gh api repos/spec-kitty/spec-kitty/milestones/11&lt;/code&gt; and the milestone’s open issues before
acting.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;links&quot;&gt;Links&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Milestones: &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/11&quot;&gt;4.0.0 release scope&lt;/a&gt; (GA
gate) · &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/12&quot;&gt;CLI 4.x stable&lt;/a&gt; ·
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/8&quot;&gt;4.x Work&lt;/a&gt; ·
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/milestone/15&quot;&gt;Infra &amp;#x26; Enablers 4.x&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Declaration of intent: &lt;a href=&quot;/changelog/4.0.0/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;4.0.0.md&lt;/code&gt;&lt;/a&gt; · Convention:
&lt;a href=&quot;/changelog/release-goals/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;release-goals.md&lt;/code&gt;&lt;/a&gt; · Summary:
&lt;a href=&quot;/plans/4-x-executive-overview/&quot;&gt;4.x Executive Overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Prior cycle roadmap: &lt;a href=&quot;/plans/3-2-x-milestone-roadmap/&quot;&gt;3.2.x Milestone Roadmap&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Convergence / client-repo inversion:
&lt;a href=&quot;/adr/3.x/2026-09-06-1-convergence-retirement-and-client-repo-inversion/&quot;&gt;ADR 2026-09-06-1&lt;/a&gt; ·
hosted context: &lt;a href=&quot;/context/team-kitty/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/context/team-kitty.md&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Durable domain plans: &lt;a href=&quot;/plans/domains/doctrine-charter-domain-plan/&quot;&gt;Doctrine &amp;#x26; Charter&lt;/a&gt; ·
&lt;a href=&quot;/plans/domains/api-dashboard-domain-plan/&quot;&gt;API &amp;#x26; Dashboard&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
