<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/migrations/tracker-egress-refusal/">
  <id>https://docs.spec-kitty.ai/migrations/tracker-egress-refusal/</id>
  <title>Migration: Tracker Egress Refusal</title>
  <updated>2026-08-04T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/migrations/tracker-egress-refusal/"/>
  <summary>Why every existing beads/fp tracker binding now needs a recorded consent decision, what the two channels are, and how to remediate each refusing state.</summary>
  <content type="html">&lt;blockquote&gt;
&lt;p&gt;Migration note: This page documents a migration path or historical transition. It is not the current 3.2 happy path.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;span id=&quot;migration-tracker-egress-refusal&quot;&gt;&lt;/span&gt;
&lt;p&gt;&lt;strong&gt;Status&lt;/strong&gt;: Shipped with mission &lt;code dir=&quot;auto&quot;&gt;tracker-egress-refusal-3108-01KYWF1R&lt;/code&gt;.
&lt;strong&gt;Issue&lt;/strong&gt;: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3108&quot;&gt;Priivacy-ai/spec-kitty#3108&lt;/a&gt;
&lt;strong&gt;Audience&lt;/strong&gt;: Operators with an existing &lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;- or &lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt;-bound project
(&lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker bind --provider beads&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;--provider fp&lt;/code&gt;) upgrading past
this mission.&lt;/p&gt;
&lt;h2 id=&quot;what-changed-and-why-it-breaks-you&quot;&gt;What Changed and Why It Breaks You&lt;/h2&gt;
&lt;p&gt;Before this mission, a &lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt; tracker binding reached the tracker
binary with &lt;strong&gt;no consent question asked at all&lt;/strong&gt;. &lt;code dir=&quot;auto&quot;&gt;LocalTrackerService&lt;/code&gt; held
zero consent references, so &lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker sync pull&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;push&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;run&lt;/code&gt;
shipped issue titles, bodies, labels and assignees as &lt;code dir=&quot;auto&quot;&gt;argv&lt;/code&gt; of an
operator-named executable even on a project whose committed
&lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; said &lt;code dir=&quot;auto&quot;&gt;sync: {enabled: false}&lt;/code&gt; — the hosted-sync refusal
did not stop the local one, because nothing local was ever gated.&lt;/p&gt;
&lt;p&gt;That gap is now closed, and closing it is a &lt;strong&gt;breaking change&lt;/strong&gt;: a local
tracker binding now requires a &lt;strong&gt;recorded decision at one of two consent
channels&lt;/strong&gt;, and &lt;strong&gt;absence of both channels denies&lt;/strong&gt;. If your project has
never recorded hosted-sync consent (no &lt;code dir=&quot;auto&quot;&gt;sync.enabled&lt;/code&gt;, no
&lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt;) and has never recorded a &lt;code dir=&quot;auto&quot;&gt;tracker.egress&lt;/code&gt; decision,
&lt;code dir=&quot;auto&quot;&gt;sync pull&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;sync push&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;sync run&lt;/code&gt; on that binding &lt;strong&gt;stop working on
upgrade&lt;/strong&gt; until you record one of the two. Nothing about your binding itself
changed — the &lt;code dir=&quot;auto&quot;&gt;tracker:&lt;/code&gt; block, the provider, the workspace, the mapped
issues, are all untouched. Only the consent decision is new, and it is
mandatory.&lt;/p&gt;
&lt;h2 id=&quot;the-two-consent-channels-and-what-absence-means-at-each&quot;&gt;The Two Consent Channels, and What Absence Means at Each&lt;/h2&gt;
&lt;p&gt;Two channels are consulted, and they are &lt;strong&gt;not parallel switches&lt;/strong&gt; — absence
means something different at each one:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Channel 1 — hosted-sync consent.&lt;/strong&gt; The existing consent chain, recorded
via &lt;code dir=&quot;auto&quot;&gt;sync.enabled: true&lt;/code&gt; in this project’s own &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, or by
running &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt;. Keyed on this project’s identity.
&lt;strong&gt;Absence denies.&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Channel 2 — &lt;code dir=&quot;auto&quot;&gt;tracker.egress&lt;/code&gt;.&lt;/strong&gt; A new key in the &lt;code dir=&quot;auto&quot;&gt;tracker:&lt;/code&gt; block of this
&lt;strong&gt;project’s own committed&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;. It holds &lt;strong&gt;exactly one
of two strings&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;refused&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;permitted&lt;/code&gt;. &lt;strong&gt;Absence is the key being
missing&lt;/strong&gt; — nothing is recorded, and the decision &lt;strong&gt;defers to Channel 1&lt;/strong&gt;
instead of denying on its own.&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;tracker&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&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;egress&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;permitted&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;   &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# or: refused&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;A malformed &lt;code dir=&quot;auto&quot;&gt;tracker:&lt;/code&gt; block — &lt;code dir=&quot;auto&quot;&gt;tracker: &quot;yes&quot;&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tracker: [a, b]&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tracker: 3&lt;/code&gt;, or a bare &lt;code dir=&quot;auto&quot;&gt;tracker:&lt;/code&gt; with nothing under it — is treated as
&lt;strong&gt;absence, not a fault&lt;/strong&gt;: the block is not the key, so the key is simply
missing and Channel 2 still defers to Channel 1.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Absence of &lt;strong&gt;both&lt;/strong&gt; channels denies. Recording a decision at either one is
enough to stop the refusal — you do not need both.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The coercion this two-way design removes.&lt;/strong&gt; Both routes to a Channel-1
record — hand-authoring &lt;code dir=&quot;auto&quot;&gt;sync.enabled: true&lt;/code&gt;, or running
&lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt; — grant &lt;strong&gt;hosted-sync&lt;/strong&gt; consent, nothing narrower.
Without a Channel-2 grant that stands on its own, the only way to keep a
&lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt; binding alive after this upgrade would have been &lt;em&gt;“consent to
hosted sync, or lose your local tracker.”&lt;/em&gt; That is not what this mission
ships. Recording &lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt; keeps your local tracker binding
working and grants &lt;strong&gt;nothing&lt;/strong&gt; to anyone else — the subprocess it authorizes
is the one already named in your own machine-global tracker credential file,
never spec-kitty’s hosted service. You record one key in a file you already
own, and you consent to hosted sync exactly as much as you did before writing
it: not at all, unless you separately say so.&lt;/p&gt;
&lt;h2 id=&quot;how-to-tell-which-channel-is-refusing-you&quot;&gt;How to Tell Which Channel Is Refusing You&lt;/h2&gt;
&lt;p&gt;Run:&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;sync&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;doctor&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 checkout prints a &lt;strong&gt;Tracker egress&lt;/strong&gt; block with &lt;strong&gt;one row per
destination&lt;/strong&gt; — the local subprocess destination (&lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt;) and the
hosted service destination (&lt;code dir=&quot;auto&quot;&gt;jira&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;linear&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;github&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;gitlab&lt;/code&gt;) — naming which
channel is refusing on each row, plus the exact remedy text. Check this
first, before guessing.&lt;/p&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt; is the diagnostic surface for this, deliberately, rather than a
&lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker&lt;/code&gt;-side command: the &lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker&lt;/code&gt; command group is
&lt;strong&gt;conditionally registered&lt;/strong&gt; and does not exist at all unless hosted SaaS
sync is armed on the machine (&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC=1&lt;/code&gt;). A
&lt;code dir=&quot;auto&quot;&gt;tracker&lt;/code&gt;-side diagnostic would be unreachable in exactly the configuration
where an operator refusing hosted sync most needs it. &lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt; has no
such precondition.&lt;/p&gt;
&lt;h2 id=&quot;the-three-channel-1-states-and-their-remedies&quot;&gt;The Three Channel-1 States and Their Remedies&lt;/h2&gt;
&lt;p&gt;Channel 1 can be in exactly one of three states, and each has its own,
distinct remedy:&lt;/p&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Channel-1 state&lt;/th&gt;&lt;th&gt;Meaning&lt;/th&gt;&lt;th&gt;Remedy&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;No record&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Nothing was recorded for this project at Channel 1.&lt;/td&gt;&lt;td&gt;Record &lt;code dir=&quot;auto&quot;&gt;sync.enabled: true&lt;/code&gt; in this project’s own &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;; &lt;strong&gt;or&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt;; &lt;strong&gt;or&lt;/strong&gt; record &lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt; (needs no project identity).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Recorded refusal&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A Channel-1 refusal exists (for example, a committed &lt;code dir=&quot;auto&quot;&gt;sync: {enabled: false}&lt;/code&gt;).&lt;/td&gt;&lt;td&gt;Change the recorded decision to &lt;code dir=&quot;auto&quot;&gt;sync.enabled: true&lt;/code&gt;; &lt;strong&gt;or&lt;/strong&gt; record &lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Not consentable&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;This checkout has no project identity at all, so hosted-sync consent cannot be recorded for it.&lt;/td&gt;&lt;td&gt;Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; in this checkout first — see the next section; &lt;strong&gt;or&lt;/strong&gt; record &lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt;, which needs no identity at all.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;strong&gt;Record &lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt; is the only remedy that works in every
one of these three states without a project identity.&lt;/strong&gt; If you want the
shortest path back to a working local binding and do not want to think about
which of the three states you are in, this is it.&lt;/p&gt;
&lt;h2 id=&quot;the-identity-less-checkout&quot;&gt;The Identity-less Checkout&lt;/h2&gt;
&lt;p&gt;This state deserves its own callout, because the hosted refusal text still
points an identity-less checkout at the wrong command.&lt;/p&gt;
&lt;p&gt;If &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt; fails, or you hand-author &lt;code dir=&quot;auto&quot;&gt;sync.enabled: true&lt;/code&gt;
and the binding &lt;strong&gt;still&lt;/strong&gt; denies, this checkout has no project identity —
there is no &lt;code dir=&quot;auto&quot;&gt;project.uuid&lt;/code&gt; for a consent decision to attach to. In this
state, &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;sync.enabled: true&lt;/code&gt; on its own does nothing&lt;/strong&gt;: Channel 1 cannot
record a decision for a project that does not yet have an identity to record
one against.&lt;/p&gt;
&lt;p&gt;The remedy is &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt;&lt;/strong&gt;, run in this checkout, which mints that
identity. Once it exists, the “no record” remedies above become available —
record &lt;code dir=&quot;auto&quot;&gt;sync.enabled: true&lt;/code&gt; or run &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt;. Or skip identity
entirely and record &lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt;, which needs no project
identity at all and is the faster path if hosted sync was never something you
wanted.&lt;/p&gt;
&lt;p&gt;Without this state named on its own, the operator-facing advice would tell
this checkout to do exactly what it just tried and failed at — an outage the
operator cannot act on. &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync doctor&lt;/code&gt; names this state explicitly
as &lt;strong&gt;not consentable&lt;/strong&gt; so you do not have to guess which of the three states
above you are in.&lt;/p&gt;
&lt;h2 id=&quot;what-permitted-does-and-does-not-do&quot;&gt;What &lt;code dir=&quot;auto&quot;&gt;permitted&lt;/code&gt; Does and Does Not Do&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt; behaves differently depending on which
destination is asked, and this is a deliberate, decided design, not an
inconsistency:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;At the local subprocess destination&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;permitted&lt;/code&gt; is an
&lt;strong&gt;affirmative grant&lt;/strong&gt; that works &lt;strong&gt;independently of hosted-sync consent&lt;/strong&gt;.
You can keep a local tracker binding alive without ever opting this
repository into spec-kitty’s hosted SaaS.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;At the hosted service destination&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;jira&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;linear&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;github&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;gitlab&lt;/code&gt;, and anything reached with &lt;code dir=&quot;auto&quot;&gt;--provider &amp;#x3C;saas&gt;&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;permitted&lt;/code&gt;
&lt;strong&gt;grants nothing&lt;/strong&gt;. It can only narrow an already-permitted path further —
it can never be the reason a hosted-service request is allowed through.
Hosted-sync consent (Channel 1) remains a hard prerequisite there, because
that transport sends to &lt;strong&gt;spec-kitty’s own hosted service&lt;/strong&gt; — bearer-token
&lt;code dir=&quot;auto&quot;&gt;/api/v1/tracker/...&lt;/code&gt; endpoints holding the connector and relaying to the
provider — not to anything local to your machine.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;This is a decided limitation, not an oversight.&lt;/strong&gt; A SaaS tracker binding
without hosted-sync consent is &lt;strong&gt;not delivered&lt;/strong&gt; by this mission, and is not
planned as an accidental gap to be closed later without a separate decision:
recording a local, project-owned key must never be able to authorize traffic
to spec-kitty’s own service on its own.&lt;/p&gt;
&lt;h2 id=&quot;the-map-list-split&quot;&gt;The &lt;code dir=&quot;auto&quot;&gt;map list&lt;/code&gt; Split&lt;/h2&gt;
&lt;p&gt;On the same refusing project, &lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker map list&lt;/code&gt; (no &lt;code dir=&quot;auto&quot;&gt;--provider&lt;/code&gt;)
&lt;strong&gt;succeeds&lt;/strong&gt;, while &lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker map list --provider jira&lt;/code&gt; &lt;strong&gt;refuses&lt;/strong&gt;.
Both are correct. &lt;code dir=&quot;auto&quot;&gt;issue-search --provider&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;list-tickets --provider&lt;/code&gt;
behave the same way.&lt;/p&gt;
&lt;p&gt;This is not a bug: &lt;strong&gt;the gate follows the destination, not the subcommand
name.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;map list&lt;/code&gt; with no provider reads local state and touches no
transport at all; &lt;code dir=&quot;auto&quot;&gt;map list --provider jira&lt;/code&gt; crosses the hosted transport,
so it is gated exactly as any other hosted-destination call is.&lt;/p&gt;
&lt;h2 id=&quot;a-typo-refuses&quot;&gt;A Typo Refuses&lt;/h2&gt;
&lt;p&gt;The Channel-2 value set is closed to exactly two strings: &lt;code dir=&quot;auto&quot;&gt;refused&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;permitted&lt;/code&gt;. There is &lt;strong&gt;no case-folding and no synonym list&lt;/strong&gt; — not
&lt;code dir=&quot;auto&quot;&gt;Refused&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;REFUSED&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;refuse&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;deny&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;yes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;on&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;1&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;true&lt;/code&gt;,
not a number, not &lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt;, not an empty string, not a mapping, not a list.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Anything else present at the &lt;code dir=&quot;auto&quot;&gt;tracker.egress&lt;/code&gt; key is a fault, and a fault
refuses tracker egress at both destinations.&lt;/strong&gt; This is intended, not a side
effect: on a confidentiality control, the only safe reading of a value nobody
defined is refusal — the alternative is that a mis-spelling silently
permits. The cost is that a typo can take a previously-working local binding
offline; the refusal message names the offending value verbatim, together
with both legal values, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync doctor&lt;/code&gt; renders the same
wording, so fixing the typo does not require reading source.&lt;/p&gt;
&lt;h2 id=&quot;which-commands-are-gated&quot;&gt;Which Commands Are Gated&lt;/h2&gt;
&lt;p&gt;Only &lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker sync pull&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;sync push&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;sync run&lt;/code&gt; consult the
Channel-1/Channel-2 join described above. &lt;code dir=&quot;auto&quot;&gt;tracker status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tracker bind&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tracker unbind&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;tracker map add&lt;/code&gt; construct no connector, run no
subprocess, and reach no transport at all — they are &lt;strong&gt;not&lt;/strong&gt; gated, so a
refusing project keeps its local-only commands fully working.&lt;/p&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;tracker bind --provider beads&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;--provider fp&lt;/code&gt; also does not require
&lt;strong&gt;hosted readiness&lt;/strong&gt; (auth, &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL&lt;/code&gt;, reachability) — a distinct
pre-flight from the Channel-1/Channel-2 gate above, but one that a local bind
must equally not be blocked by for this section’s promise to hold. An
unauthenticated project can &lt;code dir=&quot;auto&quot;&gt;tracker bind&lt;/code&gt; a local provider and keep working;
only a SaaS-provider bind (&lt;code dir=&quot;auto&quot;&gt;--provider jira&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;linear&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;github&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;gitlab&lt;/code&gt;) still
requires it.&lt;/p&gt;
&lt;h2 id=&quot;a-recorded-decision-outlives-its-binding&quot;&gt;A Recorded Decision Outlives Its Binding&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;tracker bind&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;rebind&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;unbind&lt;/code&gt; all preserve a committed
&lt;code dir=&quot;auto&quot;&gt;tracker.egress&lt;/code&gt; decision. Unbinding a provider does not erase a recorded
&lt;code dir=&quot;auto&quot;&gt;permitted&lt;/code&gt; any more than it erases a recorded &lt;code dir=&quot;auto&quot;&gt;refused&lt;/code&gt; — both survive an
&lt;code dir=&quot;auto&quot;&gt;unbind&lt;/code&gt; exactly the same way, so re-binding later does not silently reset
your decision back to absence.&lt;/p&gt;
&lt;h2 id=&quot;related-documentation&quot;&gt;Related Documentation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/migrations/&quot;&gt;Migrations index&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
