<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/guides/how-to/governance/extend-charter-for-unsupported-language/">
  <id>https://docs.spec-kitty.ai/guides/how-to/governance/extend-charter-for-unsupported-language/</id>
  <title>Extend your charter for an unsupported language</title>
  <updated>2026-10-08T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/guides/how-to/governance/extend-charter-for-unsupported-language/"/>
  <summary>What &quot;Languages unknown&quot; means, how to add tech-specific guidelines to your local charter, and what review reports for non-Python missions.</summary>
  <content type="html">&lt;span id=&quot;extend-your-charter-for-an-unsupported-language&quot;&gt;&lt;/span&gt;
&lt;p&gt;Use this guide when &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context&lt;/code&gt; reports &lt;code dir=&quot;auto&quot;&gt;Languages: unknown&lt;/code&gt; for your project
(for example a Zig or Go project), or when &lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt; says the dead-code scan is not
applicable to your Mission. It shows how to add your own tech-specific guidelines to the local
charter.&lt;/p&gt;
&lt;h2 id=&quot;what-languages-unknown-means&quot;&gt;What &lt;code dir=&quot;auto&quot;&gt;Languages: unknown&lt;/code&gt; means&lt;/h2&gt;
&lt;p&gt;Spec Kitty doctrine is technology-agnostic. It does not ship specialist guidance for every language.
&lt;code dir=&quot;auto&quot;&gt;Languages: unknown&lt;/code&gt; means your project declares a language that neither the built-in detector nor any installed doctrine recognizes.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Language-neutral doctrine keeps applying. Built-in tactics are language-neutral.&lt;/li&gt;
&lt;li&gt;Guides, tool guides and profiles that are scoped to a specific language (for example the Python
ones) stop applying to your project.&lt;/li&gt;
&lt;li&gt;Language-specific guidance lives in explicitly language-specific styleguides, toolguides and
profiles, or in your local charter. Spec Kitty does not add languages one at a time.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The context output includes a single &lt;code dir=&quot;auto&quot;&gt;Advisory:&lt;/code&gt; line that points you to this page whenever no
installed doctrine is scoped to your project’s languages. That includes &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;, and also a
recognized language that has no shipped specialist guidance (for example Rust, Swift or Ruby). In
that case the compact view shows the recorded value, such as &lt;code dir=&quot;auto&quot;&gt;Languages: rust&lt;/code&gt;, followed by the
advisory. A project whose language has installed guidance (for example Python) sees no advisory.&lt;/p&gt;
&lt;h2 id=&quot;how-spec-kitty-decides&quot;&gt;How Spec Kitty decides&lt;/h2&gt;
&lt;p&gt;The languages/frameworks answer (key &lt;code dir=&quot;auto&quot;&gt;languages_frameworks&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/interview/answers.yaml&lt;/code&gt;) decides when you give one.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A real declaration decides alone.&lt;/strong&gt; When that answer is non-empty, not a placeholder and not
the shipped default, Spec Kitty resolves your languages from that answer only. Two sources
contribute, and their results are combined:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the &lt;strong&gt;built-in detector&lt;/strong&gt;, a fixed list of common languages (Python, TypeScript, JavaScript,
Rust, Java, Swift, Ruby, PHP) and their well-known tools (for example &lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mypy&lt;/code&gt; or
&lt;code dir=&quot;auto&quot;&gt;ruff&lt;/code&gt; for Python, &lt;code dir=&quot;auto&quot;&gt;npm&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;jest&lt;/code&gt; for JavaScript, &lt;code dir=&quot;auto&quot;&gt;cargo&lt;/code&gt; for Rust, &lt;code dir=&quot;auto&quot;&gt;rspec&lt;/code&gt; for Ruby);&lt;/li&gt;
&lt;li&gt;the &lt;strong&gt;doctrine-derived vocabulary&lt;/strong&gt;: a whole word that some installed doctrine artifact
(built-in, org or project pack) is scoped to (for example &lt;code dir=&quot;auto&quot;&gt;Twig&lt;/code&gt;, or a language your own pack
declares).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;So &lt;code dir=&quot;auto&quot;&gt;Python and Twig&lt;/code&gt; is recorded as &lt;code dir=&quot;auto&quot;&gt;python, twig&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;Rust with cargo&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;rust&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;Zig&lt;/code&gt; or a
framework-only answer such as &lt;code dir=&quot;auto&quot;&gt;Django&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;. Words in your other answers (for example
&lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt; in the testing answer) are ignored, so they can no longer turn a Zig project into a
Python one.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Otherwise the other answers are scanned.&lt;/strong&gt; Only when the languages/frameworks answer is
absent, the shipped default or a placeholder (empty, &lt;code dir=&quot;auto&quot;&gt;N/A&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;none&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;TBD&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;language-agnostic&lt;/code&gt;, or several of these joined by commas, semicolons or slashes) does the
built-in detector scan the remaining answers. A hit there is recorded, and a miss records
nothing: no signal, no &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt; and no advisory.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;&lt;/strong&gt; is written only for a real languages/frameworks declaration that neither the
detector nor the vocabulary recognized.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;A language token attached to a preceding &lt;code dir=&quot;auto&quot;&gt;word-&lt;/code&gt; does not count: &lt;code dir=&quot;auto&quot;&gt;librespot-java&lt;/code&gt; does not declare
Java, and &lt;code dir=&quot;auto&quot;&gt;React-TypeScript&lt;/code&gt; does not declare TypeScript (write &lt;code dir=&quot;auto&quot;&gt;TypeScript with React&lt;/code&gt; instead).
A trailing compound such as &lt;code dir=&quot;auto&quot;&gt;Java-based&lt;/code&gt; still counts. Spec Kitty does not interpret sentiment or
negation: a mention counts even if the answer says the tool is only used for helper scripts.
Recognized languages are written to &lt;code dir=&quot;auto&quot;&gt;catalog.languages&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;add-tech-specific-guidelines-to-your-local-charter&quot;&gt;Add tech-specific guidelines to your local charter&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Scaffold a project-level styleguide or toolguide for your language. The stub lands under
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;:&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;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;new&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;styleguide&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;zig-conventions&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Fill in the placeholders, then validate it:&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;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;validate&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;.kittify/charter-packs&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Activate it:&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;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:#ECC48D;--1:#3B61B0&quot;&gt;styleguide&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;zig-conventions&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Do not set &lt;code dir=&quot;auto&quot;&gt;applies_to_languages&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;; the value is reserved and validation rejects it.
Leave the field unset and the artifact applies to your project.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Put narrative rules that do not fit an artifact (build commands, test commands, review
expectations) in &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt;. See
&lt;a href=&quot;/guides/how-to/governance/setup-governance/&quot;&gt;How to Set Up Project Governance&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;To share the same guidelines across several repositories, package them as an org Charter Pack. See
&lt;a href=&quot;/guides/how-to/governance/create-an-org-doctrine-pack/&quot;&gt;How to Create an Org Charter Pack&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;regenerate-after-correcting-the-interview&quot;&gt;Regenerate after correcting the interview&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate&lt;/code&gt; reads the interview by default (&lt;code dir=&quot;auto&quot;&gt;--from-interview&lt;/code&gt;). It re-derives the
languages from the current answers and replaces any hand edit of &lt;code dir=&quot;auto&quot;&gt;catalog.languages&lt;/code&gt;.&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;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;--force&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 keep the recorded languages unchanged, pass &lt;code dir=&quot;auto&quot;&gt;--no-from-interview&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;
without &lt;code dir=&quot;auto&quot;&gt;--resynthesize&lt;/code&gt; and the pack commands recompile without re-deriving, so they also keep the
recorded languages. &lt;code dir=&quot;auto&quot;&gt;charter activate --resynthesize&lt;/code&gt; re-derives the languages the way
&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; does and replaces a hand edit.&lt;/p&gt;
&lt;p&gt;If &lt;code dir=&quot;auto&quot;&gt;available_tools&lt;/code&gt; lists a tool Spec Kitty does not register (for example &lt;code dir=&quot;auto&quot;&gt;zig&lt;/code&gt;), generation prints
that it is not a registered tool id and ignores it. Tool ids are validated separately from project
languages, and the entry never becomes a language.&lt;/p&gt;
&lt;h2 id=&quot;what-spec-kitty-review-reports-for-non-python-missions&quot;&gt;What &lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt; reports for non-Python Missions&lt;/h2&gt;
&lt;p&gt;The dead-code scan analyzes Python sources only. When the changed files hold nothing it supports
(for example only Zig, Go or documentation files), the review reports:&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;text&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:#d6deeb;--1:#403f53&quot;&gt;MISSION_REVIEW_DEAD_CODE_NOT_APPLICABLE&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;The gate is recorded as &lt;code dir=&quot;auto&quot;&gt;skip&lt;/code&gt;, the verdict is &lt;code dir=&quot;auto&quot;&gt;pass_with_notes&lt;/code&gt; and the exit code is 0. This is not a
clean scan: no dead-code analysis ran for those files. Add your own analyzer or test command, and
tech-specific review guidance, to your local charter as described above.&lt;/p&gt;</content>
</entry>
