<?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-07-22-1-gate-binding-content-vs-relationship/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-07-22-1-gate-binding-content-vs-relationship/</id>
  <title>ADR: gate bindings reuse `mission_step_contract` — the content-vs-relationship principle</title>
  <updated>2026-07-22T00: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-07-22-1-gate-binding-content-vs-relationship/"/>
  <summary>Gate bindings reuse `mission_step_contract` instead of earning a kind: promote only distributable content artefacts, attach relationships and configuration to existing ones.</summary>
  <content type="html">&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-07-22&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Operator (Stijn Dejongh); recorded by the plan-phase architect
(&lt;code dir=&quot;auto&quot;&gt;architect-alphonso&lt;/code&gt;) per post-plan-squad finding C-C4.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt; epic &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2535&quot;&gt;#2535&lt;/a&gt;
(doctrine-controlled transition gates, half A); tracker
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2468&quot;&gt;#2468&lt;/a&gt; (the decision-record
obligation this ADR discharges); spec constraint C-001; sibling ADR
&lt;a href=&quot;/adr/3.x/2026-07-21-2-glossary-first-order-doctrine-artefact/&quot;&gt;2026-07-21-2-glossary-first-order-doctrine-artefact.md&lt;/a&gt;
(the precedent this ADR reconciles).&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;Half A of the doctrine-controlled transition gates mission (#2535) needs gate handlers
to bind to activation — a repo’s active doctrine should decide which handler fires on a
&lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; transition, not a hardcoded repo-shape probe. The open design question is
&lt;em&gt;where that binding lives&lt;/em&gt;: does a gate binding need its own first-class, charter-activatable
&lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; (a &lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt; kind, joining &lt;code dir=&quot;auto&quot;&gt;directive&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;glossary_pack&lt;/code&gt;, etc. in the
activatable universe), or does it attach to an artefact that already exists?&lt;/p&gt;
&lt;p&gt;This question was flagged for a decision record by tracker #2468 and by the post-plan
adversarial squad (finding C-C4), because the mission has a &lt;strong&gt;visible opposite precedent
in the same doctrine layer, decided one day earlier&lt;/strong&gt;: ADR
&lt;a href=&quot;/adr/3.x/2026-07-21-2-glossary-first-order-doctrine-artefact/&quot;&gt;2026-07-21-2&lt;/a&gt; promotes
&lt;code dir=&quot;auto&quot;&gt;GLOSSARY_PACK&lt;/code&gt; to a first-class, charter-activatable &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;. Without an explicit
rule, a reader lands on “glossary got its own kind” and “gate binding did not” back-to-back
and reasonably reads it as inconsistency rather than principle.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;C-001&lt;/strong&gt; (primary) — the spec constraint: gate handlers bind through the existing
&lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt; kind; no new activatable &lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;; the rationale
must be a durable principle, not merely the #2468 cost, recorded in an ADR at plan time.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Single canonical authority&lt;/strong&gt; (charter governing principle) — one rule should explain
both this decision and the glossary decision, or the doctrine layer’s own artefact-kind
boundary looks arbitrary.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2468 decision-record obligation&lt;/strong&gt; — a kind-boundary call of this shape must leave a
citable record, not a retro-justification discoverable only in code review.&lt;/li&gt;
&lt;li&gt;Frames &lt;strong&gt;C-002&lt;/strong&gt; (native handlers only, half A) and &lt;strong&gt;FR-006&lt;/strong&gt; (bindings resolve through
the existing activatable kind) — this ADR is why FR-006 is shaped the way it is.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Option 1 (chosen)&lt;/strong&gt; — Reuse &lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt;: a gate binding is a new field,
&lt;code dir=&quot;auto&quot;&gt;gates: list[GateBinding]&lt;/code&gt;, on the existing &lt;code dir=&quot;auto&quot;&gt;MissionStepContract&lt;/code&gt; model, authored in
&lt;code dir=&quot;auto&quot;&gt;review.step-contract.yaml&lt;/code&gt;. No new &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;, no new enumeration surface.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option 2 (rejected)&lt;/strong&gt; — Promote a first-class &lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;, mirroring the
glossary-pack precedent: its own DRG node kind, its own URN prefix, its own place in the
charter-activatable universe.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Chosen option: Option 1 — reuse &lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&quot;the-principle&quot;&gt;The principle&lt;/h3&gt;
&lt;p&gt;Whether a concept earns its own first-class &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; turns on &lt;strong&gt;what kind of thing
it is&lt;/strong&gt;, not on how important or how novel it is:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;PROMOTE&lt;/strong&gt; a concept to a first-class, charter-activatable &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; when it is a
new &lt;strong&gt;distributable content artefact&lt;/strong&gt; — it ships its own files, has its own repository
of instances, carries its own provenance, and is meaningfully migrated, versioned, and
activated as a unit independent of any other artefact. The glossary pack is this shape:
&lt;code dir=&quot;auto&quot;&gt;*.glossary-pack.yaml&lt;/code&gt; files, a migratable 104-term corpus, its own &lt;code dir=&quot;auto&quot;&gt;glossary_pack:&lt;/code&gt; URN.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;REUSE / ATTACH&lt;/strong&gt; when the concept is a &lt;strong&gt;relationship or configuration&lt;/strong&gt; expressed
&lt;em&gt;on&lt;/em&gt; an artefact that already has its own first-class identity. It has no files,
repository, or provenance of its own — it is a field that configures how the existing
artefact behaves at a named point. A gate binding is this shape: it does not exist
independent of the step contract it configures; it says “when this contract’s
&lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; edge fires, call this named handler.” It is the field
&lt;code dir=&quot;auto&quot;&gt;gates: list[GateBinding]&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;MissionStepContract&lt;/code&gt;, authored inline in
&lt;code dir=&quot;auto&quot;&gt;review.step-contract.yaml&lt;/code&gt; — not a standalone file type, not a separate corpus, not
something a project would ever activate or deactivate on its own apart from the contract
it lives on.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Applied here: a gate binding rides the &lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt; kind’s &lt;em&gt;existing&lt;/em&gt;
activation, resolution, and DRG wiring. It needs no new enumeration surface — no new entry
in &lt;code dir=&quot;auto&quot;&gt;pack_context._BUILTIN_ARTIFACT_KINDS&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;activations._ALLOWED_KINDS&lt;/code&gt;, or
&lt;code dir=&quot;auto&quot;&gt;org_pack_loader._ORG_DRG_CANONICAL_KINDS&lt;/code&gt; (the three mirrored kind-lists the glossary ADR
names as drift-guarded). This is exactly what FR-006 requires: bindings resolve through the
existing activatable kind, with no new &lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;reconciling-the-glossary-precedent-squad-finding-c-c4&quot;&gt;Reconciling the glossary precedent (squad finding C-C4)&lt;/h3&gt;
&lt;p&gt;The glossary ADR and this ADR reach opposite conclusions — &lt;strong&gt;promote&lt;/strong&gt; vs &lt;strong&gt;reuse&lt;/strong&gt; — from
the &lt;strong&gt;same governing rule&lt;/strong&gt;, because the two artefacts differ in kind, not in importance:&lt;/p&gt;








































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Dimension&lt;/th&gt;&lt;th&gt;Glossary pack&lt;/th&gt;&lt;th&gt;Gate binding&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Nature&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;New distributable content&lt;/td&gt;&lt;td&gt;Relationship/configuration on an existing artefact&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Has its own files?&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Yes — &lt;code dir=&quot;auto&quot;&gt;*.glossary-pack.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;No — a field inside &lt;code dir=&quot;auto&quot;&gt;review.step-contract.yaml&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Has its own corpus/instances?&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Yes — 104 migrated terms, growable independently&lt;/td&gt;&lt;td&gt;No — bindings are inline entries on one contract&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Has its own provenance/URN?&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Yes — &lt;code dir=&quot;auto&quot;&gt;glossary_pack:&lt;/code&gt;&lt;/td&gt;&lt;td&gt;No — inherits the contract’s &lt;code dir=&quot;auto&quot;&gt;mission_step_contract:&lt;/code&gt; identity&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Independently activatable?&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Yes — a project can carry a pack with no gates and vice versa is meaningless the other way&lt;/td&gt;&lt;td&gt;No — a binding has no existence apart from the contract it configures&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Outcome under the rule&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Promote&lt;/strong&gt; to a first-class &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Reuse/attach&lt;/strong&gt; as a field on an existing kind&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Read together, the two ADRs are not a contradiction: they are the &lt;strong&gt;same rule applied
correctly to two different shapes of thing&lt;/strong&gt;. A future reader who lands on either ADR
should follow the cross-link to the other and see one principle, not two ad hoc calls.&lt;/p&gt;
&lt;h3 id=&quot;rejected-option-2-promote-a-gate-artifactkind&quot;&gt;Rejected: Option 2 (promote a &lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;)&lt;/h3&gt;
&lt;p&gt;Rejected on the content-vs-relationship rule itself: a gate binding has no independent
files, repository, or provenance — promoting it would misclassify a relationship as
content. It also fails the #2468 cost test the glossary ADR already names as load-bearing:
a new kind means growing the three mirrored, drift-guarded kind-lists
(&lt;code dir=&quot;auto&quot;&gt;pack_context._BUILTIN_ARTIFACT_KINDS&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;activations._ALLOWED_KINDS&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;org_pack_loader._ORG_DRG_CANONICAL_KINDS&lt;/code&gt;) for a concept that has nothing to enumerate on
its own. The cost is corroborating evidence, not the reason — the reason is the principle
above.&lt;/p&gt;
&lt;h3 id=&quot;consequences&quot;&gt;Consequences&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Positive&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;One principle explains both the glossary promotion and the gate reuse; no artefact-kind
boundary call in this doctrine layer reads as arbitrary.&lt;/li&gt;
&lt;li&gt;FR-006 is satisfied for free: bindings resolve through existing activation with zero new
enumeration surfaces to keep in sync.&lt;/li&gt;
&lt;li&gt;The schema work (data-model.md §3, &lt;code dir=&quot;auto&quot;&gt;GateBinding&lt;/code&gt;) can proceed on a settled, cited
foundation instead of an implicit assumption discovered during review.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Negative&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A gate binding is invisible to any tooling that lists &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; values directly
(e.g. a future “what kinds exist” report) — it is only discoverable by reading the
&lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt; schema. This is the expected shape for a field, not a defect.&lt;/li&gt;
&lt;li&gt;If a future need arises for gate bindings to be independently distributable (their own
files/provenance, shared across contracts) the classification would flip and Option 2
would need to be reopened as a new decision, not retrofitted onto this one.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Boundaries&lt;/strong&gt; — this ADR does not define the &lt;code dir=&quot;auto&quot;&gt;GateBinding&lt;/code&gt; field shape, the resolution
join, or the lane→contract ownership mapping; those are IC-04’s schema work
(data-model.md §3). It records only the kind-boundary principle and its application.&lt;/p&gt;
&lt;h2 id=&quot;related-adrs&quot;&gt;Related ADRs&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/adr/3.x/2026-07-21-2-glossary-first-order-doctrine-artefact/&quot;&gt;2026-07-21-2-glossary-first-order-doctrine-artefact.md&lt;/a&gt;
— the &lt;strong&gt;promote&lt;/strong&gt; precedent this ADR reconciles: same content-vs-relationship rule,
opposite outcome, because the glossary pack is new distributable content and a gate
binding is a relationship on an existing artefact.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/3.x/2026-05-16-1-doctrine-layer-merge-semantics/&quot;&gt;2026-05-16-1-doctrine-layer-merge-semantics.md&lt;/a&gt;
— the governing doctrine-integrity ADR; this decision operates inside its artefact-kind
and activation model.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
