<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/development/how-to/create-a-doctrine-artifact/">
  <id>https://docs.spec-kitty.ai/development/how-to/create-a-doctrine-artifact/</id>
  <title>Create a doctrine artifact</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/development/how-to/create-a-doctrine-artifact/"/>
  <summary>A concrete, followable walkthrough for authoring a new doctrine artifact end to end — file location, schema, activation, and the loose-contract asset kind.</summary>
  <content type="html">&lt;span id=&quot;create-a-doctrine-artifact&quot;&gt;&lt;/span&gt;
&lt;p&gt;This guide walks through authoring one new doctrine artifact — from picking a kind through
verifying it is live in governed mission context. It uses a &lt;strong&gt;tactic&lt;/strong&gt; as the worked example
because tactics have the simplest schema and the most built-in precedent to copy from, but the
same six steps apply to the doctrine artifact kinds listed on the &lt;a href=&quot;/architecture/doctrine-kinds/&quot;&gt;doctrine kinds&lt;/a&gt;
page. Two kinds need a different recipe. A &lt;strong&gt;pack skill&lt;/strong&gt; has its own page:
&lt;a href=&quot;/development/how-to/create-a-pack-skill/&quot;&gt;Create and activate a pack skill&lt;/a&gt;. The loose-contract &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; kind (a
shipped blob, not an activatable artifact) has a short recipe at the end:
&lt;a href=&quot;#author-an-asset-a-shipped-blob&quot;&gt;Author an asset&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This guide covers &lt;strong&gt;project-layer&lt;/strong&gt; artifacts — the fast, self-serve path for one project’s own
doctrine. If you are building a shareable &lt;strong&gt;org pack&lt;/strong&gt; (doctrine distributed across multiple
projects), the file layout differs; see
&lt;a href=&quot;/architecture/org-doctrine-layer/&quot;&gt;Understanding the Org Layer of the Charter Offering&lt;/a&gt; after finishing
this guide.&lt;/p&gt;
&lt;h2 id=&quot;prerequisites&quot;&gt;Prerequisites&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A Spec Kitty project with governance set up (&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt; exists — see
&lt;a href=&quot;/guides/how-to/governance/setup-governance/&quot;&gt;How to Set Up Project Governance&lt;/a&gt; if it does not yet).&lt;/li&gt;
&lt;li&gt;The &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; CLI on your &lt;code dir=&quot;auto&quot;&gt;PATH&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;step-1-pick-a-kind-and-its-project-directory&quot;&gt;Step 1: Pick a kind and its project directory&lt;/h2&gt;
&lt;p&gt;Every kind has its own directory under &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;, its own file suffix, and its own
schema. Project-layer directories use singular names for four kinds and plural names for the
rest — this is a real, code-verified asymmetry, not a typo. The mapping has a single canonical
home: &lt;code dir=&quot;auto&quot;&gt;PROJECT_KIND_DIRS&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/artifact_kinds.py&lt;/code&gt; (the charter offering package, imported
by the activation layer and the CLI — there is no second copy to drift). The table below is that
mapping:&lt;/p&gt;











































































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Kind&lt;/th&gt;&lt;th&gt;Project directory&lt;/th&gt;&lt;th&gt;File suffix&lt;/th&gt;&lt;th&gt;Schema&lt;/th&gt;&lt;th&gt;ID field&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;directive&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/directive/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.directive.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive.schema.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/tactic/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.tactic.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic.schema.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/styleguide/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.styleguide.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide.schema.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/procedure/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.procedure.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;procedure.schema.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/toolguides/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.toolguide.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide.schema.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/paradigms/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.paradigm.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm.schema.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/agent_profiles/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.agent.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent-profile.schema.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;profile-id&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/mission_step_contracts/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.step-contract.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;(Pydantic model, no standalone JSON Schema file)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;skill&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/skills/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.skill.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;skill.schema.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;skill&lt;/code&gt; kind does not follow Steps 2–6 below: it needs a &lt;code dir=&quot;auto&quot;&gt;skill_namespace&lt;/code&gt;, a body file, and
it projects files into each tool’s skill root. Follow &lt;a href=&quot;/development/how-to/create-a-pack-skill/&quot;&gt;Create and activate a pack
skill&lt;/a&gt; for it.
Schemas live under &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/schemas/&lt;/code&gt;. If you are working from a project that installed
&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; as a package rather than from this source checkout, the fastest way to see a kind’s
required fields is to copy a real built-in file of that kind and edit it — every built-in
artifact under &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&amp;#x3C;kind-plural&gt;/&lt;/code&gt; is already schema-valid.&lt;/p&gt;
&lt;p&gt;This walkthrough creates a &lt;strong&gt;tactic&lt;/strong&gt;, so the target directory is &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/tactic/&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;step-2-choose-an-id&quot;&gt;Step 2: Choose an ID&lt;/h2&gt;
&lt;p&gt;Doctrine artifact IDs are the config-stem — the filename with its kind suffix stripped — and for
most kinds must match &lt;code dir=&quot;auto&quot;&gt;^[a-z][a-z0-9-]*$&lt;/code&gt; (kebab-case, starting with a letter; see the &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;
pattern in &lt;code dir=&quot;auto&quot;&gt;tactic.schema.yaml&lt;/code&gt;). This ID is what you pass to &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate&lt;/code&gt;, so
pick something you’ll type again: &lt;code dir=&quot;auto&quot;&gt;example-driven-api-design&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;Tactic For API Design&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;step-3-write-the-artifact-file&quot;&gt;Step 3: Write the artifact file&lt;/h2&gt;
&lt;p&gt;Create &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/tactic/example-driven-api-design.tactic.yaml&lt;/code&gt;. A tactic’s schema
(&lt;code dir=&quot;auto&quot;&gt;src/charter/offering/schemas/tactic.schema.yaml&lt;/code&gt;) requires &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;name&lt;/code&gt;, and at
least one step (each step requires at least a &lt;code dir=&quot;auto&quot;&gt;title&lt;/code&gt;):&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;schema_version&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;1.0&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&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:#7FDBCA;--1:#111111&quot;&gt;id&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;example-driven-api-design&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:#7FDBCA;--1:#111111&quot;&gt;name&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;Example-Driven API Design&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:#7FDBCA;--1:#111111&quot;&gt;purpose&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;&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:#ECC48D;--1:#3B61B0&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;Design a new API surface by writing the concrete request/response examples first,&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:#ECC48D;--1:#3B61B0&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;then deriving the interface from what makes the examples read cleanly. Prevents&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:#ECC48D;--1:#3B61B0&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;designing an interface that is technically coherent but awkward for real callers.&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:#7FDBCA;--1:#111111&quot;&gt;steps&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:#7FDBCA;--1:#111111&quot;&gt;title&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;Write three realistic call examples&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;description&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;&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:#ECC48D;--1:#3B61B0&quot;&gt;      &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;Before writing any interface signature, write out three concrete example calls a&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:#ECC48D;--1:#3B61B0&quot;&gt;      &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;real caller would make, including the exact request and response shape you want&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:#ECC48D;--1:#3B61B0&quot;&gt;      &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;them to see.&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;examples&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:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;Good: a runnable curl example with real field values, not placeholders.&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&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:#7FDBCA;--1:#111111&quot;&gt;title&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;Derive the interface from the examples&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;description&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;&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:#ECC48D;--1:#3B61B0&quot;&gt;      &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;Only after the examples read naturally, write the interface (types, endpoint&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:#ECC48D;--1:#3B61B0&quot;&gt;      &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;names, parameters) that would make those exact examples true.&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:#7FDBCA;--1:#111111&quot;&gt;title&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;Check for awkward callers&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;description&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;&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:#ECC48D;--1:#3B61B0&quot;&gt;      &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;Re-read each example as if you were a caller who has never seen the design.&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:#ECC48D;--1:#3B61B0&quot;&gt;      &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;If an example needs a comment to explain why a field is shaped the way it is,&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:#ECC48D;--1:#3B61B0&quot;&gt;      &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;the interface needs another pass.&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:#7FDBCA;--1:#111111&quot;&gt;failure_modes&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:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;Skipping straight to the interface and retrofitting examples afterward — the examples end up justifying the design instead of shaping it.&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Every field here maps directly onto the schema: &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; must be the literal string
&lt;code dir=&quot;auto&quot;&gt;&quot;1.0&quot;&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;steps&lt;/code&gt; is a non-empty list of objects with at least a &lt;code dir=&quot;auto&quot;&gt;title&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;purpose&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;failure_modes&lt;/code&gt; are optional but recommended (see the real built-in
&lt;code dir=&quot;auto&quot;&gt;problem-decomposition.tactic.yaml&lt;/code&gt; cited on the &lt;a href=&quot;/architecture/doctrine-kinds/#tactic&quot;&gt;doctrine kinds&lt;/a&gt; page
for a fuller example with &lt;code dir=&quot;auto&quot;&gt;references&lt;/code&gt; to other tactics).&lt;/p&gt;
&lt;p&gt;For a different kind, swap the required fields per the table in Step 1 — for example an
&lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; additionally requires &lt;code dir=&quot;auto&quot;&gt;purpose&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;specialization&lt;/code&gt;, and either &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;roles&lt;/code&gt;
(see &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/schemas/agent-profile.schema.yaml&lt;/code&gt;), and its ID field is &lt;code dir=&quot;auto&quot;&gt;profile-id&lt;/code&gt;, not
&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;step-4-confirm-the-artifact-is-discovered&quot;&gt;Step 4: Confirm the artifact is discovered&lt;/h2&gt;
&lt;p&gt;The project layer is read directly off disk — no separate “import” step. Confirm your new
file is found and parses:&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;list&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;--show-available&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Your new tactic should appear as an available-but-not-yet-activated ID under the &lt;code dir=&quot;auto&quot;&gt;tactic&lt;/code&gt; row.
If it does not appear, re-check the filename suffix (&lt;code dir=&quot;auto&quot;&gt;.tactic.yaml&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;.yaml&lt;/code&gt;) and the
directory (&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/tactic/&lt;/code&gt;, singular).&lt;/p&gt;
&lt;h2 id=&quot;step-5-activate-it&quot;&gt;Step 5: Activate it&lt;/h2&gt;
&lt;p&gt;An artifact existing on disk is not the same as it being &lt;strong&gt;active&lt;/strong&gt; — activation is what makes
an artifact eligible for context injection into governed mission actions. Activate by kind and
ID:&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;tactic&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;example-driven-api-design&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 is a fast, config-only write to &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;activated_tactics&lt;/code&gt; list (see
&lt;code dir=&quot;auto&quot;&gt;plan_activation&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;commit_plan&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;src/charter/activation/activation_engine.py&lt;/code&gt;) — it does not by itself
regenerate the derived bundle. If your new tactic references other artifacts (via a &lt;code dir=&quot;auto&quot;&gt;references&lt;/code&gt;
field) that are not yet activated, the command warns you and suggests &lt;code dir=&quot;auto&quot;&gt;--cascade&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:#919F9F;--1:#5F636F&quot;&gt;# Activate the tactic and everything it references, in one pass&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:#ECC48D;--1:#3B61B0&quot;&gt;tactic&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;example-driven-api-design&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;--cascade&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;all&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;# Also eagerly refresh the derived bundle/DRG immediately (otherwise this&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:#919F9F;--1:#5F636F&quot;&gt;# happens lazily on the next synthesize)&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:#ECC48D;--1:#3B61B0&quot;&gt;tactic&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;example-driven-api-design&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;--resynthesize&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Kinds that skip explicit activation.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt; do not
use the &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; list at all — all built-ins for those two kinds are available
without an activation step (&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter list --all&lt;/code&gt; reports them as
“All built-ins — no explicit activation”). If you are authoring one of those two kinds, Steps
4–5 collapse into “confirm the file is present and well-formed”; there is no &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;
call to make.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;step-6-verify-it-took-effect&quot;&gt;Step 6: Verify it took effect&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;# Confirm the ID now shows under &quot;Activated&quot; for its kind&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;list&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 overall charter health&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;/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 the artifact actually surfaces in a real mission action&apos;s context —&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:#919F9F;--1:#5F636F&quot;&gt;# pick an action your tactic is relevant to&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;specify&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; reports the bundle as stale, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter synthesize&lt;/code&gt; (dry-run
first) to promote it — see
&lt;a href=&quot;/guides/how-to/governance/synthesize-doctrine/&quot;&gt;How to Synthesize and Maintain Doctrine&lt;/a&gt; for the full
synthesis workflow. If something looks wrong at any step, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; and
&lt;a href=&quot;/guides/how-to/governance/troubleshoot-charter/&quot;&gt;Troubleshooting Charter Failures&lt;/a&gt; are the first places to
check.&lt;/p&gt;
&lt;h2 id=&quot;modeling-relationships-between-artifacts-including-tension&quot;&gt;Modeling relationships between artifacts, including tension&lt;/h2&gt;
&lt;p&gt;Every relationship between doctrine artifacts — obligation (&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;), lineage (&lt;code dir=&quot;auto&quot;&gt;specializes_from&lt;/code&gt;), augmentation (&lt;code dir=&quot;auto&quot;&gt;enhances&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;overrides&lt;/code&gt;), and tension (&lt;code dir=&quot;auto&quot;&gt;in_tension_with&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reconciles_tension&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;rejects&lt;/code&gt;) — is an authored &lt;strong&gt;DRG edge&lt;/strong&gt; in a &lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt; fragment, never a
field on the artifact body. The full authoring reference — worked examples
for every relation, plus the URN-ordering mechanic for &lt;code dir=&quot;auto&quot;&gt;in_tension_with&lt;/code&gt; — is
&lt;a href=&quot;/architecture/doctrine-relationships/&quot;&gt;Doctrine relationships&lt;/a&gt;; see
its &lt;a href=&quot;/architecture/doctrine-relationships/&quot;&gt;“Tension vocabulary” section&lt;/a&gt;
for how to model two co-valid artifacts that disagree (for example
DIRECTIVE_024’s locality-of-change vs. DIRECTIVE_025’s boy-scout rule) and
how to bridge a tension pair with a reconciler.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;opposed_by&lt;/code&gt; is retired, not an authoring option.&lt;/strong&gt; Use &lt;code dir=&quot;auto&quot;&gt;in_tension_with&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;reconciles_tension&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;rejects&lt;/code&gt; instead — see the linked reference above for
the full semantics. It survives only as a legacy input an unmigrated
org/downstream pack may still carry; &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate rewrite-opposed-by --pack &amp;#x3C;path&gt;&lt;/code&gt; rewrites those legacy entries into the correct typed edges
(idempotent, safe to run repeatedly).&lt;/p&gt;
&lt;h2 id=&quot;undoing-this&quot;&gt;Undoing this&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;deactivate&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;tactic&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;example-driven-api-design&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Deactivating removes the ID from &lt;code dir=&quot;auto&quot;&gt;activated_tactics&lt;/code&gt;; it does not delete the file. Delete
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/tactic/example-driven-api-design.tactic.yaml&lt;/code&gt; directly if you want the
artifact gone entirely.&lt;/p&gt;
&lt;h2 id=&quot;author-an-asset-a-shipped-blob&quot;&gt;Author an asset (a shipped blob)&lt;/h2&gt;
&lt;p&gt;The walkthrough above covers the &lt;strong&gt;activation&lt;/strong&gt; kinds. The &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; kind works differently and
gets its own short recipe here — it is the canonical way to ship an image, font, template fixture,
or an executable script (a lint, a hook) to a downstream repo, instead of naming a repo-local
&lt;code dir=&quot;auto&quot;&gt;scripts/…&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;.github/…&lt;/code&gt; path a consumer does not have (see
&lt;a href=&quot;/development/how-to/review-gates/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;review-gates.md&lt;/code&gt;&lt;/a&gt;). An asset is a &lt;strong&gt;blob&lt;/strong&gt; plus a &lt;strong&gt;sidecar
manifest&lt;/strong&gt;; there is no schema on the blob and — unlike the activation kinds above — &lt;strong&gt;no
&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; step&lt;/strong&gt;. It is delivered when a reachable artifact points at it, not when you
activate it (see &lt;a href=&quot;/architecture/doctrine-kinds/#delivery-verdicts-which-kinds-reach-a-mission&quot;&gt;Delivery verdicts&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;This recipe is executable against a fresh project — copy it verbatim.&lt;/p&gt;
&lt;h3 id=&quot;step-a-place-the-blob&quot;&gt;Step A: place the blob&lt;/h3&gt;
&lt;p&gt;The project-layer asset directory is &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/assets/&lt;/code&gt; (from the single canonical
&lt;code dir=&quot;auto&quot;&gt;PROJECT_KIND_DIRS&lt;/code&gt; mapping). Put the blob there. For a worked example, a shared release checklist:&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;mkdir&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;-p&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/assets&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:#C5E478;--1:#3B61B0&quot;&gt;printf&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&apos;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;# Release checklist\n- [ ] Tests green\n&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&apos;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;&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;.kittify/charter-packs/assets/team-release-checklist.md&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;h3 id=&quot;step-b-write-the-sidecar-manifest&quot;&gt;Step B: write the sidecar manifest&lt;/h3&gt;
&lt;p&gt;Alongside the blob, create a manifest named &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;blob&gt;.asset.yaml&lt;/code&gt; — here
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/assets/team-release-checklist.md.asset.yaml&lt;/code&gt;. The manifest is the validated
surface; it requires &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mime&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt;, with an optional &lt;code dir=&quot;auto&quot;&gt;title&lt;/code&gt;:&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;id&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;team-release-checklist&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:#7FDBCA;--1:#111111&quot;&gt;mime&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;text/markdown&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:#7FDBCA;--1:#111111&quot;&gt;path&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;team-release-checklist.md&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:#7FDBCA;--1:#111111&quot;&gt;title&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;Team release checklist&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Field rules (&lt;code dir=&quot;auto&quot;&gt;charter.offering.assets.models.AssetManifest&lt;/code&gt;, enforced by the pack validator):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; — a stable identifier, unique per pack per kind. This is what you resolve by.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mime&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;type/subtype&lt;/code&gt; form (e.g. &lt;code dir=&quot;auto&quot;&gt;text/markdown&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;image/png&lt;/code&gt;); when the extension implies a
type, &lt;code dir=&quot;auto&quot;&gt;mime&lt;/code&gt; must agree with it.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt; — the blob’s path &lt;strong&gt;relative to the &lt;code dir=&quot;auto&quot;&gt;assets/&lt;/code&gt; root&lt;/strong&gt;. It must resolve &lt;em&gt;inside&lt;/em&gt; that root:
an absolute path, a &lt;code dir=&quot;auto&quot;&gt;..&lt;/code&gt;-escape, or a symlink that leaves the root is rejected (NFR-006
containment).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;title&lt;/code&gt; — optional human-facing display name.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;step-c-resolve-it&quot;&gt;Step C: resolve it&lt;/h3&gt;
&lt;p&gt;Assets are not activated — they are resolved on demand, from any installation, with no charter
step. Confirm the asset is discoverable and resolves to your blob:&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;# List every resolvable asset and its source tier (built-in / org / project)&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;pack&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;asset&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;list&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;# Resolve one identifier to a filesystem path (exit 0 on success;&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:#919F9F;--1:#5F636F&quot;&gt;# an unknown id exits non-zero and names the id)&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;pack&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;asset&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;path&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;team-release-checklist&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 &lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt; command prints the absolute path to your blob and exits &lt;code dir=&quot;auto&quot;&gt;0&lt;/code&gt;. Downstream code (a mission
step, a hook, a shipped lint) consumes the asset by calling &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack asset path &amp;#x3C;id&gt;&lt;/code&gt;
and reading the file at the returned path — never by hard-coding a source-tree path. A more
specific tier wins: a project or org asset of the same &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; shadows the built-in, and the shadow is
reported by &lt;code dir=&quot;auto&quot;&gt;asset list&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;There is nothing to undo — no activation entry was written. Delete the blob and its
&lt;code dir=&quot;auto&quot;&gt;*.asset.yaml&lt;/code&gt; manifest to remove the asset entirely.&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;/architecture/doctrine-kinds/&quot;&gt;Doctrine artifact kinds&lt;/a&gt; — what each kind is for, with a
real example of each.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/development/how-to/create-a-pack-skill/&quot;&gt;Create and activate a pack skill&lt;/a&gt; — author a &lt;code dir=&quot;auto&quot;&gt;skill&lt;/code&gt; and project it
into each configured tool.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/doctrine-relationships/&quot;&gt;Doctrine relationships&lt;/a&gt; — the full DRG relation
reference, including the tension vocabulary (&lt;code dir=&quot;auto&quot;&gt;in_tension_with&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reconciles_tension&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;rejects&lt;/code&gt;) that supersedes the retired &lt;code dir=&quot;auto&quot;&gt;opposed_by&lt;/code&gt; field.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/org-doctrine-layer/&quot;&gt;Understanding the Org Layer of the Charter Offering&lt;/a&gt; — how to package
and share doctrine artifacts across multiple projects instead of authoring them project-local.&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; — the broader
synthesis/resynthesis maintenance workflow this guide’s Step 6 hands off to.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
