<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/context/charter-overview/">
  <id>https://docs.spec-kitty.ai/context/charter-overview/</id>
  <title>How Charter Works</title>
  <updated>2026-11-13T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/context/charter-overview/"/>
  <summary>The Charter mental model — synthesis, DRG, governed context, and profile invocation.</summary>
  <content type="html">&lt;span id=&quot;how-charter-works&quot;&gt;&lt;/span&gt;
&lt;p&gt;Charter is the governance layer that turns your project’s structured policy file
(&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt;) into context that every agent mission action automatically
receives. This page explains the mental model — synthesis, the DRG, governed context, and profile
invocation. For the complete, step-by-step create-your-charter flow (interview through
generation, validation, and synthesis), see
&lt;a href=&quot;/guides/how-to/governance/setup-governance/&quot;&gt;How to Set Up Project Governance&lt;/a&gt;. For the guided tour connecting
setup to a full mission run, see the
&lt;a href=&quot;/guides/tutorials/charter-governed-workflow/&quot;&gt;Governed Charter Workflow Tutorial&lt;/a&gt;.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key invariant&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt; is the git-tracked, authoritative,
structured charter — &lt;code dir=&quot;auto&quot;&gt;governance&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directives&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;catalog&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;overrides&lt;/code&gt; all live inside it.
What the project has activated lives beside it in the git-tracked activation ledger
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;, written by &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt;.
&lt;code dir=&quot;auto&quot;&gt;governance&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directives&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;overrides&lt;/code&gt; are hand-authored (or interview-seeded); &lt;code dir=&quot;auto&quot;&gt;catalog&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;metadata&lt;/code&gt; are refreshed deterministically by
&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt; is a &lt;strong&gt;curated companion&lt;/strong&gt;: a human-readable
narrative the runtime never parses, scrapes, or resolves policy from — editing it has no
runtime effect. A project may also keep a public constitution or governance document outside
&lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt;; both &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; and any external document are supporting context, not alternate
authoritative charter paths. &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; carries a single &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; pointer that
resolves the active &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;. Do not hand-edit &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;catalog&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;metadata&lt;/code&gt;
sections, synthesis manifests, or provenance sidecars. Agent synthesis input under
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/&lt;/code&gt; is produced by the harness, not by routine operator edits.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;h2 id=&quot;what-charter-does&quot;&gt;What Charter Does&lt;/h2&gt;
&lt;p&gt;Charter solves a specific problem: agent prompts need consistent, project-accurate policy context,
sourced from one operator-controlled, machine-readable charter file.&lt;/p&gt;
&lt;p&gt;The mechanism:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You author (directly, or via interview + &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt;) the &lt;code dir=&quot;auto&quot;&gt;governance&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;directives&lt;/code&gt;
sections of &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt; — testing standards, quality gates, branching rules,
directive selections — and record what you activate in &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;
with &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; refreshes &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;catalog&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;metadata&lt;/code&gt; sections (the doctrine
reference manifest and a generation timestamp) from the active charter, merging
the refresh back into the file without touching your authored sections.&lt;/li&gt;
&lt;li&gt;When &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; invokes an agent profile for a mission action, the runtime reads
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; directly and injects the relevant charter context into the prompt automatically.
The agent does not invent governance; it reads and complies with what the charter says.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; plays no role in that resolution path. Keep it as a narrative companion — a
human-facing summary of the same policy, or a pointer to a public constitution — but editing it
does not change runtime behavior.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;synthesis-flow&quot;&gt;Synthesis Flow&lt;/h2&gt;
&lt;p&gt;At a high level, the Charter setup flow is: capture policy decisions via interview, generate (or
refresh) &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, check for graph-native decay, synthesize doctrine into
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;, validate the bundle against the &lt;code dir=&quot;auto&quot;&gt;CharterBundleManifest&lt;/code&gt; v2.0.0 schema, and
confirm status shows no drift. For the complete command-by-command walkthrough — including flags,
what each command outputs, and how to recover from a stale bundle — follow
&lt;a href=&quot;/guides/how-to/governance/setup-governance/&quot;&gt;How to Set Up Project Governance&lt;/a&gt; rather than reproducing the
sequence here.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt;&lt;/strong&gt; is a separate runtime/debug command for rendering action-specific
governance context for a specific workflow action. It is not part of the generation pipeline:&lt;/p&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;# Render what governance context an agent would receive for the &apos;implement&apos; action&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;uv&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;run&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;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;To change runtime policy by hand, edit &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;governance:&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;directives:&lt;/code&gt; sections
directly. There is no separate sync step: the next &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; call reads the file as-is.
The &lt;code dir=&quot;auto&quot;&gt;charter sync&lt;/code&gt; command was removed (#5828); nothing replaces it.&lt;/p&gt;
&lt;p&gt;A directive you add under the &lt;code dir=&quot;auto&quot;&gt;directives:&lt;/code&gt; section is &lt;strong&gt;additive&lt;/strong&gt;: it is unioned onto the
directive set the project already resolves (the built-in catalog default, charter-activated
directives, or an explicit &lt;code dir=&quot;auto&quot;&gt;governance.charter.selected_directives&lt;/code&gt; selection), never a
replacement of it. If you set &lt;code dir=&quot;auto&quot;&gt;governance.charter.selected_directives&lt;/code&gt;, that list defines the
authoritative &lt;em&gt;base&lt;/em&gt; set; the &lt;code dir=&quot;auto&quot;&gt;directives:&lt;/code&gt; section then layers on top of it additively. The
resolution branch is now visible: &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --action plan --json&lt;/code&gt; exposes a
top-level &lt;code dir=&quot;auto&quot;&gt;directives_source&lt;/code&gt; (for example &lt;code dir=&quot;auto&quot;&gt;catalog_fallback+project_local&lt;/code&gt; when a project-local
directive is merged onto the catalog default, or &lt;code dir=&quot;auto&quot;&gt;catalog_fallback&lt;/code&gt; for a bare project), and the
human-readable &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; output prints a diagnostic when project-local directives are
merged or when the catalog-default fallback is used.&lt;/p&gt;
&lt;p&gt;For partial regeneration of a specific directive or tactic without touching unrelated artifacts:&lt;/p&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;uv&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;run&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;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;resynthesize&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;--topic&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;directive:PROJECT_001&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;hr&gt;
&lt;h2 id=&quot;the-drg-backed-context-model&quot;&gt;The DRG-Backed Context Model&lt;/h2&gt;
&lt;p&gt;The charter bundle is not a flat file — it is backed by the &lt;strong&gt;Doctrine Reference Graph (DRG)&lt;/strong&gt;.
The DRG is a directed graph whose nodes are doctrine artifacts (directives, tactics, paradigms,
styleguides, toolguides, procedures, agent profiles and the other kinds), mission actions and
glossary scopes (&lt;code dir=&quot;auto&quot;&gt;NodeKind&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/drg/models.py&lt;/code&gt;), and whose edges use typed
relations such as &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;, &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;vocabulary&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;instantiates&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;replaces&lt;/code&gt;, and
&lt;code dir=&quot;auto&quot;&gt;delegates_to&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;When &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; prepares a prompt for a mission action (for example, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;), the
runtime traverses the DRG from the entry point for that action and collects the relevant subgraph.
This is &lt;strong&gt;governed profile invocation&lt;/strong&gt;: the agent receives a &lt;code dir=&quot;auto&quot;&gt;(profile, action, governance-context)&lt;/code&gt;
triple, where the governance context is the DRG-derived subgraph rendered as structured text.&lt;/p&gt;
&lt;p&gt;The agent cannot see or modify the DRG directly. It receives the rendered context and acts in
accordance with the directives it finds there.&lt;/p&gt;
&lt;h2 id=&quot;external-governance-documents&quot;&gt;External Governance Documents&lt;/h2&gt;
&lt;p&gt;Projects that already publish governance outside &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt;, for example
&lt;code dir=&quot;auto&quot;&gt;spec/constitution.md&lt;/code&gt;, should keep that public document in place and reference it from
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt;. Spec Kitty does not require the public document, &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;,
and &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; to be byte-for-byte equal — &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; is the only one the runtime resolves.&lt;/p&gt;
&lt;p&gt;Declare supporting docs under &lt;code dir=&quot;auto&quot;&gt;governance.charter.governance_references&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;
(the interview’s equivalent answer writes into this same section):&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;yaml&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:#7FDBCA;--1:#111111&quot;&gt;governance&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;:&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;  &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;charter&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;:&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;    &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;governance_references&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;:&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;      &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;- &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;spec/constitution.md&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;spec-kitty charter context --action ...&lt;/code&gt; renders these paths as required governance reading.
&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter status&lt;/code&gt; reports missing or unsafe references so operators can fix stale paths.
All referenced paths must be repository-relative and stay inside the repo root.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;bootstrap-vs-compact-context&quot;&gt;Bootstrap vs Compact Context&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --action &amp;#x3C;action&gt; --json&lt;/code&gt; reports which of two modes it rendered in
its &lt;code dir=&quot;auto&quot;&gt;mode&lt;/code&gt; field. The mode depends on the action and on whether this is its first load, not on the
size of the payload (&lt;code dir=&quot;auto&quot;&gt;src/charter/activation/context.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;context_state.py&lt;/code&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bootstrap mode&lt;/strong&gt;: the first time an action loads context (recorded in
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/context-state.json&lt;/code&gt;), or whenever a caller asks for a depth of 2 or more, the runtime
renders the governance it resolved for that action from the DRG. This applies to &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;BOOTSTRAP_ACTIONS&lt;/code&gt;) and to any other action whose node is
declared in the DRG.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Compact mode&lt;/strong&gt;: later loads of the same action get a compact view that keeps every directive,
tactic and section id but collapses the long-form text. An action with no declared DRG node
always gets the compact view.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Issue #787 (closed) recorded that compact mode left out free-form rules written only in
&lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;. The runtime resolves policy from &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; only (see the key invariant above), so
a rule belongs there, not in &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;key-governance-files&quot;&gt;Key Governance Files&lt;/h2&gt;


















































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;File&lt;/th&gt;&lt;th&gt;Written by&lt;/th&gt;&lt;th&gt;Purpose&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Human&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;governance&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;directives&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;overrides&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;catalog&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;metadata&lt;/code&gt; only)&lt;/td&gt;&lt;td&gt;The single git-tracked, authoritative structured charter&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt;, presets&lt;/td&gt;&lt;td&gt;Activation ledger: what the project has activated and deactivated&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Human&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Curated narrative companion; never parsed by the runtime&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Human&lt;/strong&gt;; &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; pointer minted once at bootstrap&lt;/td&gt;&lt;td&gt;Points to the active &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;; also declares org packs under &lt;code dir=&quot;auto&quot;&gt;charter_packs.org.packs&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Agent harness&lt;/td&gt;&lt;td&gt;Candidate doctrine YAML consumed by &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesis-manifest.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Auto-generated (&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;Manifest for promoted project-local doctrine artifacts&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/provenance/*.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Auto-generated (&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;Provenance sidecars for synthesized doctrine artifacts&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Auto-generated (synthesize)&lt;/td&gt;&lt;td&gt;Project-local doctrine promoted by synthesizer&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;See &lt;a href=&quot;/context/governance-files/&quot;&gt;Governance Files Reference&lt;/a&gt; for the full table.&lt;/p&gt;
&lt;hr&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/governance-files/&quot;&gt;Governance Files Reference&lt;/a&gt; — authoritative 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; — initial setup walkthrough&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/guides/how-to/governance/synthesize-doctrine/&quot;&gt;How to Synthesize and Maintain Doctrine&lt;/a&gt; — day-to-day synthesis&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/charter-synthesis-drg/&quot;&gt;Understanding Charter: Synthesis, DRG, and Governed Context&lt;/a&gt; — deeper explanation&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/charter-pack-usage-journey/&quot;&gt;Activation Preset Usage Journey&lt;/a&gt; — the
preset-driven onboarding path (&lt;code dir=&quot;auto&quot;&gt;charter activate --preset&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt;) and the dispatch safety net&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
