<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/architecture/charter-pack-usage-journey/">
  <id>https://docs.spec-kitty.ai/architecture/charter-pack-usage-journey/</id>
  <title>Activation Preset Usage Journey: Activate, Generate, and the Dispatch Safety Net</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/architecture/charter-pack-usage-journey/"/>
  <summary>Why `charter activate --preset` alone does not deliver governance on a fresh project, the `generate` follow-up, and how the dispatch fallback behaves around compilation.</summary>
  <content type="html">&lt;span id=&quot;activation-preset-usage-journey-activate-generate-and-the-dispatch-safety-net&quot;&gt;&lt;/span&gt;
&lt;p&gt;&lt;a href=&quot;/guides/how-to/governance/setup-governance/&quot;&gt;How to Set Up Project Governance&lt;/a&gt; documents the
&lt;strong&gt;interview-driven&lt;/strong&gt; path to a charter (&lt;code dir=&quot;auto&quot;&gt;charter interview&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt;). This page
documents the second, &lt;strong&gt;preset-driven&lt;/strong&gt; onboarding path — &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate --preset &amp;#x3C;name&gt;&lt;/code&gt; — which is faster to run but has a two-step shape operators can miss: activating a preset
on a fresh project does &lt;strong&gt;not&lt;/strong&gt; deliver working governance. This page explains why, names the
exact follow-up command, and walks through how &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt;’s generic-agent safety net
behaves at each point in the journey.&lt;/p&gt;
&lt;p&gt;An &lt;strong&gt;activation preset&lt;/strong&gt; is a named set of activation keys that a Charter Pack ships under its
&lt;code dir=&quot;auto&quot;&gt;presets/&lt;/code&gt; directory (the built-in pack ships &lt;code dir=&quot;auto&quot;&gt;default&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;minimal&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack list&lt;/code&gt; shows every pack’s presets). Activating one changes the project’s &lt;strong&gt;active charter&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id=&quot;tldr&quot;&gt;TL;DR&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --preset &amp;#x3C;name&gt;&lt;/code&gt; writes activation choices. On a fresh project it does &lt;strong&gt;not&lt;/strong&gt;
compile them into the file the runtime actually reads.&lt;/li&gt;
&lt;li&gt;Until you also run &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate --no-from-interview&lt;/code&gt;, the project behaves —
correctly — as if no charter had been activated: &lt;code dir=&quot;auto&quot;&gt;dispatch&lt;/code&gt; keeps falling back to the generic
agent instead of hard-failing.&lt;/li&gt;
&lt;li&gt;Once compiled, the compiled bundle becomes the read authority: &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; report the preset’s governance, and &lt;code dir=&quot;auto&quot;&gt;dispatch&lt;/code&gt; starts running the router for real —
&lt;code dir=&quot;auto&quot;&gt;ROUTER_NO_MATCH&lt;/code&gt; on an unmatched request is now the honest signal, not a bug. From then on,
every &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; (preset or single artifact) refreshes the compiled catalog by default.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;three-tiers-not-two&quot;&gt;Three tiers, not two&lt;/h2&gt;
&lt;p&gt;Preset onboarding involves three distinct files, and they are not interchangeable:&lt;/p&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Tier&lt;/th&gt;&lt;th&gt;Path&lt;/th&gt;&lt;th&gt;Written by&lt;/th&gt;&lt;th&gt;Role&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Activation write store&lt;/strong&gt; (the active charter)&lt;/td&gt;&lt;td&gt;The activation ledger, &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt; (&lt;a href=&quot;/adr/4.x/2026-10-19-1-activation-ledger-persists-deactivation/&quot;&gt;ADR 2026-10-19-1&lt;/a&gt;). A project that has not run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; since 4.0.0rc8 still keeps its &lt;code dir=&quot;auto&quot;&gt;activated_*&lt;/code&gt; keys in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, or in the pointed-at &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; once a &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; pointer exists, and can record no exclusion until it does&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt;, presets, &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Records &lt;em&gt;which&lt;/em&gt; artifacts your project activated, and the &lt;code dir=&quot;auto&quot;&gt;deactivated_*&lt;/code&gt; exclusions. Not read directly by governance surfaces.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Compiled bundle&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;The compile seam — &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate&lt;/code&gt; (also exposed as &lt;code dir=&quot;auto&quot;&gt;compile_charter&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;write_compiled_charter&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;The &lt;strong&gt;authoritative read cache&lt;/strong&gt;. &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt;, and the dispatch-net predicate all key on this file’s presence and contents.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Display companion&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Seeded by &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt;; hand-edited afterward&lt;/td&gt;&lt;td&gt;Human-facing narrative. Never parsed for policy — see &lt;a href=&quot;/context/charter-overview/&quot;&gt;How Charter Works&lt;/a&gt; for the full mental model of this file’s role.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --preset&lt;/code&gt; writes the first tier. Its default post-activation recompile
(&lt;code dir=&quot;auto&quot;&gt;--compile&lt;/code&gt;) only &lt;strong&gt;refreshes&lt;/strong&gt; a compiled bundle that already exists; it never creates one (see
&lt;a href=&quot;#why-activate-does-not-bootstrap&quot;&gt;Why activation does not bootstrap a bundle&lt;/a&gt; below), which is why
activating a preset on a fresh project and then immediately checking &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; can look like
nothing happened.&lt;/p&gt;
&lt;h2 id=&quot;step-1--charter-activate---preset&quot;&gt;Step 1 — &lt;code dir=&quot;auto&quot;&gt;charter activate --preset&lt;/code&gt;&lt;/h2&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;charter&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;activate&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--preset&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;minimal&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;This applies the preset with &lt;strong&gt;replace semantics&lt;/strong&gt;: every activation key the preset lists is
written (plus any ids your org packs require), and every key it governs but leaves out is removed.
If the change would alter a key you customized by hand, the command refuses and names the key;
pass &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; to apply the preset anyway. A deactivated id the preset lists stays deactivated and
is named in the output; &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; also clears its exclusion. &lt;code dir=&quot;auto&quot;&gt;--pack &amp;#x3C;name&gt;&lt;/code&gt; picks the pack whose preset applies
(default &lt;code dir=&quot;auto&quot;&gt;built-in&lt;/code&gt;), and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; prints the applied preset. The command does not touch
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt; at all.&lt;/p&gt;
&lt;p&gt;On a fresh project (no compiled bundle yet), at this point:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --action &amp;#x3C;action&gt;&lt;/code&gt; still report the
charter as unavailable — the same as an unconfigured project. This is not a bug; it is tier 2
being genuinely absent.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt; on an unmatched request still falls back to the warned generic agent (see
&lt;a href=&quot;#the-dispatch-safety-net&quot;&gt;The dispatch safety net&lt;/a&gt; below) — activating a preset must never leave
dispatch &lt;em&gt;worse&lt;/em&gt; than an empty project.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;step-2--compile-the-bundle&quot;&gt;Step 2 — compile the bundle&lt;/h2&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;charter&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;activate&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--preset&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;minimal&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;charter&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;generate&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--no-from-interview&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; runs the compile seam and creates the compiled bundle. It needs a git working
tree. After that first compile, every &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; recompiles the
catalog through the same seam by default; &lt;code dir=&quot;auto&quot;&gt;--no-compile&lt;/code&gt; skips that refresh (the catalog may then
go stale until the next &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt;), and &lt;code dir=&quot;auto&quot;&gt;--resynthesize&lt;/code&gt; runs the full synthesis pipeline
instead.&lt;/p&gt;
&lt;p&gt;&lt;a id=&quot;why-activate-does-not-bootstrap&quot;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&quot;why-activation-does-not-bootstrap-a-bundle&quot;&gt;Why activation does not bootstrap a bundle&lt;/h3&gt;
&lt;p&gt;Creating the bundle is a separate step because &lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt; does more than the bare minimum:
it requires a git working tree, seeds &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; when absent, creates &lt;code dir=&quot;auto&quot;&gt;library/&lt;/code&gt;, writes
&lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; entries, stages files, and migrates &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; to a &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; pointer. Folding all
of that into &lt;code dir=&quot;auto&quot;&gt;activate&lt;/code&gt; would silently change its contract from a lightweight activation write into
a heavier, git-dependent operation, and, on a project that has not moved to the activation ledger,
minting the &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; pointer as a side effect would move the activation write store off
&lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; in the middle of an activation. Keeping the first
compile explicit keeps both contracts predictable.&lt;/p&gt;
&lt;p&gt;After compilation, &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter context --action &amp;#x3C;action&gt;&lt;/code&gt; report the preset’s
activated directive/tactic set (not the full built-in catalog, and not “charter file not found”).
This holds even if the display-only &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; is later deleted — the read authority is
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;the-dispatch-safety-net&quot;&gt;The dispatch safety net&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt; falls back to the generic agent when a request doesn’t match a routable
profile — a safety net so an unmatched request never hard-fails on an unconfigured project. Whether
that fallback engages is decided by a predicate that keys on &lt;strong&gt;compiled-bundle presence&lt;/strong&gt; plus the
direct dispatch-routability signals (an org pack, or an explicit agent-profile activation) — not on
whether &lt;em&gt;any&lt;/em&gt; config activation has happened.&lt;/p&gt;






























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Project state&lt;/th&gt;&lt;th&gt;Compiled bundle?&lt;/th&gt;&lt;th&gt;Unmatched &lt;code dir=&quot;auto&quot;&gt;dispatch&lt;/code&gt; result&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Nothing configured&lt;/td&gt;&lt;td&gt;Absent&lt;/td&gt;&lt;td&gt;Falls back to the generic agent (baseline).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --preset&lt;/code&gt; only, no bundle&lt;/td&gt;&lt;td&gt;Absent&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Still&lt;/strong&gt; falls back to the generic agent — activating a preset never leaves dispatch worse than doing nothing.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --preset&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt; (compiled)&lt;/td&gt;&lt;td&gt;Present&lt;/td&gt;&lt;td&gt;The router runs for real. An unmatched request now returns &lt;code dir=&quot;auto&quot;&gt;ROUTER_NO_MATCH&lt;/code&gt; — the &lt;em&gt;honest&lt;/em&gt; signal, since the project opted into a compiled bundle.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Org pack or explicit agent-profile activation, no compiled bundle&lt;/td&gt;&lt;td&gt;Absent&lt;/td&gt;&lt;td&gt;The net stays disengaged and the router reaches the org profiles — no regression for projects that are routable without ever compiling a bundle.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;what-empty-means&quot;&gt;What “empty” means&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;“Empty” means the compiled bundle is ABSENT&lt;/strong&gt; — never “bundle present but its activations are
empty”. Running &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; on a bare project bootstraps a near-empty &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;; that
still counts as &lt;em&gt;not&lt;/em&gt; empty for dispatch purposes, because the operator explicitly opted into a
compiled bundle. &lt;code dir=&quot;auto&quot;&gt;ROUTER_NO_MATCH&lt;/code&gt; in that state is honest, not a regression. The predicate never
inspects bundle &lt;em&gt;contents&lt;/em&gt; to decide emptiness — only bundle presence plus the org-pack/profile
routability signals — which keeps it stable against future pack additions.&lt;/p&gt;
&lt;h3 id=&quot;the-deliberate-behaviour-change&quot;&gt;The deliberate behaviour change&lt;/h3&gt;
&lt;p&gt;Before this journey was fixed, some non-routing config-activation dimensions (directive packs,
tactic packs, toolguides, procedures, paradigms, styleguides, mission-step-contracts, and
&lt;strong&gt;glossary packs&lt;/strong&gt;) could keep the dispatch net disengaged even with no compiled bundle and no
routable org pack or agent profile. That is no longer the case: a project that has activated
&lt;strong&gt;only&lt;/strong&gt; dimensions like these — with no compiled bundle and nothing router-routable — now
correctly fires the generic-agent net, the same as an unconfigured project. This is a deliberate,
recorded behaviour change, not an oversight: none of those dimensions add a routable profile, so
disengaging the net for them was never actually safe. A glossary-only activation reversing back to
“net fires” is one visible instance of this broader, benign correction.&lt;/p&gt;
&lt;h2 id=&quot;quick-reference&quot;&gt;Quick reference&lt;/h2&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# Activate a preset, then create the compiled bundle (requires a git working tree)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;charter&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;activate&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--preset&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;minimal&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;charter&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;generate&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--no-from-interview&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;
&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# Confirm governance is actually live&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;charter&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;status&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--json&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;charter&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;context&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--action&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;implement&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--json&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;If &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; still reports the charter as missing after &lt;code dir=&quot;auto&quot;&gt;activate --preset&lt;/code&gt;, that is
expected on a fresh project — go run &lt;code dir=&quot;auto&quot;&gt;charter generate --no-from-interview&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;see-also&quot;&gt;See also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/context/charter-overview/&quot;&gt;How Charter Works&lt;/a&gt; — the write-store/compiled-bundle/companion
model in full, plus the DRG-backed context model&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/context/governance-files/&quot;&gt;Governance Files Reference&lt;/a&gt; — authoritative per-file table&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/guides/how-to/governance/setup-governance/&quot;&gt;How to Set Up Project Governance&lt;/a&gt; — the interview-driven
onboarding path (the alternative to activating a preset)&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/api/charter-commands/&quot;&gt;Charter CLI Reference&lt;/a&gt; — narrative command reference; see the
generated &lt;a href=&quot;/api/cli-commands/#spec-kitty-charter-pack&quot;&gt;CLI Command Reference&lt;/a&gt; for the full,
&lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt;-verified &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter pack&lt;/code&gt; flag surface&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/api/agent_profiles/generic-agent/&quot;&gt;Generic Agent — Agent Profile&lt;/a&gt; — the profile the
dispatch safety net falls back to&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
