<?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-08-13-2-gates-are-declarative-asset-backed-doctrine-artefacts/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-08-13-2-gates-are-declarative-asset-backed-doctrine-artefacts/</id>
  <title>ADR: Transition gates are declarative, asset-backed, first-class doctrine artefacts</title>
  <updated>2026-08-13T00: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-08-13-2-gates-are-declarative-asset-backed-doctrine-artefacts/"/>
  <summary>Replaces the named-Python-handler gate registry with a declarative `gate` kind whose asset runs as an allowlisted interpreter plus argv, confined, after the trust check.</summary>
  <content type="html">&lt;h2 id=&quot;transition-gates-are-declarative-asset-backed-first-class-doctrine-artefacts&quot;&gt;Transition gates are declarative, asset-backed, first-class doctrine artefacts&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Filename:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;2026-08-13-2-gates-are-declarative-asset-backed-doctrine-artefacts.md&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted (2026-09-27, amended in place)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-08-13 (proposed) · 2026-09-27 (amended and accepted)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Operator (ATDD)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt; Follows &lt;a href=&quot;/adr/3.x/2026-08-13-1-built-in-mission-subtree-stays-nested-retire-legacy-step-contracts/&quot;&gt;ADR 2026-08-13-1&lt;/a&gt;,
which retires the legacy &lt;code dir=&quot;auto&quot;&gt;MissionStepContract&lt;/code&gt; surface that currently carries gate bindings.
Gate semantics must be re-homed onto the unified &lt;code dir=&quot;auto&quot;&gt;MissionStep&lt;/code&gt; model as part of that removal.
Implementation tracks the #2535 gate epic (#3418 gate kind, #3419 dispatcher, #3420 re-home
binding, #3421 &lt;code dir=&quot;auto&quot;&gt;execute_dir&lt;/code&gt;).&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;amendment-note-2026-09-27&quot;&gt;Amendment note (2026-09-27)&lt;/h2&gt;
&lt;p&gt;Accepted together with &lt;a href=&quot;/adr/3.x/2026-08-13-4-executable-doctrine-runs-only-from-trusted-publishers/&quot;&gt;ADR 2026-08-13-4&lt;/a&gt;
and &lt;a href=&quot;/adr/3.x/2026-08-13-6-gate-outcomes-carry-severity-operator-strategy-decides-effect/&quot;&gt;ADR 2026-08-13-6&lt;/a&gt;
as one set, after the pack-trust ADR review (architect-alphonso / paula-patterns squad,
operator-approved 2026-09-27). The body below is &lt;strong&gt;rewritten in place&lt;/strong&gt; so it no longer carries
text that the 2026-08-13 post-dialectics revision had superseded. Changes against the Proposed
text:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The shell-string &lt;code dir=&quot;auto&quot;&gt;entrypoint&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;python {asset} --strict&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;disposition: fail_closed&lt;/code&gt; are
removed. Invocation is a structured &lt;code dir=&quot;auto&quot;&gt;interpreter&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;args[]&lt;/code&gt;; the outcome is a severity-bearing
verdict whose effect ADR -6 decides.&lt;/li&gt;
&lt;li&gt;An &lt;strong&gt;interpreter allowlist&lt;/strong&gt; is added (it was binding in #2599 and had been lost from this ADR).&lt;/li&gt;
&lt;li&gt;“Determinism enforced by a network-denied sandbox” is replaced by the concrete v1
&lt;strong&gt;refuse-unconfinable&lt;/strong&gt; baseline from #2540; OS-level sandboxing stays in #2541.&lt;/li&gt;
&lt;li&gt;A hard ordering invariant is added: nothing is resolved or executed before the ADR -4 trust
check passes.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; must become activatable for gate use; open question 1 is resolved (pre-review stays a
grandfathered code gate).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The 2026-08-13 dialectics pass (&lt;code dir=&quot;auto&quot;&gt;work/gate-design-dialectics/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;99-COHERENCE.md&lt;/code&gt;) is folded into
the body: gate stays a first-class &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;, the outcome is a structured verdict, and
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-pre-review&lt;/code&gt; stays a code gate.&lt;/p&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;Today a transition gate is a &lt;strong&gt;binding&lt;/strong&gt; in a step-contract YAML — &lt;code dir=&quot;auto&quot;&gt;on_transition: &quot;in_progress-&gt;for_review&quot;&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;handler: &quot;spec-kitty-pre-review&quot;&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;fail_open: true&lt;/code&gt; — where
&lt;code dir=&quot;auto&quot;&gt;handler&lt;/code&gt; is a &lt;em&gt;name&lt;/em&gt; into &lt;code dir=&quot;auto&quot;&gt;GATE_REGISTRY&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/review/gate_registry.py&lt;/code&gt;), a
Python dict whose &lt;code dir=&quot;auto&quot;&gt;run: Callable[[TransitionGateContext], GateVerdict]&lt;/code&gt; is compiled code.
The binding is data, but the &lt;strong&gt;check logic is Python registered in-process&lt;/strong&gt;. There is
exactly one handler, and every gate fault is converted to a warning by &lt;code dir=&quot;auto&quot;&gt;_mt_fail_open_gate&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/agent/tasks_move_task.py&lt;/code&gt;). The &lt;code dir=&quot;auto&quot;&gt;GateBinding&lt;/code&gt; fields
&lt;code dir=&quot;auto&quot;&gt;handler_kind&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;fail_open&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/charter/offering/missions/step_contracts.py&lt;/code&gt;) are declared
but never read.&lt;/p&gt;
&lt;p&gt;Two problems: (1) adding a gate requires a code deploy (a new registered handler), not a
doctrine edit, so gates cannot ship as part of a mission-type’s doctrine pack; (2) retiring
&lt;code dir=&quot;auto&quot;&gt;MissionStepContract&lt;/code&gt; (ADR 2026-08-13-1) removes the surface the gate binding lives on, so
gate semantics must move to the unified &lt;code dir=&quot;auto&quot;&gt;MissionStep&lt;/code&gt; model regardless.&lt;/p&gt;
&lt;p&gt;Gates are &lt;strong&gt;deterministic&lt;/strong&gt; — a simple code check or a script (documentation linting,
consistency checks, structural validation). That determinism is the lever: the check can be
declared as data and shipped in the pack rather than compiled into the CLI. Built-in already
ships such a script (&lt;code dir=&quot;auto&quot;&gt;packs/built-in/assets/docs_structural_lint.py&lt;/code&gt;) that nothing executes.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Gates should ship &lt;em&gt;with&lt;/em&gt; the mission-type doctrine that needs them, per-type where relevant.&lt;/li&gt;
&lt;li&gt;Single canonical authority — one step model (&lt;code dir=&quot;auto&quot;&gt;MissionStep&lt;/code&gt;), one gate mechanism.&lt;/li&gt;
&lt;li&gt;Reuse the existing &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; kind (the sanctioned way to ship executable logic downstream)
rather than invent a second code-shipping mechanism.&lt;/li&gt;
&lt;li&gt;No shell surface: a declarative gate must not be a way to smuggle an arbitrary command line
into a pack.&lt;/li&gt;
&lt;li&gt;Determinism must be preserved and enforced (gates are pure checks, never mutate state), with
a baseline that ships now and needs no new dependency.&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;A — Keep the Python handler registry&lt;/strong&gt;, add handlers as needed (status quo, code-deploy per gate).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;B — Declarative &lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt; artefact kind&lt;/strong&gt;, check logic referenced from an &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt;, invoked as an
allowlisted interpreter plus an argv list.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;C — Inline command strings&lt;/strong&gt; in the gate/step YAML (no asset), executed directly.&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: “B”.&lt;/strong&gt; A gate is a &lt;strong&gt;first-class doctrine &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt;), tiered
and DRG-participating like every other kind, reusable by id. The ~8 totality-map edits a new
kind costs are accepted as the price of a uniform kind model (operator decision).&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Code ships as an &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt;&lt;/strong&gt; (unchanged loose-contract inert blob, &lt;code dir=&quot;auto&quot;&gt;mime&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt;,
resolved to a path, never auto-executed). The gate &lt;em&gt;references&lt;/em&gt; the asset by id. &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; is
today excluded from activation (&lt;code dir=&quot;auto&quot;&gt;_NON_AUGMENTATION_ELIGIBLE_KINDS&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;src/charter/offering/artifact_kinds.py&lt;/code&gt;); it &lt;strong&gt;must become activatable for gate use&lt;/strong&gt; so a
gate’s asset resolves through the same charter/DRG chain as the gate itself.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Structured invocation, no shell.&lt;/strong&gt; The gate declares &lt;code dir=&quot;auto&quot;&gt;interpreter&lt;/code&gt; plus &lt;code dir=&quot;auto&quot;&gt;args[]&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;{asset}&lt;/code&gt;
is substituted as &lt;strong&gt;one argv element&lt;/strong&gt; (the resolved asset path); it is never interpolated into
a string. The process is spawned without a shell. This removes shell injection and the
“&lt;code dir=&quot;auto&quot;&gt;sys.executable&lt;/code&gt; lacks the pack’s dependencies” trap.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Interpreter allowlist.&lt;/strong&gt; The dispatcher accepts only vetted interpreter tokens (initially
&lt;code dir=&quot;auto&quot;&gt;python&lt;/code&gt;) and maps each to a concrete executable itself. A gate can never name an arbitrary
executable. Without the allowlist, &lt;code dir=&quot;auto&quot;&gt;interpreter: sh&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;args: [-c, &quot;...&quot;]&lt;/code&gt; is the shell
again. A gate naming an interpreter outside the allowlist is refused at load time.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The outcome is a structured verdict carrying a severity&lt;/strong&gt;, not an exit code plus a
per-gate fail-closed boolean. The verdict channel is a capped structured (JSON) payload.
Block-vs-proceed is decided by the operator’s error-handling strategy over the severity
ladder — see &lt;a href=&quot;/adr/3.x/2026-08-13-6-gate-outcomes-carry-severity-operator-strategy-decides-effect/&quot;&gt;ADR 2026-08-13-6&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Determinism baseline (v1): refuse-unconfinable.&lt;/strong&gt; Every gate run gets the #2540 containment
baseline: an environment allowlist, a dedicated process group killed on timeout plus
&lt;code dir=&quot;auto&quot;&gt;setrlimit&lt;/code&gt; bounds, path confinement to the resolved execution context, and the capped
verdict channel. If a capability probe shows the host cannot apply the baseline, the result is
a &lt;strong&gt;could-not-run&lt;/strong&gt; outcome (severity fixed by ADR -6) — &lt;strong&gt;never an unconfined run&lt;/strong&gt;.
OS-level sandboxing (network namespaces, seccomp and similar) remains follow-on work in #2541.
The baseline applies to trusted packs as well: trust is not containment.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ordering invariant (hard).&lt;/strong&gt; No asset is resolved and nothing is executed before the
&lt;a href=&quot;/adr/3.x/2026-08-13-4-executable-doctrine-runs-only-from-trusted-publishers/&quot;&gt;ADR 2026-08-13-4&lt;/a&gt;
trust check has passed for the pack that ships the gate. Order: gate definition → trust
check (including the dispatch-time re-hash) → asset resolution → execution-context stamping
→ confined run.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Binding lives on the &lt;code dir=&quot;auto&quot;&gt;MissionStep&lt;/code&gt;&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;gates: [{on_transition, gate: &amp;#x3C;id&gt;}]&lt;/code&gt;) —
definition (what the check is) and binding (when it fires) are cleanly separated. This
keeps the edge-scoped transition model and &lt;code dir=&quot;auto&quot;&gt;TransitionGateContext&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One generic dispatcher plus a few code gates.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;GATE_REGISTRY&lt;/code&gt; gains one generic
&lt;code dir=&quot;auto&quot;&gt;declarative-gate&lt;/code&gt; dispatcher that reads the gate, runs it as above, and returns a
&lt;code dir=&quot;auto&quot;&gt;GateVerdict&lt;/code&gt;. Named per-gate Python handlers are not added any more.
&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty-pre-review&lt;/code&gt; stays a grandfathered code gate&lt;/strong&gt;: its inputs are an injected
&lt;code dir=&quot;auto&quot;&gt;ScopeSource&lt;/code&gt;, a baseline and the changed-files SSOT, not cwd plus an exit code, so it does not
fit the declarative shape. It keeps its live never-break-&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; behaviour, mapped onto
the ADR -6 severity model.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Shape of a gate definition:&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;id&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;docs-structural-lint&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 style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;schema_version&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;1.0&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&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 style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;asset&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;common-docs-structural-lint&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;# asset id, resolved only after the trust check passes&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 style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;interpreter&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;python&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;# allowlisted token, never a free executable&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 style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;args&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: [&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;{asset}&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;, &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;--strict&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&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;# {asset} is one argv element; no shell string&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 style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;executionTarget&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;primary&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;# ADR 2026-08-13-3 surface selector&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 style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;timeout_seconds&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#F78C6C;--1:#AA0982&quot;&gt;120&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 style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;severity&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;RECOVERABLE&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;# severity for a *detected violation* (ADR -6)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;h3 id=&quot;consequences&quot;&gt;Consequences&lt;/h3&gt;
&lt;h4 id=&quot;positive&quot;&gt;Positive&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Adding/changing a gate is a doctrine edit, shippable per mission-type in the pack.&lt;/li&gt;
&lt;li&gt;One code-shipping mechanism (assets); the asset kind keeps its inert loose contract.&lt;/li&gt;
&lt;li&gt;No shell surface: the interpreter allowlist plus argv substitution closes injection by
construction.&lt;/li&gt;
&lt;li&gt;Determinism is enforced by a baseline that ships without a new dependency, and a host that
cannot apply it yields an honest could-not-run outcome instead of an unconfined run.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;“Execute an asset” is &lt;strong&gt;net-new machinery&lt;/strong&gt; — assets are resolved to a path today and
never executed (see &lt;a href=&quot;/adr/3.x/2026-08-13-3-gate-execution-targets-through-kernel-surface-selector/&quot;&gt;ADR 2026-08-13-3&lt;/a&gt;
for &lt;em&gt;where&lt;/em&gt; it runs and &lt;a href=&quot;/adr/3.x/2026-08-13-4-executable-doctrine-runs-only-from-trusted-publishers/&quot;&gt;ADR 2026-08-13-4&lt;/a&gt;
for &lt;em&gt;whether&lt;/em&gt; it may run).&lt;/li&gt;
&lt;li&gt;Making &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; activatable for gate use touches the single canonical exclusion set and every
consumer of it (org-pack loader, charter cascade).&lt;/li&gt;
&lt;li&gt;The v1 baseline does not deny network access at the OS level; that waits on #2541.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;A new &lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; is added shortly after &lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt; is removed — net
kind count roughly unchanged, but the new kind is declarative-data, not a code registry.&lt;/li&gt;
&lt;li&gt;The interpreter allowlist is dispatcher configuration; widening it is a reviewed code change,
not a pack edit.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;resolved-and-open-questions&quot;&gt;Resolved and open questions&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;&lt;em&gt;Resolved (2026-09-27):&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty-pre-review&lt;/code&gt; stays a single grandfathered code gate.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Open:&lt;/em&gt; one asset per gate, or may a gate carry its own blob (collapsing asset+gate for
non-reused checks)?&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Open:&lt;/em&gt; gate→asset DRG edge: reuse &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;, or a dedicated relation?&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Open:&lt;/em&gt; where gate &lt;em&gt;inputs&lt;/em&gt; come from (env vars vs args vs cwd contents). Depth handled in
ADR -3; whatever is chosen must pass the environment allowlist.&lt;/li&gt;
&lt;/ol&gt;</content>
</entry>
