<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/plans/domains/doctrine-charter-domain-plan/">
  <id>https://docs.spec-kitty.ai/plans/domains/doctrine-charter-domain-plan/</id>
  <title>Doctrine &amp; Charter — Domain Plan</title>
  <updated>2026-10-22T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/plans/domains/doctrine-charter-domain-plan/"/>
  <summary>Durable plan for the doctrine/charter surface: charter lifecycle, sole-door access, extensibility, activation, fail-closed reads, public API, and glossary.</summary>
  <content type="html">&lt;span id=&quot;doctrine--charter--domain-plan&quot;&gt;&lt;/span&gt;
&lt;p&gt;&lt;strong&gt;Audience:&lt;/strong&gt; the project maintainer — technical, time-pressed, wants signal over ritual.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Status: durable domain plan (throughline).&lt;/strong&gt; Unlike the release-scoped
&lt;code dir=&quot;auto&quot;&gt;docs/plans/&lt;/code&gt; working notes that follow the distil-then-retire lifecycle, this
document is one of the &lt;strong&gt;standing domain throughlines&lt;/strong&gt; meant to persist across
releases. It is the index and the “why” for the doctrine/charter governance
surface; the release milestones and epics it references are the “what ships when.”
Where a release plan and this plan disagree on &lt;em&gt;scope of the domain&lt;/em&gt;, this plan is
the canonical map; where they disagree on &lt;em&gt;what ships in a given tag&lt;/em&gt;, the milestone
roadmap and the owning epic win. Keep this plan factual and current; do not let it
accrete release-scoped tracking that belongs in an epic.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;h2 id=&quot;addendum-2026-09-04--milestone-re-key--resolved-sub-areas-post-2026-08-23-reconciliation&quot;&gt;Addendum 2026-09-04 — milestone re-key + resolved sub-areas (post-2026-08-23 reconciliation)&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;This durable plan was last revised 2026-08-12, &lt;strong&gt;11 days before&lt;/strong&gt; the 2026-08-23
release-queue reconciliation; its milestone labels (§3 open-issue lists and the §5 table)
predate it, and several sub-areas have since closed out. Per this plan’s own status contract
— “where they disagree on &lt;em&gt;what ships in a given tag&lt;/em&gt;, the milestone roadmap and the owning
epic win” — the labels and closed items are corrected here from live GitHub state (queried
2026-09-04, &lt;code dir=&quot;auto&quot;&gt;GITHUB_TOKEN&lt;/code&gt; unset). The &lt;strong&gt;invariants and sub-areas (the durable “why”) are
unchanged&lt;/strong&gt;; only the release-scoped “what ships when” moved. See the roadmap’s
&lt;a href=&quot;/plans/3-2-x-milestone-roadmap/#addendum-2026-09-04--milestone-taxonomy-re-anchor-the-delayed-action-r&quot;&gt;2026-09-04 re-anchor&lt;/a&gt;
and the &lt;a href=&quot;/changelog/4.0.0/&quot;&gt;4.0.0 declaration&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Taxonomy change.&lt;/strong&gt; The &lt;strong&gt;3.3.x&lt;/strong&gt; milestone was &lt;strong&gt;retired&lt;/strong&gt; (closed 2026-08-23, never
shipped) and milestone #4 repurposed into &lt;strong&gt;Product backlog&lt;/strong&gt;. The in-text “3.3.x” labels in
§3 have been corrected in place (2026-09-30).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Milestones re-checked 2026-09-30.&lt;/strong&gt; Since 2026-09-14 the 4.x line uses three milestones:
&lt;strong&gt;4.0.0 release scope&lt;/strong&gt; (the GA gate), &lt;strong&gt;CLI 4.x stable&lt;/strong&gt; (stable 4.x after launch) and
&lt;strong&gt;4.x Work&lt;/strong&gt; (planned beyond the stabilization release); see the
&lt;a href=&quot;/plans/4-0-0-milestone-roadmap/&quot;&gt;4.0.0 Milestone Roadmap&lt;/a&gt;. Where this plan’s epics sit now:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#2519&lt;/strong&gt; (charter authoring &amp;#x26; lifecycle robustness, §3.1): open, on &lt;strong&gt;CLI 4.x stable&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2467 / #2468&lt;/strong&gt; (pack-split keystone, mission types as doctrine, §3.2): moved
2026-10-22 to the charter repository as spec-kitty-charter #145 and #148, under the
pack ecosystem epic spec-kitty-charter #142. &lt;strong&gt;#2539&lt;/strong&gt; keeps the execution-trust half
here, on &lt;strong&gt;4.x Work&lt;/strong&gt;; pack verifiability moved to spec-kitty-charter #143.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#645&lt;/strong&gt; (stable application API, §3.6): open, on &lt;strong&gt;4.x Work&lt;/strong&gt;. &lt;strong&gt;#3179&lt;/strong&gt; (doctrine/charter
public API surface): &lt;strong&gt;closed&lt;/strong&gt; 2026-09-26.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2216&lt;/strong&gt; (§3.2 governance tiers): closed 2026-10-22 as a duplicate of spec-kitty-charter
#55; spec-kitty-charter ADR-0012 (pack mutability policy) supersedes its design.
&lt;strong&gt;#2652&lt;/strong&gt; (§3.3): open, still in &lt;strong&gt;Product backlog&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Moves and splits from 2026-10-22 are recorded in the migration table on
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/2216#issuecomment-6339908453&quot;&gt;#2216&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;§3.5 (meta.json fail-closed read routing) is DONE — strike the whole sub-area’s open list.&lt;/strong&gt;
Epic &lt;strong&gt;#3259 is CLOSED&lt;/strong&gt;, and every child listed open — &lt;strong&gt;#3230 / #3229 / #3228 / #3240&lt;/strong&gt; —
&lt;strong&gt;CLOSED&lt;/strong&gt; (the children 2026-08-11). The §3.5 “Open issues” block and its four §5 table rows
are resolved; the invariant now holds as shipped state, not pending work.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Other resolved-but-unstruck items (verified 2026-09-04):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#3282 CLOSED&lt;/strong&gt; — the §3.1 load-bearing P0 (pointer-based charters lack mission-type
activations on upgrade) shipped under &lt;strong&gt;3.2.6&lt;/strong&gt; (the §5 table now shows it closed).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3176 CLOSED&lt;/strong&gt; — the §3.1 / §5 “last builder-unreachable site” P1 residual is discharged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3183 CLOSED&lt;/strong&gt; and &lt;strong&gt;#2657 CLOSED&lt;/strong&gt; — §3.3 lists both as open (#3183 the
activation-vs-loadability collision; #2657 the external blocker on #2659’s provisioned
default charter). #2652 and #3251 remain open (Product backlog).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2262 CLOSED&lt;/strong&gt; — referenced under §3.4 of the SaaS plan; noted here for cross-consistency.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Still-live gaps (unchanged by the reconciliation):&lt;/strong&gt; §4 gap 1 (doctrine content-QA has no
owning workstream — &lt;strong&gt;#3275&lt;/strong&gt; still P3/no-milestone/no-epic) and §4 gap 4 (activation
reachability R1/R2, unspecced and blast-radius-bearing) remain the domain’s largest
declared-vs-in-force gaps. The §5 table was revised in place on 2026-09-30 to show live
state.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;addendum-2026-10-12--charter-modular-extraction-is-now-ga-gating-and-targets-its-own-repository&quot;&gt;Addendum 2026-10-12 — charter modular extraction is now GA-gating, and targets its own repository&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;The October direction update (operator ruling; see the
&lt;a href=&quot;/plans/4-0-0-milestone-roadmap/&quot;&gt;4.0.0 Milestone Roadmap&lt;/a&gt; “Direction update (2026-10-12)”)
changes the release-scoped “what ships when” for this domain. The &lt;strong&gt;invariants below are
unchanged&lt;/strong&gt;; only the gating and the extraction target move.&lt;/em&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Superseded 2026-10-19 (operator ruling).&lt;/strong&gt; The charter does not move to its own
repository. 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 &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; stays in core until its post-GA rework. The
GA leg is a frozen seam and a green conformance corpus (epic #6099, re-scoped), 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;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Charter modular extraction is a GA gate leg.&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 &lt;strong&gt;independently-released external contract package in its own
repository&lt;/strong&gt;, consumed through its public surface (&lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt;), 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;, moving the ~129
&lt;code dir=&quot;auto&quot;&gt;specify_cli → charter&lt;/code&gt; imports onto that stable surface — is &lt;strong&gt;now GA-gating&lt;/strong&gt; (it had been
“after GA”). The §3.1/§3.6 sole-door and single-entry-point invariants are exactly what make
that extraction safe; this addendum changes when it must land, not the invariant. The
physical split (wheel/repository) is the sibling
&lt;a href=&quot;/plans/domains/packs-extraction-domain-plan/&quot;&gt;Packs Extraction plan&lt;/a&gt;’s §3.1; 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). 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;, ADR
&lt;a href=&quot;/adr/3.x/2026-04-25-1-shared-package-boundary/&quot;&gt;2026-04-25-1&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The API-as-consumer boundary is unchanged, and now named open-core.&lt;/strong&gt; §3.6 here owns the
doctrine/charter &lt;strong&gt;Python import surface&lt;/strong&gt; (#3179); the &lt;strong&gt;application/mission-data API&lt;/strong&gt;
the &lt;a href=&quot;/plans/domains/api-dashboard-domain-plan/&quot;&gt;API &amp;#x26; Dashboard plan&lt;/a&gt; owns is a &lt;em&gt;different&lt;/em&gt; surface and is
now framed as the &lt;strong&gt;open-core producer&lt;/strong&gt; API. Team Kitty (“Multiplayer Mode”) is its
&lt;strong&gt;consumer&lt;/strong&gt;, not part of this domain. The non-goal boundary in §1 and §6 stands.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;1-purpose--scope&quot;&gt;1. Purpose &amp;#x26; scope&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Purpose.&lt;/strong&gt; Give the doctrine/charter surface a single durable home that states the
&lt;em&gt;invariants&lt;/em&gt; the surface must hold, groups the domain’s lasting sub-areas, and points
at the epics, ADRs, and design notes that carry the design and the tracking. Before
this plan, doctrine/charter planning had no standalone throughline — it was implicit,
spread across the open-core delivery plan, the glossary overhaul program, and the
&lt;code dir=&quot;auto&quot;&gt;docs/plans/doctrine/&lt;/code&gt; design corpus (see §2). This plan makes the throughline
explicit and becomes the domain’s index. It is the &lt;strong&gt;second&lt;/strong&gt; domain throughline
(the SaaS &amp;#x26; Hosted Sync domain plan — retired 2026-09-06, Convergence #3881 — was first).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In scope — the governance substrate.&lt;/strong&gt; “Doctrine &amp;#x26; charter” here means the
governance layer and the seam through which it reaches the runtime:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The charter&lt;/strong&gt; as the project’s governance onboarding and the &lt;strong&gt;single door&lt;/strong&gt; to
provisioned assets — activation/deactivation, the plan/commit activation seam, the
cascade over DRG &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;refines&lt;/code&gt; edges, and reconciliation between
the activation ledgers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The doctrine library&lt;/strong&gt; — the artefact kinds (directive, tactic, styleguide,
toolguide, paradigm, procedure, agent_profile, mission_step_contract, glossary_pack),
their DRG (doctrine reference graph), and the layered &lt;code dir=&quot;auto&quot;&gt;built-in → org → project&lt;/code&gt;
resolution.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Doctrine/charter extensibility &amp;#x26; the pack ecosystem&lt;/strong&gt; — org/project packs, pack
dependencies, governance tiers, and the author-able surfaces customers extend.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activation-driven availability&lt;/strong&gt; — deriving what mission types (and artefacts) are
&lt;em&gt;available&lt;/em&gt; from the charter activation set, not from filesystem position.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Doctrine content quality&lt;/strong&gt; — whether the shipped artefact &lt;em&gt;content&lt;/em&gt; (not just its
wiring) is scoped, non-duplicated, and operationalised as it claims.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;meta.json fail-closed read routing&lt;/strong&gt; — the mission-identity/VCS-lock record read
through the canonical fail-closed loader, since it is doctrine-adjacent canonical
metadata that a corrupt read must never silently absorb.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The consumer-facing seam&lt;/strong&gt; — a stable public API/import surface for the doctrine &amp;#x26;
charter modules, and the &lt;code dir=&quot;auto&quot;&gt;runtime → charter → doctrine&lt;/code&gt; layering that keeps the
runtime from reaching doctrine directly.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Glossary-as-doctrine&lt;/strong&gt; — promoting canonical terminology to a first-order,
activatable &lt;code dir=&quot;auto&quot;&gt;GLOSSARY_PACK&lt;/code&gt; doctrine artefact with executable adherence gating.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Explicit non-goals.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Not the hosted product.&lt;/strong&gt; Sync, event-envelope integrity, consent/identity egress,
CLI↔hosted auth, and rollout gating were a &lt;em&gt;different domain&lt;/em&gt; — the
SaaS &amp;#x26; Hosted Sync domain plan (retired 2026-09-06, Convergence #3881; the surface
re-homed upstream). This plan does not
restate them. Charter &lt;em&gt;domain events&lt;/em&gt; (&lt;code dir=&quot;auto&quot;&gt;CharterCreated&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;CharterUpdated&lt;/code&gt;, #2520) are
named here where the charter lifecycle emits them, but the hosted consumer of those
events belongs to the SaaS domain. (Note the inverse miscategorisation the SaaS plan
flags: the open-core plan’s “SaaS” label is the open-core split of &lt;em&gt;this&lt;/em&gt; doctrine
layer, not the hosted product.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Not the wheel/packaging cutover as a build task.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;kernel → doctrine → charter&lt;/code&gt;
wheel split (#3101, ADR 2026-08-02-1) and the built-in pack extraction (#3091/#3022)
are a &lt;em&gt;packs-extraction&lt;/em&gt; concern — the sibling
&lt;a href=&quot;/plans/domains/packs-extraction-domain-plan/&quot;&gt;Packs Extraction throughline&lt;/a&gt;. This plan owns the
charter/doctrine &lt;em&gt;access boundary and public surface&lt;/em&gt; those cutovers depend on, and
cross-references the packaging track rather than owning it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Not release scheduling.&lt;/strong&gt; Which fix ships in which release is the milestone
roadmap’s and the epic’s job (§5).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Why a durable domain plan and not a release plan.&lt;/strong&gt; Doctrine/charter is a standing
set of invariants (the charter is the sole door to assets; activation means an agent
actually receives the artefact; availability derives from activation, not from disk;
a lower-tier pack cannot silently mutate a higher tier’s governed artefact; canonical
metadata fails closed). Those invariants outlive any one tag. Release plans churn as
milestones close; the invariants and their sub-areas do not. The issue tracker is
already unwieldy, so the throughline deliberately holds the &lt;em&gt;durable spine&lt;/em&gt; and
cross-references the release-scoped docs rather than duplicating their tables.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;2-where-doctrinecharter-planning-lives-today-honest-inventory&quot;&gt;2. Where doctrine/charter planning lives today (honest inventory)&lt;/h2&gt;
&lt;p&gt;There has been &lt;strong&gt;no standalone doctrine/charter throughline&lt;/strong&gt; before this document.
The planning was distributed across four surfaces, none of which is the domain’s index:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/3-2-x-open-core-delivery-plan.md&quot;&gt;3.2.x Open-Core Delivery Plan&lt;/a&gt;&lt;/strong&gt; (superseded,
prior cycle; the active release companion is the
&lt;a href=&quot;/plans/4-0-0-milestone-roadmap/&quot;&gt;4.0.0 Milestone Roadmap&lt;/a&gt;) — the closest
thing to a doctrine/charter strategy, but framed as a &lt;em&gt;release-window&lt;/em&gt; delivery plan,
not a durable domain map. Its organizing principle is the “last permitted
breaking-change window” for the doctrine/charter seam: charter-as-sole-door (its §1.1
/ §2.2 done-bar), the built-in → module extraction (§2.2 item 3), and the
Creed/Values schema build (§3 item 4). It carries the &lt;em&gt;what-ships-in-3.2.x&lt;/em&gt; framing;
it does not hold the domain’s standing invariants across versions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Glossary Doctrine Overhaul — Program Plan&lt;/strong&gt;
— a four-mission program promoting the glossary to a first-order &lt;code dir=&quot;auto&quot;&gt;GLOSSARY_PACK&lt;/code&gt;
doctrine kind and building the executable ASSET-kind gate. A program plan scoped to
one sub-area, not the domain.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;docs/plans/doctrine/&lt;/code&gt;&lt;/strong&gt; — the design/review corpus: the
charter-activation-vs-reachability assessment, the &lt;code dir=&quot;auto&quot;&gt;runtime → charter → doctrine&lt;/code&gt;
boundary audit, the charter-as-central-path-resolver gap analysis, the layered
resolution design, the doctrine-inclusion assessment, the FoundationalValues/Creed
AUTHORITY docs, and the next-doctrine-slice research (wheel / mission-type
relocation / public API). Rich, tiered (AUTHORITY / RECORD / EVIDENCE), but a
collection of investigations, not a single throughline.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The epics themselves&lt;/strong&gt; — #2519 (charter authoring &amp;#x26; lifecycle), #2466
(doctrine/charter extensibility &amp;#x26; pack ecosystem), #2652 (specify_cli/missions
retirement / activation-driven availability), #1799 (charter/doctrine governance
config &amp;#x26; docs), #2216 (governance tiers), #3259 (meta.json fail-closed routing),
and #645 (stable application API surface). These are issue-tracker groupings with
scope bullets — &lt;strong&gt;not written plans&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;This plan now becomes the domain’s index.&lt;/strong&gt; It does not replace the open-core plan,
the glossary program, the design corpus, or the epics — it ties them together under one
set of invariants and surfaces the gaps they collectively leave open (§4). Verify live
issue/epic 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.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;3-standing-concerns--the-durable-spine&quot;&gt;3. Standing concerns — the durable spine&lt;/h2&gt;
&lt;p&gt;The domain divides into seven lasting sub-areas. Each states the &lt;strong&gt;invariant&lt;/strong&gt; it must
hold (the durable “why”), then lists the &lt;strong&gt;currently open issues&lt;/strong&gt; grouped beneath it
(the release-scoped “what,” which will turn over across versions).&lt;/p&gt;
&lt;h3 id=&quot;31-charter-authoring-activation--lifecycle&quot;&gt;3.1 Charter authoring, activation &amp;#x26; lifecycle&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; The charter is the &lt;strong&gt;sole door&lt;/strong&gt; to provisioned doctrine assets: any
path that reaches an asset around the charter is a second seam that leaks internals.
The two activation ledgers (&lt;code dir=&quot;auto&quot;&gt;config.yaml activated_*&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;answers.yaml selected_*&lt;/code&gt;,
projecting into &lt;code dir=&quot;auto&quot;&gt;references.yaml&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt;) are &lt;strong&gt;reconciled by construction&lt;/strong&gt; — an
artefact is never activated-yet-dangling — and &lt;strong&gt;“activated” means an agent actually
receives the artefact&lt;/strong&gt; at the action-context boundary, not merely that it is a member
of a filter list. Charter lifecycle transitions emit their domain events on the unified
activation seam.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Design of record.&lt;/strong&gt; Epic &lt;strong&gt;#2519&lt;/strong&gt; (charter authoring &amp;#x26; lifecycle hardening — the
disjoint-ledgers root defect, deterministic intake, &lt;code dir=&quot;auto&quot;&gt;charter author&lt;/code&gt; scaffold, charter
domain events); the sole-door done-bar in the
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/3-2-x-open-core-delivery-plan.md&quot;&gt;Open-Core Delivery Plan §1.1/§2.2&lt;/a&gt;; ADR
&lt;a href=&quot;/adr/3.x/2026-05-16-1-doctrine-layer-merge-semantics/&quot;&gt;2026-05-16-1 doctrine-layer merge semantics&lt;/a&gt;
(plan/commit activation seam, cascade over DRG edges). The reasoning trail lives in two
now-archived design notes (both &lt;code dir=&quot;auto&quot;&gt;doc_status: deprecated&lt;/code&gt;, cited here as historical
provenance) — &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/charter-activation-reachability-assessment.md&quot;&gt;charter-activation-reachability-assessment&lt;/a&gt;
(the V1/V2/V3 activation-vocabulary split; 185 activated artefacts, zero surfaced at the
action boundary) and &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/runtime-charter-doctrine-boundary.md&quot;&gt;runtime-charter-doctrine-boundary&lt;/a&gt;
(the &lt;code dir=&quot;auto&quot;&gt;runtime → charter → doctrine&lt;/code&gt; layering ratchet); their findings are distilled into
this plan’s invariants and §4 gaps.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open issues.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#3282 (P0, → #2519; closed 2026-08-27)&lt;/strong&gt; — upgrade leaves pointer-based charters without
mission-type activations on 3.2.6. A direct lifecycle/reconciliation failure: the
activation state a charter should carry after upgrade is not derived. The load-bearing
P0 of this sub-area.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3176 (P1, → #2466; closed 2026-08-20)&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;build_activation_aware_doctrine_service&lt;/code&gt; cannot
reach &lt;code dir=&quot;auto&quot;&gt;.kittify/agent_profiles&lt;/code&gt;, blocking &lt;code dir=&quot;auto&quot;&gt;projection.py&lt;/code&gt;’s FR-001 migration onto the
unified builder. The last named, composite-key-excluded call site keeping the
sole-door from being one builder / one entry point (see the Open-Core §1.1 residual).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3261 (P3, Task, → #2519)&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;charter context --include&lt;/code&gt; silently mishandles
multi-selector input (comma errors; repeated flags drop all but the last) while the
help text implies comma-separation. A usability defect on the on-demand fetch path
that is the one activation vector that &lt;em&gt;does&lt;/em&gt; surface artefacts today.&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Standing sub-thread — activation reachability (unspecced, durable).&lt;/strong&gt; The
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/charter-activation-reachability-assessment.md&quot;&gt;reachability assessment&lt;/a&gt;’s (now archived) R1
(“make activation an entry vector into action context”) and R2 (“collapse the three
activation vocabularies to one”) are the difference between a doctrine layer that is
&lt;em&gt;declared&lt;/em&gt; and one that is &lt;em&gt;in force&lt;/em&gt;. They are blast-radius-bearing (they change what
every agent receives at every action boundary in every consumer project), have no
owning mission, and should be decided before the DRG edge-migration encodes the
ambiguity. Tracked here as a durable gap (see §4).&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&quot;32-doctrinecharter-extensibility--the-pack-ecosystem&quot;&gt;3.2 Doctrine/charter extensibility &amp;#x26; the pack ecosystem&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; Customers can define and refine their own doctrine as a coherent,
author-able &lt;strong&gt;pack ecosystem&lt;/strong&gt; — packs nest and declare dependencies, and the surfaces
customers most want to extend (assets, shortcodes, mission types) are first-class
doctrine kinds — &lt;strong&gt;without&lt;/strong&gt; a lower-tier pack being able to silently mutate a
higher-tier pack’s &lt;em&gt;governed&lt;/em&gt; artefact. Tier order is &lt;code dir=&quot;auto&quot;&gt;built-in → org → project&lt;/code&gt; (later
overlays earlier); immutability is a deliberate, opt-in pack-owner act
(&lt;code dir=&quot;auto&quot;&gt;AUTHORITATIVE&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;component-type&lt;/code&gt;), never implicit, and default behaviour stays
backward-compatible.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Design of record.&lt;/strong&gt; Epic &lt;strong&gt;#2466&lt;/strong&gt; (doctrine/charter extensibility &amp;#x26; pack ecosystem —
pack-split keystone #2467, mission-types-as-doctrine #2468, assets kind, shortcodes,
pack validator; verified-distribution #2539 deferred, now on 4.x Work); epic &lt;strong&gt;#2216&lt;/strong&gt;
(governance tiers — the owner-declared &lt;code dir=&quot;auto&quot;&gt;component-type&lt;/code&gt; immutability model folding in
the consumer-declared &lt;code dir=&quot;auto&quot;&gt;replaceable-builtins.yaml&lt;/code&gt; #2082) under parent epic &lt;strong&gt;#1799&lt;/strong&gt;
(charter/doctrine governance configuration &amp;#x26; docs); the pack/DRG merge semantics in ADR
&lt;a href=&quot;/adr/3.x/2026-05-16-1-doctrine-layer-merge-semantics/&quot;&gt;2026-05-16-1&lt;/a&gt;
(&lt;code dir=&quot;auto&quot;&gt;enhances&lt;/code&gt; = field-merge, &lt;code dir=&quot;auto&quot;&gt;overrides&lt;/code&gt; = full replacement, &lt;code dir=&quot;auto&quot;&gt;specializes_from&lt;/code&gt; lineage
as a DRG edge); and the &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/doctrine-inclusion-assessment.md&quot;&gt;doctrine-inclusion-assessment&lt;/a&gt;
(the three pillars — agent profiles, mission-type customization, ad-hoc composition —
and the compiler gap).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open issues.&lt;/strong&gt; Chiefly the #2466 children: &lt;strong&gt;#2467&lt;/strong&gt; (pack-split keystone — the
foundational schema change everything else builds on), &lt;strong&gt;#2468&lt;/strong&gt; (promote mission types +
step contracts to full doctrine kinds — sizing &lt;strong&gt;L&lt;/strong&gt;, carrying a &lt;em&gt;named&lt;/em&gt; “reverses a
tested no-silent-fallback contract” risk that requires its own decision record), the
assets-kind / shortcodes / pack-validator kinds (parallelisable once the keystone
lands), plus the #2216 governance-tier work. &lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt; is deliberately &lt;strong&gt;not&lt;/strong&gt; yet
an &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;MissionTypeNotAnArtifactKind&lt;/code&gt; is intentional); its promotion is #2468
territory and must &lt;strong&gt;not&lt;/strong&gt; land as a quiet behaviour change.&lt;/p&gt;
&lt;h3 id=&quot;33-activation-driven-availability--the-single-canonical-mission-type-source&quot;&gt;3.3 Activation-driven availability &amp;#x26; the single canonical mission-type source&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; What mission types (and artefacts) are &lt;em&gt;available&lt;/em&gt; is derived from the
&lt;strong&gt;charter activation set&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;activated_mission_types&lt;/code&gt;), &lt;strong&gt;not&lt;/strong&gt; from filesystem
position — a mission type present on disk but not charter-activated is neither offered
by &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt;/enumeration nor resolvable as a template. There is &lt;strong&gt;one&lt;/strong&gt; canonical
mission-type source and &lt;strong&gt;no second availability source&lt;/strong&gt;: the derived
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&lt;/code&gt; tree is retired so &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; is an ordinary peer
doctrine type that cannot be inherited by default.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Design of record.&lt;/strong&gt; Epic &lt;strong&gt;#2652&lt;/strong&gt; (specify_cli/missions retirement — slice 2+;
sequenced #2658 template-slot → #2659 activation-driven enumeration → #2660 remove the
&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;-less fallback → #2661 delete the doctrine→&lt;code dir=&quot;auto&quot;&gt;.kittify&lt;/code&gt; copy step) and its AC
(“availability is charter-activation-driven, not filesystem-driven”); the provisioned
default-charter revision (#2657, under #461) that retires “all built-in doctrine” as the
implicit default; and the interlock analysis in the now-archived
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/next-slice-wheel-mission-types-public-api-research.md&quot;&gt;next-slice-wheel-mission-types-public-api-research&lt;/a&gt;
note &lt;em&gt;(deprecated — historical record)&lt;/em&gt; (how #3091 / #2468 / #2652 converge on the same
end state via three independently sequenced efforts).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open issues.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#3251 (no milestone, → #2652)&lt;/strong&gt; — the &lt;code dir=&quot;auto&quot;&gt;rc35_activate_builtin_mission_types&lt;/code&gt; upgrade
migration seeds from a disk-scan roster rather than the authored &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt;; the
two agree today (both four) but &lt;strong&gt;drift&lt;/strong&gt; the moment a fifth built-in type is added.
A concrete “second seed authority” leak against this invariant — repoint to the shared
&lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt; helper or add a sync guard.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3183 (→ #2652)&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;UnknownMissionTypeError&lt;/code&gt; conflates “activated in config” with
“has a loadable profile” — the exact activation-vs-availability vocabulary collision
this sub-area exists to close; a relocation slice should resolve it, not inherit it.&lt;/li&gt;
&lt;li&gt;The #2652 sub-issue chain itself (#2658 → #2659 → #2660 → #2661), with #2659 blocked
externally on #2657 (provisioned default charter).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;34-doctrine-content-quality&quot;&gt;3.4 Doctrine content quality&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; Shipped doctrine artefact &lt;strong&gt;content&lt;/strong&gt; — not just its wiring — is
correctly scoped, non-duplicated, and operationalised as it claims: a directive whose
title promises multi-ecosystem coverage does not silently operationalise only one
ecosystem, and a tactic is not duplicated across artefacts. Content is subject to the
same “resolves means reachable, not just present” honesty the activation surface demands.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Design of record.&lt;/strong&gt; &lt;em&gt;None as an owning workstream&lt;/em&gt; — this is the domain’s content-QA
gap (see §4). The nearest guardrails are the terminology enforcement in the
glossary program (canonical-term casing, banned
synonyms) and the reachability-metric discipline recorded in the now-archived
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/charter-activation-reachability-assessment.md&quot;&gt;reachability assessment §5&lt;/a&gt; &lt;em&gt;(deprecated)&lt;/em&gt;
(measure reachability, not incidence) — both wiring/terminology gates, neither a
content-scoping review.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open issues.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#3275 (P3, no milestone, no owning epic)&lt;/strong&gt; — the supply-chain security directive is
operationalised JS/TS-only while its scope claims multi-ecosystem coverage, with tactic
duplication. The concrete instance of content drift, currently unowned and unmilestoned;
§4 flags the missing workstream it exposes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;35-metajson-fail-closed-read-routing&quot;&gt;3.5 meta.json fail-closed read routing&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is the mission’s canonical identity and VCS-lock record.
&lt;strong&gt;Every read flows through the fail-closed loader&lt;/strong&gt; (or a shared L1 pure-decode
primitive, &lt;code dir=&quot;auto&quot;&gt;text|bytes → dict|None&lt;/code&gt;); a corrupt, truncated, or wrong-authority file
&lt;strong&gt;fails loud&lt;/strong&gt; rather than being silently absorbed by an ad-hoc &lt;code dir=&quot;auto&quot;&gt;json.loads&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;git show&lt;/code&gt;
stdout / &lt;code dir=&quot;auto&quot;&gt;show_blob&lt;/code&gt; bytes read. The inline-meta-read architectural gate reaches
&lt;strong&gt;0 un-routed / 0 un-allowlisted&lt;/strong&gt; bypass reads, with the routed floor re-derived from a
live count. This is the doctrine-adjacent facet of the metadata-authority discipline:
the split-brain / wrong-authority failure mode the epic exists to close.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Design of record.&lt;/strong&gt; Epic &lt;strong&gt;#3259&lt;/strong&gt; (finish routing the residual &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; bypass
reads onto the canonical seam), continuing the &lt;code dir=&quot;auto&quot;&gt;meta-fail-closed-3162&lt;/code&gt; mission that
routed one of five bypass sites; the active
&lt;code dir=&quot;auto&quot;&gt;meta-json-fail-closed-routing-01KZPJ1F&lt;/code&gt; mission in this tree.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open issues.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#3230 (→ #3259)&lt;/strong&gt; — route the 4 remaining &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; bypass reads (deferred on
routed budget + missing L1 tier, not on structure).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3229 (→ #3259)&lt;/strong&gt; — add the L1 pure-decode primitive (&lt;code dir=&quot;auto&quot;&gt;text|bytes → dict|None&lt;/code&gt;) so
the two blob-fed bypass parsers can route. The enabling seam #3230 waits on.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3228 (→ #3259)&lt;/strong&gt; — the VCS-lock-only comparison is duplicated (2 declarations, 2
non-equivalent comparators); collapse to one comparator.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3240 (→ #3259)&lt;/strong&gt; — the &lt;code dir=&quot;auto&quot;&gt;inline_meta_read&lt;/code&gt; allow-list is absent from
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/_baselines.yaml&lt;/code&gt;; register it or record the deviation (open
operator call) so the gate’s floor is auditable.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;36-stable-public-api-surface-for-doctrine--charter&quot;&gt;3.6 Stable public API surface for doctrine &amp;#x26; charter&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; External consumers of the doctrine &amp;#x26; charter modules bind to &lt;strong&gt;one
documented, versioned public surface&lt;/strong&gt;, not to deep internal submodule imports — the
single-entry-point invariant is enforced by an architectural test so it cannot silently
regress. This is the &lt;code dir=&quot;auto&quot;&gt;runtime → charter → doctrine&lt;/code&gt; layering seen from outside: the
runtime (and any future SDK/MCP adapter) reaches doctrine &lt;strong&gt;through&lt;/strong&gt; the charter proxy,
never directly.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Design of record.&lt;/strong&gt; Design-spike &lt;strong&gt;#3179&lt;/strong&gt; (“create a stable public API surface for
doctrine &amp;#x26; charter modules”), which explicitly transfers the &lt;strong&gt;#645/#460 pattern&lt;/strong&gt; —
service extraction → formalized typed contracts → architectural test enforcing the
single-entry-point invariant → &lt;em&gt;then&lt;/em&gt; a transport/framework choice, sequenced last. The
verified surface gap: &lt;code dir=&quot;auto&quot;&gt;doctrine/__init__.py&lt;/code&gt; declares 3 public names while &lt;strong&gt;79 files
reach past it across ~30 distinct submodule paths&lt;/strong&gt;, with no architectural test pinning
“use the public surface.” The now-archived &lt;code dir=&quot;auto&quot;&gt;runtime → charter → doctrine&lt;/code&gt; boundary audit
(&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/runtime-charter-doctrine-boundary.md&quot;&gt;runtime-charter-doctrine-boundary&lt;/a&gt;, &lt;em&gt;deprecated&lt;/em&gt;) is
the internal half of the same invariant; the now-archived
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/next-slice-wheel-mission-types-public-api-research.md&quot;&gt;next-slice research §(c)&lt;/a&gt; &lt;em&gt;(deprecated)&lt;/em&gt;
established that this public surface is a &lt;strong&gt;precondition&lt;/strong&gt; for a credible wheel-cutover
external contract, not a parallel effort.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open issues.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#3179 (P2, closed 2026-09-26; parented under #645)&lt;/strong&gt; — the public-API thread. Its
own body cites the #645/#460 precedent (Refs #3101, #645, #460, #2787, #3176); the
next-slice research recorded it as parented under #2466. §4 recommends the plan text
reconcile its epic home to &lt;strong&gt;#645&lt;/strong&gt; (Epic: Stable Application API Surface), whose
single-entry-point-invariant pattern it is a direct instance of.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2787&lt;/strong&gt; — the existing precedent for a &lt;em&gt;frozen&lt;/em&gt; charter contract (&lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt; as an activation-scoped external contract with &lt;code dir=&quot;auto&quot;&gt;context_schema_version&lt;/code&gt;) —
the one place this project has already frozen a stable contract, scoped to a single
CLI JSON payload rather than the importable Python surface.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;37-glossary-as-doctrine&quot;&gt;3.7 Glossary-as-doctrine&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; Canonical terminology is a &lt;strong&gt;first-order, activatable doctrine
artefact&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;ArtifactKind.GLOSSARY_PACK&lt;/code&gt;) shipping definitions, aliases, and banned
synonyms as a distributable pack — and terminology adherence is enforced by &lt;strong&gt;shipped
executable code&lt;/strong&gt; (the ASSET-kind gate) consuming that pack, not by hardcoded in-repo
Python tests. The dead runtime glossary pipeline is retired without losing its two live
authorities (the 104 curated canonical definitions and the CI casing gate). The
executable-ASSET primitive it introduces is what lets other repo-specific enforcement
move out of the shared runtime into doctrine.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Design of record.&lt;/strong&gt; The
Glossary Doctrine Overhaul — Program Plan — four
sequenced missions &lt;strong&gt;A&lt;/strong&gt; (glossary-pack kind keystone, #1418) → &lt;strong&gt;D&lt;/strong&gt; (executable
ASSET-kind gate, #2599/#2535, phased built-in-only trust model) → &lt;strong&gt;B&lt;/strong&gt; (enforcement +
cleanup, #2822/#2830/#2823) → &lt;strong&gt;C&lt;/strong&gt; (retire the runtime glossary, #2727) — and its
correctness traps (URN must be &lt;code dir=&quot;auto&quot;&gt;glossary_pack:&lt;/code&gt; underscore; the silent-invisibility
guard; &lt;code dir=&quot;auto&quot;&gt;GLOSSARY_PACK&lt;/code&gt; joins the charter-activatable universe, not the &lt;code dir=&quot;auto&quot;&gt;{template, asset}&lt;/code&gt; exclusion set; three mirrored kind-lists move in lockstep).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open issues.&lt;/strong&gt; The program’s own ticket set — #1418, #2599 (epic #2535), #2822, #2830, #2823, #2727
(all pre-spec at the program’s last pass). This sub-area is at
program-planning maturity (&lt;code dir=&quot;auto&quot;&gt;doc_status: draft&lt;/code&gt;), ahead of its per-mission specs.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;4-known-gaps&quot;&gt;4. Known gaps&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Doctrine content-QA has no owning workstream.&lt;/strong&gt; #3275 (supply-chain directive
operationalised JS/TS-only vs its multi-ecosystem scope claim; tactic duplication)
is a concrete content-scoping defect, but it is a lone &lt;strong&gt;P3, no-milestone, no-epic&lt;/strong&gt;
issue. The domain’s guardrails all target &lt;em&gt;wiring&lt;/em&gt; (activation reachability) or
&lt;em&gt;terminology&lt;/em&gt; (glossary casing/banned-synonyms) — nothing owns &lt;em&gt;content scoping /
non-duplication / operationalisation-matches-claim&lt;/em&gt; as a coherent workstream. §3.4 is
the invariant; there is no epic behind it. Recommend either parenting #3275 (and its
class) under a content-QA epic, or explicitly folding a content-scoping gate into the
glossary program’s ASSET-gate rail (mission B) so shipped content is reviewed the way
its wiring now is.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3179 epic-home discrepancy.&lt;/strong&gt; The now-archived
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/next-slice-wheel-mission-types-public-api-research.md&quot;&gt;next-slice research §(c)&lt;/a&gt; &lt;em&gt;(deprecated)&lt;/em&gt;
recorded #3179 as filed &lt;strong&gt;parented under #2466&lt;/strong&gt; (extensibility &amp;#x26; pack ecosystem),
while the issue itself is framed entirely on the &lt;strong&gt;#645/#460&lt;/strong&gt; stable-application-API
pattern (its Refs list is #3101, #645, #460, #2787, #3176) and the triage parents it
to &lt;strong&gt;#645&lt;/strong&gt;. These are different epics. Recommend the plan text and the tracker
reconcile to &lt;strong&gt;#645&lt;/strong&gt; — #3179 is a direct instance of #645’s single-entry-point
invariant, not of the pack ecosystem — and that §3.6 / §5 be the reconciling view
until the tracker parent is corrected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter-sole-door residual doors are tracked in two places.&lt;/strong&gt; The residual bypass
inventory lives in &lt;strong&gt;both&lt;/strong&gt; the &lt;a href=&quot;/plans/doctrine/charter-sole-door-deferred-issues/&quot;&gt;charter-sole-door-deferred-issues&lt;/a&gt;
record (six deferred issues: #2986, #3036, #3039, #3091, #3022, #3101) &lt;strong&gt;and&lt;/strong&gt; the
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/3-2-x-open-core-delivery-plan.md&quot;&gt;Open-Core Delivery Plan §1.1&lt;/a&gt; residual list
(&lt;code dir=&quot;auto&quot;&gt;resolve_template_by_id&lt;/code&gt;’s 5 importers, &lt;code dir=&quot;auto&quot;&gt;runtime/resolver.py&lt;/code&gt;’s tier-1–4
reimplementation, &lt;code dir=&quot;auto&quot;&gt;runtime/home.py&lt;/code&gt;’s importlib-resources root, three missions-root
duplicates, the escalated #3176 site, sequenced as #3176/#3091/#3022/#3101). The two
overlap but neither is the canonical ledger. Recommend one canonical residual-door
ledger (this §3.1 + the deferred-issues doc as its citable summary) so a reader is not
left to diff two lists to learn what the sole-door still leaks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activation reachability (R1/R2) is unspecced and durable.&lt;/strong&gt; Per the now-archived
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/charter-activation-reachability-assessment.md&quot;&gt;reachability assessment&lt;/a&gt; &lt;em&gt;(deprecated)&lt;/em&gt;, 185
charter-activated artefacts surface &lt;strong&gt;zero&lt;/strong&gt; at the action-context boundary because
activation is operationalised as &lt;em&gt;filter membership&lt;/em&gt; (V1) while the boundary renders
from the &lt;em&gt;interview-answer&lt;/em&gt; vocabulary (V2/V3). R1 (activation as an entry vector into
action context) and R2 (collapse the three vocabularies to one, an ADR-level change)
have no owning mission and are blast-radius-bearing across every consumer project.
This is the domain’s largest &lt;em&gt;declared-vs-in-force&lt;/em&gt; gap and should be specced before
the DRG edge-migration encodes the vocabulary ambiguity.&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h2 id=&quot;5-release-scoped-view-the-what-ships-when&quot;&gt;5. Release-scoped view (the “what ships when”)&lt;/h2&gt;
&lt;p&gt;This plan tracks the &lt;strong&gt;why&lt;/strong&gt; (invariants and sub-areas); the epic tracks the
&lt;strong&gt;what-ships-when&lt;/strong&gt;. The table below is a snapshot for orientation, not a schedule. It
will turn over as milestones close. Verify live state via
&lt;code dir=&quot;auto&quot;&gt;gh issue view &amp;#x3C;n&gt; --repo spec-kitty/spec-kitty&lt;/code&gt; before acting.&lt;/p&gt;





















































































































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Issue&lt;/th&gt;&lt;th&gt;Pri&lt;/th&gt;&lt;th&gt;Sub-area (§3)&lt;/th&gt;&lt;th&gt;State (2026-09-30)&lt;/th&gt;&lt;th&gt;Owning epic&lt;/th&gt;&lt;th&gt;Notes&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;#3282&lt;/td&gt;&lt;td&gt;P0&lt;/td&gt;&lt;td&gt;Charter lifecycle (3.1)&lt;/td&gt;&lt;td&gt;Closed 2026-08-27 (shipped in 3.2.6)&lt;/td&gt;&lt;td&gt;#2519&lt;/td&gt;&lt;td&gt;Pointer-based charters lack mission-type activations on upgrade&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#3176&lt;/td&gt;&lt;td&gt;P1&lt;/td&gt;&lt;td&gt;Charter lifecycle / sole-door (3.1)&lt;/td&gt;&lt;td&gt;Closed 2026-08-20&lt;/td&gt;&lt;td&gt;#2466&lt;/td&gt;&lt;td&gt;Last builder-unreachable &lt;code dir=&quot;auto&quot;&gt;.kittify/agent_profiles&lt;/code&gt; site blocking &lt;code dir=&quot;auto&quot;&gt;projection.py&lt;/code&gt; FR-001&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#3261&lt;/td&gt;&lt;td&gt;P3&lt;/td&gt;&lt;td&gt;Charter lifecycle (3.1)&lt;/td&gt;&lt;td&gt;Open, Product backlog&lt;/td&gt;&lt;td&gt;#2519&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter context --include&lt;/code&gt; multi-selector mishandling&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#2467&lt;/td&gt;&lt;td&gt;P2&lt;/td&gt;&lt;td&gt;Extensibility (3.2)&lt;/td&gt;&lt;td&gt;Open, 4.x Work&lt;/td&gt;&lt;td&gt;#2466&lt;/td&gt;&lt;td&gt;Pack-split keystone — foundational schema everything builds on&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#2468&lt;/td&gt;&lt;td&gt;P2&lt;/td&gt;&lt;td&gt;Extensibility (3.2)&lt;/td&gt;&lt;td&gt;Open, 4.x Work&lt;/td&gt;&lt;td&gt;#2466&lt;/td&gt;&lt;td&gt;Mission-types-as-doctrine (sizing L); reverses a tested no-silent-fallback contract — needs a decision record&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#2216&lt;/td&gt;&lt;td&gt;P2&lt;/td&gt;&lt;td&gt;Extensibility / gov tiers (3.2)&lt;/td&gt;&lt;td&gt;Open, Product backlog&lt;/td&gt;&lt;td&gt;#2466&lt;/td&gt;&lt;td&gt;Owner-declared &lt;code dir=&quot;auto&quot;&gt;component-type&lt;/code&gt; immutability, folds in #2082&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#3251&lt;/td&gt;&lt;td&gt;P3&lt;/td&gt;&lt;td&gt;Activation-driven availability (3.3)&lt;/td&gt;&lt;td&gt;Open, Product backlog&lt;/td&gt;&lt;td&gt;#2652&lt;/td&gt;&lt;td&gt;rc35 migration seeds from disk-scan, not &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt; — second-authority drift&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#3183&lt;/td&gt;&lt;td&gt;P2&lt;/td&gt;&lt;td&gt;Activation-driven availability (3.3)&lt;/td&gt;&lt;td&gt;Closed 2026-08-05&lt;/td&gt;&lt;td&gt;#2652&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;UnknownMissionTypeError&lt;/code&gt; conflates activation with loadability&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#3275&lt;/td&gt;&lt;td&gt;P3&lt;/td&gt;&lt;td&gt;Doctrine content quality (3.4)&lt;/td&gt;&lt;td&gt;Open, Product backlog&lt;/td&gt;&lt;td&gt;#2466 &lt;em&gt;(assigned since; see §4)&lt;/em&gt;&lt;/td&gt;&lt;td&gt;Supply-chain directive JS/TS-only vs multi-ecosystem scope; tactic duplication&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#3230 / #3229 / #3228 / #3240&lt;/td&gt;&lt;td&gt;—&lt;/td&gt;&lt;td&gt;meta.json fail-closed (3.5)&lt;/td&gt;&lt;td&gt;Closed 2026-08-11 (per the 2026-09-04 addendum)&lt;/td&gt;&lt;td&gt;#3259&lt;/td&gt;&lt;td&gt;Residual bypass reads, pure-decode primitive, VCS-lock comparator, allow-list registration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#3179&lt;/td&gt;&lt;td&gt;P2&lt;/td&gt;&lt;td&gt;Public API surface (3.6)&lt;/td&gt;&lt;td&gt;Closed 2026-09-26&lt;/td&gt;&lt;td&gt;#645&lt;/td&gt;&lt;td&gt;Stable public surface; #645/#460 pattern&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#1418&lt;/td&gt;&lt;td&gt;P1&lt;/td&gt;&lt;td&gt;Glossary-as-doctrine (3.7)&lt;/td&gt;&lt;td&gt;Closed 2026-07-22 (PR #2852)&lt;/td&gt;&lt;td&gt;(glossary program)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;GLOSSARY_PACK&lt;/code&gt; keystone; program mission A&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;#2599&lt;/td&gt;&lt;td&gt;P2&lt;/td&gt;&lt;td&gt;Glossary-as-doctrine (3.7)&lt;/td&gt;&lt;td&gt;Open, Product backlog&lt;/td&gt;&lt;td&gt;#2535&lt;/td&gt;&lt;td&gt;Executable ASSET-kind gate; program mission D&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;em&gt;Read the WHY in §3; the epic tracks the WHAT-ships-when. “Product backlog” means validated
but on no committed release. #3275 has since been parented under #2466, but the §4
content-QA gap (no owning workstream) stands.&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;6-cross-references&quot;&gt;6. Cross-references&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Sibling domain throughlines (the durable spine of &lt;code dir=&quot;auto&quot;&gt;docs/plans/&lt;/code&gt;):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Team Kitty / hosted collaboration&lt;/strong&gt; — the former SaaS &amp;#x26; hosted sync domain plan was
retired 2026-09-06 (Convergence #3881; surface re-homed upstream, see
&lt;a href=&quot;/context/team-kitty/&quot;&gt;Team Kitty context&lt;/a&gt;). It remains the &lt;strong&gt;non-goal boundary&lt;/strong&gt;
for this plan (§1): consent/identity egress, auth and rollout gating are not this domain.
The planned crossing thread, charter domain events (#2520), was closed as not planned when
the sync transport was removed; no charter event is emitted today.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Packs extraction&lt;/strong&gt; — &lt;a href=&quot;/plans/domains/packs-extraction-domain-plan/&quot;&gt;Packs Extraction — Domain Plan&lt;/a&gt;
(its &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&lt;/code&gt; premise has since changed; see its status banner). Owns the
&lt;code dir=&quot;auto&quot;&gt;kernel → doctrine → charter&lt;/code&gt; wheel cutover (#3101, ADR 2026-08-02-1, Option B,
no-partial) and the built-in pack extraction (#3091 missions/ relocation, #3022
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-packs-open&lt;/code&gt;). This plan owns the access boundary and public surface (§3.6)
those cutovers depend on.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Release-scoped doctrine/charter docs (the “what ships”):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/plans/4-0-0-milestone-roadmap/&quot;&gt;4.0.0 Milestone Roadmap&lt;/a&gt; — the active-cycle release
companion.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/3-2-x-open-core-delivery-plan.md&quot;&gt;3.2.x Open-Core Delivery Plan&lt;/a&gt; — &lt;em&gt;superseded, prior
cycle.&lt;/em&gt; The release-window
delivery strategy: charter-as-sole-door done-bar (§1.1/§2.2), built-in → module
extraction (§2.2), Creed/Values schema (§3 item 4). The &lt;code dir=&quot;auto&quot;&gt;what-ships-in-3.2.x&lt;/code&gt; view of
§3.1/§3.2 here.&lt;/li&gt;
&lt;li&gt;Glossary Doctrine Overhaul — Program Plan —
the §3.7 program in detail (missions A/D/B/C; #1418/#2599/#2822/#2830/#2823/#2727).&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/plans/doctrine/charter-sole-door-deferred-issues/&quot;&gt;Charter as Sole Door: Deferred Issues Record&lt;/a&gt; —
the citable residual-door summary for §3.1 (six deferred follow-ons).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Doctrine design corpus&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;docs/plans/doctrine/&lt;/code&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/charter-path-resolution-gaps.md&quot;&gt;Charter as Central Path Resolver — Gap Analysis&lt;/a&gt;, &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/doctrine-inclusion-assessment.md&quot;&gt;Doctrine Inclusion Assessment&lt;/a&gt;, &lt;a href=&quot;/plans/doctrine/layered-doctrine-resolution-design/&quot;&gt;Layered Doctrine Resolution — Design Blueprint&lt;/a&gt;, and the FoundationalValues/Creed AUTHORITY docs — background design for §3.1/§3.2.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Archived design notes (retired — cited above as historical provenance, not live design authority).&lt;/strong&gt;
These three &lt;code dir=&quot;auto&quot;&gt;docs/plans/doctrine/&lt;/code&gt; investigations have been distilled into the invariants and gaps above and flipped to &lt;code dir=&quot;auto&quot;&gt;doc_status: deprecated&lt;/code&gt;; the durable throughline no longer treats them as its live design corpus. They are retained for lineage — read them for the reasoning trail, not for current state:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/charter-activation-reachability-assessment.md&quot;&gt;Charter Activation vs DRG Reachability&lt;/a&gt; &lt;em&gt;(deprecated)&lt;/em&gt; — the V1/V2/V3 split and R1–R5, distilled into §3.1 and §4 gap 4.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/runtime-charter-doctrine-boundary.md&quot;&gt;Runtime → Charter → Doctrine — boundary audit&lt;/a&gt; &lt;em&gt;(deprecated)&lt;/em&gt; — the layering ratchet, distilled into §3.6.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/next-slice-wheel-mission-types-public-api-research.md&quot;&gt;Next doctrine slice — wheel / mission-types / public API research&lt;/a&gt; &lt;em&gt;(deprecated)&lt;/em&gt; — the (a)/(b)/(c) interlock, distilled into §3.3, §3.6, and §4 gap 2.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Doctrine/charter ADRs (design of record):&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/adr/3.x/2026-05-16-1-doctrine-layer-merge-semantics/&quot;&gt;2026-05-16-1 doctrine-layer merge semantics&lt;/a&gt; — activation plan/commit seam, cascade, DRG merge verbs (§3.1, §3.2).&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/3.x/2026-08-02-1-charter-wheel-assessment/&quot;&gt;2026-08-02-1 charter-wheel assessment&lt;/a&gt; — the deferred &lt;code dir=&quot;auto&quot;&gt;kernel → doctrine → charter&lt;/code&gt; cutover (packs-extraction sibling; §3.6 precondition).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Epics:&lt;/strong&gt; #2519 (charter authoring &amp;#x26; lifecycle), #2466 (extensibility &amp;#x26; pack ecosystem), #2652
(specify_cli/missions retirement / activation-driven availability), #1799
(governance configuration &amp;#x26; docs), #2216 (governance tiers), #3259 (meta.json fail-closed
routing), #645 (stable application API surface).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Plans index:&lt;/strong&gt; &lt;a href=&quot;/plans/&quot;&gt;docs/plans/index.md&lt;/a&gt;.&lt;/p&gt;</content>
</entry>
