Contracts
This section holds the Contract Registry for the contract-ownership boundary (#2441): the single, canonical manifest of ownership contracts that Spec Kitty enforces, plus the schema that validates it.
It also holds the handoff packet payload contract that external
requirements tools use to seed /spec-kitty.specify without losing
requirement identity:
handoff-packet-v1.md— optional YAML-frontmatter overlay on a Markdown brief. Frontmatter is additive; unknown versions degrade to prose intake. Parser:src/specify_cli/intake/packet.py.
Files
contract-registry.yaml— 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.contract-registry-schema.yaml— the schema every registry record is validated against: required fields, allowedkind/status/enforcementranges, well-formed semver and tracker references, resolvable anchors, and the DIR-041 self-consistency rule that forbids positionalfile:lineanchoring.handoff-packet-v1.md— optional YAML-frontmatter overlay that lets an upstream requirements tool seed/spec-kitty.specifywithout losing FR/AC identity. Unknown versions degrade to prose intake.
Validation
The registry is validated by the CLI gate:
spec-kitty doctor contractsStructural validation is the only enforcing gate in v1 — a malformed record or a
positional file:line anchor exits non-zero. The retirement absence-sweep is
advisory. See spec-kitty doctor contracts --help (documented in
docs/api/cli-commands.md) for exit codes and options.