<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/plans/domains/packs-extraction-domain-plan/">
  <id>https://docs.spec-kitty.ai/plans/domains/packs-extraction-domain-plan/</id>
  <title>Packs Extraction — Domain Plan</title>
  <updated>2026-10-19T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/plans/domains/packs-extraction-domain-plan/"/>
  <summary>Durable domain plan for re-extracting the doctrine layer from src/charter/offering/ and packs/built-in/ into separately released units: invariants, sub-areas, open epics.</summary>
  <content type="html">&lt;span id=&quot;packs-extraction--domain-plan&quot;&gt;&lt;/span&gt;
&lt;p&gt;&lt;strong&gt;Audience:&lt;/strong&gt; maintainers deciding what to build next in the doctrine layer’s
packaging.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Restated 2026-09-30 (#5428).&lt;/strong&gt; The first version of this plan (2026-08-12) was
written against a &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&lt;/code&gt; package that no longer exists. It described a buildable
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-doctrine&lt;/code&gt; wheel and a charter↔doctrine import cycle. Both are gone:
the package was absorbed into &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/&lt;/code&gt;, and the dormant wheel
groundwork was deleted. This version restates the extraction as a &lt;strong&gt;re-extraction&lt;/strong&gt; from
today’s tree. The earlier text is in git history. It is also linked from 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;archived 3.2.x Open-Core Delivery Plan&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is a &lt;strong&gt;standing domain throughline&lt;/strong&gt;. It holds the invariants the extraction must
keep, whatever release ships each step. The epics and the milestone roadmap decide
&lt;em&gt;what ships when&lt;/em&gt;. Where the two disagree on what ships in a tag, the epic wins.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;1-scope&quot;&gt;1. Scope&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;In scope: the physical split.&lt;/strong&gt; This plan covers moving doctrine code and doctrine
content across a package, wheel or repository boundary:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Code.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; subtree (or all of &lt;code dir=&quot;auto&quot;&gt;src/charter/&lt;/code&gt;) is released as its
own externally-versioned unit — &lt;strong&gt;its own repository&lt;/strong&gt;, consumed through
&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; (#3101). &lt;strong&gt;Direction
update 2026-10-12: this is now GA-gating&lt;/strong&gt; — its precondition #645 (move the ~129
&lt;code dir=&quot;auto&quot;&gt;specify_cli → charter&lt;/code&gt; imports onto the stable API) is a GA gate leg (see the
&lt;a href=&quot;/plans/4-0-0-milestone-roadmap/&quot;&gt;4.0.0 roadmap&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:&lt;/strong&gt; the charter code is not extracted to its own repository; see the
note under &lt;em&gt;Open work&lt;/em&gt; below.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Content.&lt;/strong&gt; Doctrine content for &lt;strong&gt;both&lt;/strong&gt; pack tiers is authored in &lt;code dir=&quot;auto&quot;&gt;spec-kitty-open-packs&lt;/code&gt;
and pinned to a commit in &lt;code dir=&quot;auto&quot;&gt;packs/&amp;#x3C;pack&gt;.source.yaml&lt;/code&gt;, then fetched by &lt;code dir=&quot;auto&quot;&gt;make sync-packs&lt;/code&gt; and the wheel build hook: &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; (#3504, #6451) and, as of the
2026-10-12 direction update, &lt;code dir=&quot;auto&quot;&gt;packs/internal/&lt;/code&gt; as well — a &lt;strong&gt;source-location move only&lt;/strong&gt;. A
later step may fetch built-in content at runtime (#3022). The packaging invariants are
unchanged (§3.2).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Distribution integrity.&lt;/strong&gt; Pinned, checksummed and verifiable pack distribution
(#2539, on 4.x Work).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Out of scope: authoring and governance.&lt;/strong&gt; Pack tiers (&lt;code dir=&quot;auto&quot;&gt;built-in → org → project&lt;/code&gt;),
DRG merge semantics (&lt;code dir=&quot;auto&quot;&gt;enhances&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;overrides&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;specializes_from&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;component-type&lt;/code&gt;
immutability belong to the
&lt;a href=&quot;/plans/domains/doctrine-charter-domain-plan/&quot;&gt;Doctrine &amp;#x26; Charter Domain Plan §3.2&lt;/a&gt;. That plan owns
&lt;em&gt;how packs are authored and layered&lt;/em&gt;. This plan owns &lt;em&gt;where the code and content live and
how they ship&lt;/em&gt;. When a packaging change alters an authoring guarantee, link the two plans
rather than restating either one.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;2-where-things-stand-checked-2026-09-30&quot;&gt;2. Where things stand (checked 2026-09-30)&lt;/h2&gt;









































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Fact&lt;/th&gt;&lt;th&gt;Evidence&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Doctrine code lives in &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;src/doctrine.py&lt;/code&gt; is only a deprecation shim.&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;[tool.hatch.build.targets.wheel]&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; imports nothing outside itself and &lt;code dir=&quot;auto&quot;&gt;kernel&lt;/code&gt;, so the import cycle the first plan called “the blocker” no longer exists.&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;grep&lt;/code&gt; of &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/**/*.py&lt;/code&gt; imports&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;The enforced module chain is &lt;code dir=&quot;auto&quot;&gt;kernel &amp;#x3C;- charter &amp;#x3C;- {glossary, runtime, mission_runtime} &amp;#x3C;- specify_cli&lt;/code&gt;.&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_layer_rules.py&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;The public import surface is curated in &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/api.py&lt;/code&gt;. That was #3179, the wheel’s own precondition.&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_doctrine_public_surface.py&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;The dormant &lt;code dir=&quot;auto&quot;&gt;spec-kitty-doctrine&lt;/code&gt; wheel groundwork was &lt;strong&gt;deleted&lt;/strong&gt;, not kept. No doctrine wheel has ever been built or shipped.&lt;/td&gt;&lt;td&gt;mission &lt;code dir=&quot;auto&quot;&gt;charter-code-topology-01M152G1&lt;/code&gt;; comment in &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Built-in content lives at the repository root in &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt;. The CLI wheel force-includes it.&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;force-include&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;tests/cross_cutting/packaging/test_packaging_safety.py&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;In-house doctrine lives in &lt;code dir=&quot;auto&quot;&gt;packs/internal/&lt;/code&gt; and never ships (its source home moves to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-open-packs&lt;/code&gt; — source-location only; still excluded from the wheel/sdist).&lt;/td&gt;&lt;td&gt;ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-16-3&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;test_packaging_safety.py&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;The mission data move to &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions&lt;/code&gt; has landed.&lt;/td&gt;&lt;td&gt;#3091, closed by PR #3204&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h2 id=&quot;3-standing-concerns&quot;&gt;3. Standing concerns&lt;/h2&gt;
&lt;p&gt;Each sub-area states its &lt;strong&gt;invariant&lt;/strong&gt; (the durable “why”) and its &lt;strong&gt;open work&lt;/strong&gt; (the
part that turns over).&lt;/p&gt;
&lt;h3 id=&quot;31-the-code-boundary-3101&quot;&gt;3.1 The code boundary (#3101)&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; depends only on &lt;code dir=&quot;auto&quot;&gt;kernel&lt;/code&gt;. Callers outside it import
through &lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt;. The layer rules and the public-surface test stay the
mechanical guard; a function-local import never papers over an upward reach.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open work.&lt;/strong&gt; #3101 is a design spike. &lt;strong&gt;As of the 2026-10-12 direction update it is
GA-gating&lt;/strong&gt; (via its precondition #645), and the target is the charter’s &lt;strong&gt;own repository&lt;/strong&gt;
(an independently-released external contract package), not merely a wheel built in-tree. It
must decide:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;whether the released unit is &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; alone or all of &lt;code dir=&quot;auto&quot;&gt;src/charter/&lt;/code&gt;;&lt;/li&gt;
&lt;li&gt;whether &lt;code dir=&quot;auto&quot;&gt;kernel&lt;/code&gt; ships as its own wheel first (&lt;code dir=&quot;auto&quot;&gt;src/kernel/pyproject.toml&lt;/code&gt; is dormant
metadata for that, per ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-02-1&lt;/code&gt;);&lt;/li&gt;
&lt;li&gt;whether the new package starts version-locked to the CLI, as &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-tracker&lt;/code&gt; did (ADR &lt;code dir=&quot;auto&quot;&gt;2026-04-25-1&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The repository extraction 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;; its mechanics ride with a dedicated epic (to be filed);
this plan owns the invariant and the precondition, not that epic.&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;h3 id=&quot;32-content-provenance-3504-then-3022&quot;&gt;3.2 Content provenance (#3504, then #3022)&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; A consumer’s install does not change when content provenance moves. Built-in
doctrine is always present in the wheel, byte-identical to a pinned source; the filesystem
resolver &lt;code dir=&quot;auto&quot;&gt;resolve_pack_root(&quot;built-in&quot;)&lt;/code&gt; stays as it is. &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;packs/internal/&lt;/code&gt; stays excluded
from the wheel/sdist&lt;/strong&gt; regardless of where its source is authored (the &lt;code dir=&quot;auto&quot;&gt;packs&lt;/code&gt; include stays
narrowed to &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt;, guarded by &lt;code dir=&quot;auto&quot;&gt;tests/cross_cutting/packaging/test_packaging_safety.py&lt;/code&gt;).
Moving a tier’s &lt;em&gt;source&lt;/em&gt; changes neither its presence nor its exclusion in the consumer install.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Design of record.&lt;/strong&gt; ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-16-2&lt;/code&gt; (Accepted) chose Option B: author the content in
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-open-packs&lt;/code&gt;, and have the build fetch a pinned, checksummed ref before
&lt;code dir=&quot;auto&quot;&gt;hatch build&lt;/code&gt;. &lt;strong&gt;Direction update 2026-10-12:&lt;/strong&gt; that open-packs source home now covers &lt;strong&gt;both&lt;/strong&gt;
tiers — &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;packs/internal/&lt;/code&gt;. This is a &lt;strong&gt;source-location move only&lt;/strong&gt; and is
&lt;strong&gt;not&lt;/strong&gt; a reversal of ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-16-3&lt;/code&gt; (internal is a public org pack, not force-shipped);
it extends the already-chosen built-in provenance to name internal’s source home too. No
packaging code or gate changes for it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open work.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;#3504 and #6451 build the pin-and-fetch pipeline (&lt;code dir=&quot;auto&quot;&gt;make sync-packs&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;charter pack vendor&lt;/code&gt; is now a pin-bump helper).&lt;/li&gt;
&lt;li&gt;#3022 is the deferred Option C: fetching built-in content at runtime like an org pack.
It raises hard questions: &lt;code dir=&quot;auto&quot;&gt;PackContext.pack_roots&lt;/code&gt; assumes the built-in root is at
index 0, and a missing pack would become a failure mode for every consumer’s baseline
governance. Option C waits on #3504 and on the manifest and checksum work.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;33-strangler-discipline&quot;&gt;3.3 Strangler discipline&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; Every step lands in place on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; as move → shim → repoint → delete.
There is no long-lived divergent branch. A consumer-visible break rides the migration
rail (&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;) behind a deprecation shim that names its replacement and
removal version. &lt;code dir=&quot;auto&quot;&gt;src/doctrine.py&lt;/code&gt; is the live example.&lt;/p&gt;
&lt;h3 id=&quot;34-distribution-integrity-2539&quot;&gt;3.4 Distribution integrity (#2539)&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Invariant.&lt;/strong&gt; Once content or code ships from a second source, the consumer can verify
what they received: pinned refs, content hashes, and later a graduated trust signal
(built-in / org / third-party / verified).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Open work.&lt;/strong&gt; #2539 (owner: Robert) is on &lt;strong&gt;4.x Work&lt;/strong&gt;, not in 4.0.0 scope. One of its
eight sub-issues is done.&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;No acceptance check for “transparent to consumers”.&lt;/strong&gt; Nothing tests yet that a
consumer pinned to &lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt; survives the wheel split, or that a vendored
&lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; is byte-identical to the pinned open-packs ref. #3504’s confirmation
criterion and #2539 are the natural homes for those checks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Epic facets are mixed in the tracker.&lt;/strong&gt; #2466 carries both authoring work (§3.2 of
the doctrine-charter plan) and packaging work (this plan) as sub-issues. The scope
split in §1 of this plan is the reconciling map until the tracker mirrors it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mixed GA scope as of 2026-10-12.&lt;/strong&gt; The charter modular extraction (§3.1, #3101, with #645
as its GA-gating precondition) is &lt;strong&gt;now a GA gate leg&lt;/strong&gt; — no longer post-4.0.0. The content
provenance move (#3504/#3022) and verified distribution (#2539) remain post-4.0.0 direction,
not GA dependencies. None of these issues is &lt;em&gt;on milestone 11&lt;/em&gt; (local integrity); the GA gate
now spans three legs (see the roadmap), and the charter-extraction leg is tracked on #645 and
ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-12-2&lt;/code&gt; plus a charter-repo-extraction epic (to be filed), not on milestone 11.
&lt;strong&gt;Superseded 2026-10-19:&lt;/strong&gt; the GA leg is a frozen &lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt; seam and a green
conformance corpus (epic #6099, re-scoped), not a repository extraction; see &lt;em&gt;Open work&lt;/em&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h2 id=&quot;5-epics-at-a-glance&quot;&gt;5. Epics at a glance&lt;/h2&gt;
&lt;p&gt;A snapshot for orientation. Check 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.&lt;/p&gt;















































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Work&lt;/th&gt;&lt;th&gt;Sub-area&lt;/th&gt;&lt;th&gt;Epic&lt;/th&gt;&lt;th&gt;State (2026-09-30)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Mission data into &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions&lt;/code&gt;&lt;/td&gt;&lt;td&gt;3.3&lt;/td&gt;&lt;td&gt;#3091&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Landed&lt;/strong&gt; (PR #3204)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Curated public surface &lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt;&lt;/td&gt;&lt;td&gt;3.1&lt;/td&gt;&lt;td&gt;#3179&lt;/td&gt;&lt;td&gt;Largely landed&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Doctrine/charter wheel split&lt;/td&gt;&lt;td&gt;3.1&lt;/td&gt;&lt;td&gt;#3101&lt;/td&gt;&lt;td&gt;Open, design spike, Product backlog&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Pin and fetch open-packs into &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;packs/internal/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;3.2&lt;/td&gt;&lt;td&gt;#3504, #6451&lt;/td&gt;&lt;td&gt;Landed on branch &lt;code dir=&quot;auto&quot;&gt;feat/6451-built-in-from-open-packs&lt;/code&gt;; pending merge&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Runtime-fetched built-in pack (Option C)&lt;/td&gt;&lt;td&gt;3.2&lt;/td&gt;&lt;td&gt;#3022&lt;/td&gt;&lt;td&gt;Open, deferred, Product backlog&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Verified distribution&lt;/td&gt;&lt;td&gt;3.4&lt;/td&gt;&lt;td&gt;#2539&lt;/td&gt;&lt;td&gt;Open, 4.x Work&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;All six sit under the parent epic #2466.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;6-cross-references&quot;&gt;6. Cross-references&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/plans/domains/doctrine-charter-domain-plan/&quot;&gt;Doctrine &amp;#x26; Charter Domain Plan&lt;/a&gt;. Its §3.2 is the
authoring boundary for this plan.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/plans/domains/api-dashboard-domain-plan/&quot;&gt;API &amp;#x26; Dashboard Domain Plan&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;ADR &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 wheel-split assessment.&lt;/li&gt;
&lt;li&gt;ADR &lt;a href=&quot;/adr/3.x/2026-08-16-2-open-packs-is-source-of-truth-for-built-in-doctrine/&quot;&gt;2026-08-16-2 open-packs is source of truth for built-in doctrine&lt;/a&gt;: Option B, the re-vendor, amended 2026-10-19 to pin and fetch (#6451).&lt;/li&gt;
&lt;li&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;: the authoring seam this plan stays out of.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/plans/&quot;&gt;Plans index&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
