<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-04-19-6-harness-owned-generated-artifact-charter-handoff/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-04-19-6-harness-owned-generated-artifact-charter-handoff/</id>
  <title>Harness-Owned Generated-Artifact Charter Handoff Contract</title>
  <updated>2026-04-19T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-04-19-6-harness-owned-generated-artifact-charter-handoff/"/>
  <summary>Fixes the layout and identity rules the harness must satisfy for generated doctrine YAML before it is promoted from the staging tree into the live doctrine tree.</summary>
  <content type="html">&lt;h2 id=&quot;context&quot;&gt;Context&lt;/h2&gt;
&lt;p&gt;Charter synthesis is no longer an internal model call. The host LLM or harness
does the reasoning work, reads project evidence, and writes doctrine YAML into
the generated-artifact staging area. &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; then validates those files,
records provenance, emits the project DRG layer, and promotes the results into
the live project doctrine tree.&lt;/p&gt;
&lt;p&gt;The important boundary is simple:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The harness owns &lt;strong&gt;reading evidence and generating doctrine&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; owns &lt;strong&gt;validation, neutrality gating, provenance, staging, and promotion&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This ADR exists to keep that boundary explicit and prevent future drift back to
an in-process model adapter.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;h3 id=&quot;1-canonical-generated-artifact-layout&quot;&gt;1. Canonical generated-artifact layout&lt;/h3&gt;
&lt;p&gt;The harness writes generated doctrine YAML under:&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;.kittify/charter/generated/&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;directives/&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;&amp;#x3C;NNN&gt;-&amp;#x3C;slug&gt;.directive.yaml&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;tactics/&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;&amp;#x3C;slug&gt;.tactic.yaml&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;styleguides/&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;&amp;#x3C;slug&gt;.styleguide.yaml&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 live promoted tree remains:&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;.kittify/doctrine/&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;directives/&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;tactics/&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;styleguides/&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:#d6deeb;--1:#403f53&quot;&gt;.kittify/charter/&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;provenance/&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;synthesis-manifest.yaml&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;2-canonical-identity-rules&quot;&gt;2. Canonical identity rules&lt;/h3&gt;
&lt;p&gt;The harness must match both the filename rule and the YAML identity rule.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Directives use &lt;code dir=&quot;auto&quot;&gt;artifact_id = PROJECT_&amp;#x3C;NNN&gt;&lt;/code&gt; and filename &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;NNN&gt;-&amp;#x3C;slug&gt;.directive.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Tactics use &lt;code dir=&quot;auto&quot;&gt;artifact_id = &amp;#x3C;slug&gt;&lt;/code&gt; and filename &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;.tactic.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Styleguides use &lt;code dir=&quot;auto&quot;&gt;artifact_id = &amp;#x3C;slug&gt;&lt;/code&gt; and filename &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;.styleguide.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;The top-level YAML &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; field must exactly match the target &lt;code dir=&quot;auto&quot;&gt;artifact_id&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Examples:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:PROJECT_001&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/directives/001-project-intent-directive.directive.yaml&lt;/code&gt; (renamed from &lt;code dir=&quot;auto&quot;&gt;001-mission-type-scope-directive&lt;/code&gt;, see the 2026-10-19 amendment)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:testing-philosophy-tactic&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/tactics/testing-philosophy-tactic.tactic.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:python-style-guide&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/styleguides/python-style-guide.styleguide.yaml&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If the file is missing or the YAML &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; does not match, synthesis fails closed.&lt;/p&gt;
&lt;h3 id=&quot;3-evidence-ownership&quot;&gt;3. Evidence ownership&lt;/h3&gt;
&lt;p&gt;Evidence is split on purpose:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; owns evidence declaration and identity:
&lt;ul&gt;
&lt;li&gt;code-reading signals&lt;/li&gt;
&lt;li&gt;configured URL lists&lt;/li&gt;
&lt;li&gt;bundled corpus snapshots&lt;/li&gt;
&lt;li&gt;hashing and provenance fields derived from that evidence&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;The harness owns evidence consumption:
&lt;ul&gt;
&lt;li&gt;reading the repo and the URLs&lt;/li&gt;
&lt;li&gt;deciding how that evidence should shape generated doctrine text&lt;/li&gt;
&lt;li&gt;writing the generated YAML files that &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; will validate&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;No internal HTTP fetcher, browser reader, or model client belongs inside
&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; for this contract.&lt;/p&gt;
&lt;h3 id=&quot;4-operator-cli-sequence&quot;&gt;4. Operator CLI sequence&lt;/h3&gt;
&lt;p&gt;The canonical operator flow is:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Collect interview answers and any configured synthesis inputs.&lt;/li&gt;
&lt;li&gt;Have the harness write generated YAML into &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Validate the handoff without promotion:&lt;/li&gt;
&lt;/ol&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;synthesize&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;--dry-run&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;ol start=&quot;4&quot;&gt;
&lt;li&gt;Promote the validated artifacts into the live tree:&lt;/li&gt;
&lt;/ol&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;synthesize&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;ol start=&quot;5&quot;&gt;
&lt;li&gt;Regenerate one bounded topic after the harness updates the corresponding
generated artifact:&lt;/li&gt;
&lt;/ol&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;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;ol start=&quot;6&quot;&gt;
&lt;li&gt;Inspect operator state, evidence summary, manifest health, and provenance:&lt;/li&gt;
&lt;/ol&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;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;--provenance&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;5-fixture-adapter-policy&quot;&gt;5. Fixture adapter policy&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;--adapter fixture&lt;/code&gt; remains supported only as the deterministic regression
harness. It is not the default runtime path and it is not a production
generation policy.&lt;/p&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;h3 id=&quot;positive&quot;&gt;Positive&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;One inference engine, the host harness already talking to the user.&lt;/li&gt;
&lt;li&gt;No hidden SDK calls or second API-key story inside &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Clear separation between generation and validation.&lt;/li&gt;
&lt;li&gt;Provenance stays trustworthy because the CLI records the exact validated
handoff, not a hidden model invocation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;negative&quot;&gt;Negative&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The harness now has to respect the file layout and identity rules exactly.&lt;/li&gt;
&lt;li&gt;Operator tooling must make the handoff state visible enough that a bad file is
easy to diagnose. That is why &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; and generated-artifact error UX
matter.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;more-information&quot;&gt;More information&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/charter/synthesizer/generated_artifact_adapter.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/charter.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/charter/synthesizer/write_pipeline.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/agent/cli/commands/test_charter_status_cli.py&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-10-19-the-always-synthesized-directive-is-renamed&quot;&gt;Amendment 2026-10-19: the always-synthesized directive is renamed&lt;/h2&gt;
&lt;p&gt;The always-synthesized directive’s slug is now &lt;code dir=&quot;auto&quot;&gt;project-intent-directive&lt;/code&gt; (title “Project Intent Directive”); it was &lt;code dir=&quot;auto&quot;&gt;mission-type-scope-directive&lt;/code&gt; (#6443, mission &lt;code dir=&quot;auto&quot;&gt;charter-synthesis-graph-and-languages-01M59RZ5&lt;/code&gt;). The generated-input layout above is unchanged except for that file name: &lt;code dir=&quot;auto&quot;&gt;directives/&amp;#x3C;NNN&gt;-project-intent-directive.directive.yaml&lt;/code&gt;. The declared &lt;code dir=&quot;auto&quot;&gt;PROJECT_00N&lt;/code&gt; id, the &lt;code dir=&quot;auto&quot;&gt;directive:PROJECT_00N&lt;/code&gt; URN and the interview section label &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; do not change, and synthesis no longer emits a &lt;code dir=&quot;auto&quot;&gt;requires --&gt; mission_type:*&lt;/code&gt; edge for it.&lt;/p&gt;
&lt;p&gt;An existing project converges through one charter-layer helper, &lt;code dir=&quot;auto&quot;&gt;rename_legacy_project_intent_directive&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;charter.activation.api&lt;/code&gt;). It moves the artifact file and this harness input, rewrites the provenance and synthesis-manifest entries (recomputing the manifest hashes), relabels the overlay node, drops the dead edge, rewrites stem tokens in the activation write target and restamps the bundle hash. It never rewrites the artifact body, is idempotent, and refuses on a target collision having changed nothing. The upgrade migration &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_project_intent_directive_rename&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;resynthesize&lt;/code&gt; (before they write, so a legacy file can never leave two files declaring &lt;code dir=&quot;auto&quot;&gt;PROJECT_00N&lt;/code&gt;) both call it. Without the harness-input move, the next synthesize would raise &lt;code dir=&quot;auto&quot;&gt;GeneratedArtifactMissingError&lt;/code&gt; for the new file name.&lt;/p&gt;
&lt;h2 id=&quot;amendment-2026-10-30-what-the-neutrality-gate-judges&quot;&gt;Amendment 2026-10-30: what the neutrality gate judges&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; owns “neutrality gating” (above) without saying what the gate judges.
It judges &lt;strong&gt;scope&lt;/strong&gt;, not vocabulary (#6724, mission
&lt;code dir=&quot;auto&quot;&gt;companion-tactic-neutrality-scope-01M67JR8&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;A generic-scoped artifact addresses every project, so a language-specific term in
it is an unstated assumption about the reader’s stack — that is the bias the gate
exists to stop, and it is the harm FR-008 and FR-012 of
&lt;code dir=&quot;auto&quot;&gt;charter-ownership-consolidation-and-neutrality-hardening-01KPD880&lt;/code&gt; name. An
artifact whose audience is one known stack has no such assumption to make.&lt;/p&gt;
&lt;p&gt;Two halves, both required:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;companion tactic&lt;/strong&gt; — the &lt;code dir=&quot;auto&quot;&gt;tactic:how-we-apply-&amp;#x3C;directive-id&gt;&lt;/code&gt; that
&lt;code dir=&quot;auto&quot;&gt;interview_mapping&lt;/code&gt; expands from the &lt;code dir=&quot;auto&quot;&gt;selected_directives&lt;/code&gt; interview section, one
per explicitly activated directive — is the project’s own application note. It is
still linted, but it may name the banned terms of the project’s &lt;strong&gt;own&lt;/strong&gt; languages:
those observed in the code plus those declared in the interview snapshot
(&lt;code dir=&quot;auto&quot;&gt;language_scope&lt;/code&gt;; org packs contribute none), each expanded to its family. Terms
of any other language stay banned, so a Rust-only project’s companion cannot name
&lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt;. A banned term’s language is its id prefix (&lt;code dir=&quot;auto&quot;&gt;PY-&lt;/code&gt; is Python), owned by
&lt;code dir=&quot;auto&quot;&gt;neutrality.lint._term_language&lt;/code&gt;; a term with an unmapped prefix is never exempted.
Its slug is derived from a directive id and names no language, so the old
slug-component inference could only answer “unknown”, read as “generic”, which is
what refused a companion naming the project’s own test runner.&lt;/li&gt;
&lt;li&gt;When &lt;strong&gt;no&lt;/strong&gt; language is observed and none is declared, nothing is exempted: the
companion is still refused for any banned term. An unconfigured project still gets
no Python default, and &lt;code dir=&quot;auto&quot;&gt;banned_terms.yaml&lt;/code&gt; gains no entry.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Detection reads provenance (&lt;code dir=&quot;auto&quot;&gt;source_section&lt;/code&gt;), which records why the artifact
exists, and the artifact kind — never the slug. The gate’s exemption therefore
cannot admit a styleguide, and cannot admit a tactic authored outside the
companion expansion.&lt;/p&gt;</content>
</entry>
