<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/4.x/2026-10-16-1-extract-charter-offering-first-activation-rework-post-ga/">
  <id>https://docs.spec-kitty.ai/adr/4.x/2026-10-16-1-extract-charter-offering-first-activation-rework-post-ga/</id>
  <title>ADR: extract the charter offering layer first as the GA gate leg; the activation rework rides the post-GA stable line</title>
  <updated>2026-10-21T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/4.x/2026-10-16-1-extract-charter-offering-first-activation-rework-post-ga/"/>
  <summary>Charter extraction splits by seam: offering extracts first as the 4.0.0 GA gate leg; the activation drain/rework moves off-gate to CLI 4.x stable. Amends 2026-10-12-2.</summary>
  <content type="html">&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted (2026-10-16); amended 2026-10-20 (activation timing and authority, see the end).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-10-16&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Stijn Dejongh (operator).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt; epic #6099 (extract the charter offering layer to its own
independently-released repository — GA-gating, milestone “4.0.0 release scope”); #6188
(move the &lt;code dir=&quot;auto&quot;&gt;specify_cli → charter&lt;/code&gt; imports onto the offering seam — &lt;strong&gt;completed&lt;/strong&gt; 2026-10-13,
PR #6200); #6218 (align the seam’s return types with &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; ADR-0004).
Amends 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
charter becomes an external contract package in its own repository) and its Amendment
2026-10-13. Companion: 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; (the
open-core producer surface). Durable plan:
&lt;a href=&quot;/plans/domains/doctrine-charter-domain-plan/&quot;&gt;Doctrine &amp;#x26; Charter&lt;/a&gt; §3.6.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Reader:&lt;/strong&gt; a maintainer sequencing the charter extraction, or planning the 4.0.0 GA gate.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;ADR 2026-10-12-2 ratified that the charter becomes an external contract package in its own
repository, with two sibling entry-point seams (&lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter.activation.api&lt;/code&gt;;
Amendment 2026-10-13). That amendment held &lt;strong&gt;236 &lt;code dir=&quot;auto&quot;&gt;(file, module)&lt;/code&gt; reaches&lt;/strong&gt; from
&lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;runtime&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;glossary&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; internals
as a shrink-only baseline (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/charter_activation_boundary_baseline.yaml&lt;/code&gt;,
owner #6099) and stated they would be “drained onto &lt;code dir=&quot;auto&quot;&gt;charter.activation.api&lt;/code&gt; &lt;strong&gt;before the
4.0.0 GA gate&lt;/strong&gt;.”&lt;/p&gt;
&lt;p&gt;Two facts have changed the right sequencing since then:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;The import-move precondition is done.&lt;/strong&gt; #6188 (“move the &lt;code dir=&quot;auto&quot;&gt;specify_cli → charter&lt;/code&gt; imports
onto the &lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt; public surface”) &lt;strong&gt;closed completed&lt;/strong&gt; on 2026-10-13
(PR #6200 split the offering and activation entry-point seams). #645 (“Stable Application
API Surface”), long cited as the open GA-gating precondition, &lt;strong&gt;closed &lt;code dir=&quot;auto&quot;&gt;not_planned&lt;/code&gt;&lt;/strong&gt; the
same day with all 13 children shipped. Any plan whose first task is “move the ~129 imports”
or that cites #645 as an open precondition is planning finished work.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The offering layer has zero code dependency on activation.&lt;/strong&gt; Verified in-tree:
&lt;code dir=&quot;auto&quot;&gt;src/charter/offering/**&lt;/code&gt; contains &lt;strong&gt;no&lt;/strong&gt; runtime import of &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; (the 67
textual matches are all docstrings / Sphinx cross-references — &lt;code dir=&quot;auto&quot;&gt;org_pack_loader.py&lt;/code&gt; even
documents that “&lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; sits below the charter facades and &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt;”).
The reverse edge is heavy: &lt;strong&gt;~360&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; references from &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt;.
Offering is the foundational bottom layer; activation sits above it and consumes it.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The consequence: &lt;strong&gt;offering can be lifted out cleanly now&lt;/strong&gt;, consuming nothing that would have
to follow it, while &lt;strong&gt;activation can stay in core&lt;/strong&gt; and keep consuming the (now external)
offering package. Draining the 236 activation reaches — the long pole of the whole extraction —
is &lt;strong&gt;not&lt;/strong&gt; a precondition for extracting offering, so forcing it onto the GA gate couples the
cheap, ready leg to the expensive, not-ready one.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dependency direction (verified).&lt;/strong&gt; offering → activation code edges = 0; activation →
offering ≈ 360. The clean cut is offering-first.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Smallest viable GA scope.&lt;/strong&gt; The GA gate should carry the leg that is ready and foundational,
not the leg (activation drain) whose 236-reach baseline is still being worked down.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Single canonical authority / architectural alignment&lt;/strong&gt; (charter governing principles): the
extracted unit is consumed through one 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;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Honest records&lt;/strong&gt; (Standing Order #9 throughline — don’t carry stale “truth”): the
precondition record (#645 open, “~129 imports to move”) is stale and must be corrected.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Charter modular extraction splits by seam. Offering extracts first as the GA gate leg;
the activation rework rides the post-GA CLI 4.x stable line.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;D-1 (Accepted): extract &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; first, as the charter modular-extraction GA
leg.&lt;/strong&gt; It is the foundational layer with zero code dependency on activation, so it is
independently liftable. This is the charter leg of the 4.0.0 GA gate (ADR 2026-10-12-2 D-2,
roadmap rule 5), now scoped to &lt;strong&gt;offering&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;D-2 (Accepted): the &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; drain/rework moves OFF the GA gate to the post-GA
“CLI 4.x stable” milestone.&lt;/strong&gt; Activation &lt;strong&gt;stays in core as-is for GA&lt;/strong&gt;. The 236-reach
shrink-only baseline remains a priced, shrink-only ratchet (ADR 2026-09-30-1), but draining
it onto &lt;code dir=&quot;auto&quot;&gt;charter.activation.api&lt;/code&gt;, and any activation extraction, is &lt;strong&gt;post-GA&lt;/strong&gt;. &lt;strong&gt;This
supersedes ADR 2026-10-12-2 Amendment 2026-10-13’s clause that the activation reaches are
“drained onto &lt;code dir=&quot;auto&quot;&gt;charter.activation.api&lt;/code&gt; before the 4.0.0 GA gate.”&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;D-3 (Accepted): the offering extraction is tracked as four phases under epic #6099 on
milestone “4.0.0 release scope.”&lt;/strong&gt; They follow the &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;
precedent (version-locked first, decouple cadence once the boundary is proven) and the
#645/#460 pattern (typed contract + acceptance test before transport). ADR-0004 DTO
alignment (#6218) coordinates with the first phase.&lt;/p&gt;








































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Phase&lt;/th&gt;&lt;th&gt;Issue&lt;/th&gt;&lt;th&gt;Scope&lt;/th&gt;&lt;th&gt;Size&lt;/th&gt;&lt;th&gt;Red-first&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;P1&lt;/td&gt;&lt;td&gt;#6285&lt;/td&gt;&lt;td&gt;enumerate + freeze the offering public contract surface (reconcile &lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt; + the &lt;code dir=&quot;auto&quot;&gt;charter.*&lt;/code&gt; facades; annotate ADR-0004 DTO-forward)&lt;/td&gt;&lt;td&gt;M&lt;/td&gt;&lt;td&gt;—&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;P2&lt;/td&gt;&lt;td&gt;#6286&lt;/td&gt;&lt;td&gt;red-first offering contract-conformance acceptance suite against the frozen surface (the “a seam-pinned consumer survives the split” net)&lt;/td&gt;&lt;td&gt;M&lt;/td&gt;&lt;td&gt;&lt;strong&gt;yes&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;P3&lt;/td&gt;&lt;td&gt;#6287&lt;/td&gt;&lt;td&gt;enforce &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; as an external contract package at the boundary/layer gates (importing up the chain fails dependency resolution)&lt;/td&gt;&lt;td&gt;L&lt;/td&gt;&lt;td&gt;—&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;P4&lt;/td&gt;&lt;td&gt;#6288&lt;/td&gt;&lt;td&gt;&lt;del&gt;extract &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt;, consume version-locked first&lt;/del&gt; &lt;strong&gt;(replaced by Amendment 2026-10-19):&lt;/strong&gt; the offering stays in core behind &lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt; and is replaced in place by the spec-kitty-charter service (spec-kitty-charter ADR-0008). The 4.0.0 leg is a frozen seam and a green conformance corpus, not an extraction.&lt;/td&gt;&lt;td&gt;L&lt;/td&gt;&lt;td&gt;—&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;#6218 (align &lt;code dir=&quot;auto&quot;&gt;api.py&lt;/code&gt; C-003 with &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; ADR-0004) is a &lt;strong&gt;P1 prerequisite&lt;/strong&gt;, not a
phase — it is docs/ADR only. The single first ticket is &lt;strong&gt;#6285 (P1)&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;D-4 (Accepted): the event ledger’s value-bearing read surface is confirmed GA-gating; no
additional read-path tickets join the gate.&lt;/strong&gt; The claim “the event API is only valuable if the
read path is enabled” is &lt;strong&gt;true only abstractly&lt;/strong&gt; (a write-only ledger nobody reads delivers no
value) but is &lt;strong&gt;disproved as a reason to widen the gate&lt;/strong&gt;: the append-only &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;
ledger already has live readers today — &lt;code dir=&quot;auto&quot;&gt;orchestrator-api mission-state&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;list-ready&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;agent tasks status --json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;events tail&lt;/code&gt;, and the Java &lt;code dir=&quot;auto&quot;&gt;services/mission-status-api/&lt;/code&gt; reading
the ledger off disk — and ADR 2026-10-13-2 routes event value through the ledger being &lt;em&gt;read&lt;/em&gt;,
not through the deliberately inert &lt;code dir=&quot;auto&quot;&gt;status/adapters.py&lt;/code&gt; fan-out. The value-bearing read surface —
epic #5528 and its detail resource #957 — is &lt;strong&gt;already GA-gating&lt;/strong&gt; on milestone “4.0.0 release
scope” (ADR 2026-10-01-2 D-12), so the intent that read-path value sit on the GA gate is
&lt;strong&gt;already satisfied with no change&lt;/strong&gt;. The reader-consolidation refactors #5532 (re-point readers
onto one seam/reducer) and #5533 (rehome ex-dashboard routes) stay &lt;strong&gt;off-gate&lt;/strong&gt; (CLI 4.x stable)
by their deliberate placement; pulling them onto the gate would duplicate #5528 and contradict
ADR 2026-10-01-2 D-5. &lt;strong&gt;Open sub-decision (operator):&lt;/strong&gt; whether to pull &lt;strong&gt;#5532 alone&lt;/strong&gt; onto the
gate on the separate reducer-duality argument (two reducers persist at GA while #5532 stays
off-gate, #4941) — recorded here, not decided.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;D-5 (Accepted): correct the stale precondition record.&lt;/strong&gt; #645 is closed &lt;code dir=&quot;auto&quot;&gt;not_planned&lt;/code&gt;;
#6188 (the import move onto the offering seam) is complete. Neither is an open precondition.
#6099 is the live extraction epic; the roadmap, charter and domain plans that still cite
“#645 / ~129 imports to move” as open GA-gating work are corrected to match.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;consequences&quot;&gt;Consequences&lt;/h3&gt;
&lt;h4 id=&quot;positive&quot;&gt;Positive&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The GA gate carries the ready, foundational leg (offering) and is not blocked on the 236-reach
activation drain.&lt;/li&gt;
&lt;li&gt;Open-core consumers can depend on the extracted &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; unit at its own version.&lt;/li&gt;
&lt;li&gt;The precondition record stops asserting finished work as pending.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The charter is extracted in two steps (offering now, activation later), so cross-repo
coordination exists for longer than a single-shot extraction would.&lt;/li&gt;
&lt;li&gt;Activation keeps a shrink-only baseline of 236 reaches live past GA (priced debt, owner #6099
/ its post-GA successor).&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Activation staying in core for GA does not change any gate or layer rule in this ADR; it
changes &lt;em&gt;when&lt;/em&gt; the activation drain must land.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;confirmation&quot;&gt;Confirmation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;An architectural test pins &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; as an external contract package once the
extraction lands; a consumer pinned to the offering seam survives the split (the phase-2
acceptance suite is that net).&lt;/li&gt;
&lt;li&gt;The four #6099 children are filed on milestone “4.0.0 release scope”.&lt;/li&gt;
&lt;li&gt;The roadmap and ADR 2026-10-12-2 no longer cite #645 / “~129 imports” as open GA-gating work.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;more-information&quot;&gt;More Information&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;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; and its
Amendment 2026-10-13 (the two sibling seams and the shrink-only activation baseline).&lt;/li&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; §3.6.&lt;/li&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 GA gate legs.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; ADR-0004 (the public API returns generated OpenAPI DTOs), tracked in
core by #6218.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-10-19-p4-is-replaced-the-offering-is-replaced-in-place-not-extracted&quot;&gt;Amendment 2026-10-19: P4 is replaced; the offering is replaced in place, not extracted&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Stijn Dejongh (operator), 2026-10-19. Requested by
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/blob/main/docs/adr/0010-cutover-scope-and-seam-boundary.md&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; ADR-0010&lt;/a&gt;
(“Requests to core”), building on &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt;
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/blob/main/docs/adr/0008-rewrite-and-replace-against-bdd-and-openapi-contracts.md&quot;&gt;ADR-0008&lt;/a&gt;
(rewrite and replace). Recorded in
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-charter/pull/88&quot;&gt;spec-kitty-charter#88&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;D-3, phase P4 (#6288, “extract &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt;”) is replaced
with:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The offering stays in core behind &lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt; and is replaced in place by the
spec-kitty-charter service (spec-kitty-charter ADR-0008). The 4.0.0 leg is a frozen seam and
a green conformance corpus, not an extraction.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;What this changes in the record above:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;D-1 is read through this amendment.&lt;/strong&gt; “Extract &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; first” no longer means a
repository move. Nothing Python moves to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt;; the Python charter stays in
core until its reads are retired by the cutover that ADR
&lt;a href=&quot;/adr/4.x/2026-10-03-1-charter-read-write-service-strangler/&quot;&gt;2026-10-03-1&lt;/a&gt; (Amendment 2026-10-19)
governs. The GA leg is the frozen seam (P1, #6285) and the green conformance corpus (P2,
#6286).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Additive seam symbols land by amendment of ADR &lt;a href=&quot;/adr/4.x/2026-10-03-1-charter-read-write-service-strangler/&quot;&gt;2026-10-03-1&lt;/a&gt;&lt;/strong&gt; while P1 (#6285) freezes the surface (first: &lt;code dir=&quot;auto&quot;&gt;LANGUAGE_TOKENS&lt;/code&gt;, #6541).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;D-2 stands.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; stays in core until its post-GA rework.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;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; is
superseded&lt;/strong&gt; by &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; ADR-0008 and ADR-0010 (operator ruling, 2026-10-19).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;P3 (#6287) is premised on the extraction&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; as an external contract package at
the boundary gates). It is not re-scoped by this amendment; the operator decides its fate
separately.&lt;/li&gt;
&lt;li&gt;The &lt;em&gt;Confirmation&lt;/em&gt; bullet “an architectural test pins &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; as an external
contract package once the extraction lands” no longer applies: no extraction lands. The
phase-2 conformance corpus remains the net.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-10-20-the-charter-service-becomes-authoritative-for-activation&quot;&gt;Amendment 2026-10-20: the charter service becomes authoritative for activation&lt;/h2&gt;
&lt;p&gt;Operator rulings of 2026-10-20 (Mission &lt;code dir=&quot;auto&quot;&gt;persistent-deactivation-ledger-01M59YAA&lt;/code&gt;, rulings
&lt;code dir=&quot;auto&quot;&gt;contract_rulings_r2_r12&lt;/code&gt; R2 and &lt;code dir=&quot;auto&quot;&gt;contract_epic_ga_milestone&lt;/code&gt;), recorded in the amendment of
ADR &lt;a href=&quot;/adr/4.x/2026-10-19-1-activation-ledger-persists-deactivation/&quot;&gt;2026-10-19-1&lt;/a&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Authority after the cutover (R2).&lt;/strong&gt; After the charter contract’s 1.0.0 remote cutover, the
charter service is authoritative for activation, and core’s activation ledger
(&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;) is the mapped local copy. Until then the activation
ledger stays core’s authority, and an anti-corruption layer maps its content onto the
contract (&lt;code dir=&quot;auto&quot;&gt;contract_document_scope&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Timing.&lt;/strong&gt; The post-GA timing of the activation rework is superseded. Switching to the
charter surface is a 4.0 deliverable: the charter-contract alignment epic and all its
children are on the GA milestone (#11), whose target date is removed. The offering-first
split of this ADR is unchanged.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
