<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/contracts/">
  <id>https://docs.spec-kitty.ai/contracts/</id>
  <title>Contracts</title>
  <updated>2026-08-14T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/contracts/"/>
  <summary>Contract-ownership boundary registry for Spec Kitty: the seeded contract manifest and its validation schema, checked by the doctor contracts gate.</summary>
  <content type="html">&lt;span id=&quot;contracts&quot;&gt;&lt;/span&gt;
&lt;p&gt;This section holds the &lt;strong&gt;Contract Registry&lt;/strong&gt; for the contract-ownership
boundary (#2441): the single, canonical manifest of ownership contracts that
Spec Kitty enforces, plus the schema that validates it.&lt;/p&gt;
&lt;p&gt;It also holds the &lt;strong&gt;handoff packet&lt;/strong&gt; payload contract that external
requirements tools use to seed &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; without losing
requirement identity:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;handoff-packet-v1.md&lt;/code&gt; — optional YAML-frontmatter overlay on a Markdown
brief. Frontmatter is additive; unknown versions degrade to prose intake.
Parser: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/intake/packet.py&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;files&quot;&gt;Files&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;contract-registry.yaml&lt;/code&gt; — the seeded contract manifest. Each record declares
a contract’s kind, status, enforcement level, owning boundary, semver, and
tracker references, along with the anchors that pin it to the code or docs it
governs.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;contract-registry-schema.yaml&lt;/code&gt; — the schema every registry record is
validated against: required fields, allowed &lt;code dir=&quot;auto&quot;&gt;kind&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;enforcement&lt;/code&gt;
ranges, well-formed semver and tracker references, resolvable anchors, and the
DIR-041 self-consistency rule that forbids positional &lt;code dir=&quot;auto&quot;&gt;file:line&lt;/code&gt; anchoring.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;handoff-packet-v1.md&lt;/code&gt; — optional YAML-frontmatter overlay that lets an
upstream requirements tool seed &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; without losing FR/AC
identity. Unknown versions degrade to prose intake.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;validation&quot;&gt;Validation&lt;/h2&gt;
&lt;p&gt;The registry is validated by the CLI gate:&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;plaintext&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;spec-kitty doctor contracts&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Structural validation is the only enforcing gate in v1 — a malformed record or a
positional &lt;code dir=&quot;auto&quot;&gt;file:line&lt;/code&gt; anchor exits non-zero. The retirement absence-sweep is
advisory. See &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor contracts --help&lt;/code&gt; (documented in
&lt;code dir=&quot;auto&quot;&gt;docs/api/cli-commands.md&lt;/code&gt;) for exit codes and options.&lt;/p&gt;</content>
</entry>
