<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/operations/identity-boundary-ci-gate/">
  <id>https://docs.spec-kitty.ai/operations/identity-boundary-ci-gate/</id>
  <title>Identity-Boundary CI Gate</title>
  <updated>2026-08-26T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/operations/identity-boundary-ci-gate/"/>
  <summary>Retired record of the former drift-detector required CI check, which ran the canonical-registry recognition test on every PR until the sync transport it policed was deleted.</summary>
  <content type="html">&lt;span id=&quot;identity-boundary-ci-gate&quot;&gt;&lt;/span&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Retired (2026-08-26):&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;drift-detector&lt;/code&gt; workflow and its subject were
deleted with the CLI→SaaS sync transport (spec-kitty#5); the canonical-registry
recognition test lived in the deleted &lt;code dir=&quot;auto&quot;&gt;tests/sync/test_diagnose.py&lt;/code&gt;, and the
workflow file &lt;code dir=&quot;auto&quot;&gt;.github/workflows/drift-detector.yml&lt;/code&gt; no longer exists. This
page is retained only as a historical record of the #1247 gate; the Admin
Action below is moot.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;drift-detector&lt;/code&gt; required check used to run
&lt;code dir=&quot;auto&quot;&gt;tests/sync/test_diagnose.py::TestCanonicalRegistryRecognition&lt;/code&gt; on every PR
against &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;. It caught drift between the canonical registries in this
repo and the consumer-recognition contract that
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-end-to-end-testing#41&lt;/code&gt; closed over an 8-RC peeling cycle
(rc14 -&gt; rc22). Its workflow file was
&lt;code dir=&quot;auto&quot;&gt;.github/workflows/drift-detector.yml&lt;/code&gt; (deleted).&lt;/p&gt;
&lt;p&gt;This is one of three coordinated CI gates tracked under
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/1247&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;#1247&lt;/code&gt;&lt;/a&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;drift-detector&lt;/code&gt; here (this repo).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;cross-repo-harness-tests&lt;/code&gt; in &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty-events&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;&lt;/a&gt; - workflow &lt;code dir=&quot;auto&quot;&gt;.github/workflows/cross-repo-harness-tests.yml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;identity-boundary-canary&lt;/code&gt; in &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty-saas&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty-saas&lt;/code&gt;&lt;/a&gt; - workflow &lt;code dir=&quot;auto&quot;&gt;.github/workflows/canary-gate.yml&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This repo’s drift-detector pinned no external SHA. It only ran an in-repo
test. The sibling repos’ workflows pinned a specific commit of
&lt;code dir=&quot;auto&quot;&gt;Priivacy-ai/spec-kitty-end-to-end-testing&lt;/code&gt;; each sibling’s README
&lt;code dir=&quot;auto&quot;&gt;Identity-Boundary CI Gate&lt;/code&gt; section documented the SHA-bump procedure.&lt;/p&gt;
&lt;h2 id=&quot;admin-action&quot;&gt;Admin Action&lt;/h2&gt;
&lt;p&gt;Historical only — the check this section registered no longer exists. When
the gate was live, a repo admin had to register it as required on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/settings/branches&quot;&gt;https://github.com/Priivacy-ai/spec-kitty/settings/branches&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Edit the rule for &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Under “Require status checks to pass before merging”, add the exact name
&lt;code dir=&quot;auto&quot;&gt;drift-detector&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Save.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Until that step is done, the workflow still runs on every PR but its red
status does not block merge.&lt;/p&gt;</content>
</entry>
