<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/development/reference/issue-matrix-verdicts/">
  <id>https://docs.spec-kitty.ai/development/reference/issue-matrix-verdicts/</id>
  <title>Issue-Matrix Verdict Reference</title>
  <updated>2026-10-26T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/development/reference/issue-matrix-verdicts/"/>
  <summary>The five issue-matrix verdict values, which transitions each one gates, the reference-classification model that decides whether a row is required, and the evidence-token rule.</summary>
  <content type="html">&lt;span id=&quot;issue-matrix-verdict-reference&quot;&gt;&lt;/span&gt;
&lt;p&gt;Look-up material for the &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; verdict vocabulary and the
reference-classification model that decides which discovered &lt;code dir=&quot;auto&quot;&gt;#NNNN&lt;/code&gt; citations
require a verdict row at all (#3469). This page documents the two levers as a
single source of truth so an operator or agent never has to reverse-engineer
gating behavior from gate error text.&lt;/p&gt;
&lt;h2 id=&quot;the-two-levers&quot;&gt;The two levers&lt;/h2&gt;
&lt;p&gt;The issue-matrix approval gate has two independent decisions, and confusing
them is the root of most “why is this blocking approval” surprises:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Classification&lt;/strong&gt; decides whether a row is &lt;strong&gt;required&lt;/strong&gt; (gating). It runs
once, over every &lt;code dir=&quot;auto&quot;&gt;#NNNN&lt;/code&gt; reference discovered in mission artifacts
(&lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research.md&lt;/code&gt;, analysis docs, WP prompts, contracts),
and is consumed identically by every site that computes
“referenced-but-missing”: the WP &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt;-transition blocker, the merge-time
&lt;code dir=&quot;auto&quot;&gt;merge_gates&lt;/code&gt; check, and &lt;code dir=&quot;auto&quot;&gt;status/doctor&lt;/code&gt;. One shared function, one answer —
a reference is never gating at one site and non-gating at another.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Verdict&lt;/strong&gt; decides whether an existing row is &lt;strong&gt;resolved&lt;/strong&gt;. An operator may
record any verdict on any row regardless of its classification; a
&lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt; verdict makes a row non-gating regardless of classification,
and an implementation-target classification requires a row to exist even if
the scaffolder didn’t produce one for it.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The two levers can disagree by design (an operator can always assert
&lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt; on a row the scaffolder classified gating), and that
disagreement always resolves in favor of the operator’s explicit verdict.&lt;/p&gt;
&lt;h2 id=&quot;verdict-values&quot;&gt;Verdict values&lt;/h2&gt;









































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Verdict&lt;/th&gt;&lt;th&gt;Meaning&lt;/th&gt;&lt;th&gt;Gates &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt;?&lt;/th&gt;&lt;th&gt;Gates &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;/merge?&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;fixed&lt;/code&gt;&lt;/td&gt;&lt;td&gt;The mission fixed the referenced issue.&lt;/td&gt;&lt;td&gt;No (resolves the row)&lt;/td&gt;&lt;td&gt;No&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;verified-already-fixed&lt;/code&gt;&lt;/td&gt;&lt;td&gt;The issue was confirmed already fixed before this mission touched it.&lt;/td&gt;&lt;td&gt;No&lt;/td&gt;&lt;td&gt;No&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;deferred-with-followup&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Work is deliberately deferred; a follow-up is tracked. Requires an evidence-token (see below).&lt;/td&gt;&lt;td&gt;No&lt;/td&gt;&lt;td&gt;No&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt;&lt;/td&gt;&lt;td&gt;A later work package in &lt;em&gt;this&lt;/em&gt; mission will close the issue.&lt;/td&gt;&lt;td&gt;No — accepted at per-WP &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Yes&lt;/strong&gt; — rejected at &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;; must resolve to a terminal verdict before the mission merges&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt;&lt;/td&gt;&lt;td&gt;The reference is cited for context only, or is a PR/commit reference — the mission owes it no work. &lt;strong&gt;Terminal.&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;No&lt;/td&gt;&lt;td&gt;No — passes unchanged, unlike &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt; is additive: it was added alongside the four pre-existing
values with no change to their meaning, so every &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; file
written before this change continues to validate with zero migration.&lt;/p&gt;
&lt;h2 id=&quot;what-done-enforces&quot;&gt;What &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; enforces&lt;/h2&gt;
&lt;p&gt;At &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;, through the &lt;code dir=&quot;auto&quot;&gt;issue_matrix_verdict_terminality&lt;/code&gt;
merge gate, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task --to done&lt;/code&gt;) the &lt;strong&gt;verdict&lt;/strong&gt;
decides resolution for &lt;strong&gt;every&lt;/strong&gt; existing row, whatever its classification:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Every &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt; row blocks in &lt;code dir=&quot;auto&quot;&gt;block&lt;/code&gt; mode and warns in &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt; mode,
whether or not its issue is cited. An uncited row, a &lt;code dir=&quot;auto&quot;&gt;context_only&lt;/code&gt;
citation such as &lt;code dir=&quot;auto&quot;&gt;see #12&lt;/code&gt;, a one-digit reference the detector skips, or a
row recorded with &lt;code dir=&quot;auto&quot;&gt;agent issue-verdict&lt;/code&gt; alone all count.&lt;/li&gt;
&lt;li&gt;When a matrix exists, it is judged whole, even for a Mission with zero
gating references: a malformed row or an unknown verdict is unresolved too.&lt;/li&gt;
&lt;li&gt;A Mission with zero gating references and &lt;strong&gt;no&lt;/strong&gt; matrix has nothing to
enforce and passes. After consolidation that means the coordination ref is
valid and holds neither &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; nor &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;ISSUE_MATRIX_NOT_AUTHORED&lt;/code&gt;). A deleted ref, a failed git probe or an empty
matrix still fails.&lt;/li&gt;
&lt;li&gt;A Mission &lt;strong&gt;with&lt;/strong&gt; gating references still needs a matrix and a row for
each of them (the completeness gate is unchanged); a missing matrix fails.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A PASS says what it judged:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;No unresolved (in-mission/unknown) rows among N issue-matrix row(s)&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;No issue-matrix authored and no gating issue references — nothing to enforce&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; is unchanged: an &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt; row is accepted there, and a Mission
with zero gating references never needs a matrix to be approved.&lt;/p&gt;
&lt;p&gt;To clear a blocking row, record a terminal verdict (&lt;code dir=&quot;auto&quot;&gt;fixed&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;verified-already-fixed&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;deferred-with-followup&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt;):&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;agent&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;issue-verdict&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--mission&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;&amp;#x3C;handle&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--issue&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;&apos;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;#5678&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&apos;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--verdict&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;fixed&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--actor&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;&amp;#x3C;actor&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--evidence-ref&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;&amp;#x3C;evidence&gt;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Design record: &lt;a href=&quot;/adr/4.x/2026-10-26-1-done-judges-every-issue-matrix-row/&quot;&gt;ADR 2026-10-26-1&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;reference-classification-which-citations-become-gating-rows&quot;&gt;Reference classification: which citations become gating rows&lt;/h2&gt;
&lt;p&gt;Every discovered &lt;code dir=&quot;auto&quot;&gt;#NNNN&lt;/code&gt; token is classified into exactly one of three
buckets, aggregated over &lt;strong&gt;all&lt;/strong&gt; of its occurrences in the mission’s
artifacts (not just the first one found):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Implementation-target&lt;/strong&gt; (gating) — the default. A row is required and
must carry a verdict before &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Context-only&lt;/strong&gt; (non-gating) — the citation is scaffolded as a row for
audit purposes, but does not block approval. A row still records the
citation truthfully (typically with &lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt;); it just isn’t
required to unblock the transition.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;PR/commit reference&lt;/strong&gt; (non-gating) — the same as context-only: recorded,
never blocking.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;default-gating-fail-safe&quot;&gt;Default-gating fail-safe&lt;/h3&gt;
&lt;p&gt;Classification only ever &lt;strong&gt;demotes&lt;/strong&gt; a reference from gating to non-gating,
and only on a positive, explicit signal. An unmarked bare &lt;code dir=&quot;auto&quot;&gt;#NNNN&lt;/code&gt; in ordinary
prose always gates. The demoting signals are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A &lt;code dir=&quot;auto&quot;&gt;PR &lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;pull&lt;/code&gt; token immediately associated with the reference (either
hash form, &lt;code dir=&quot;auto&quot;&gt;PR #300&lt;/code&gt;, or a full &lt;code dir=&quot;auto&quot;&gt;/pull/&amp;#x3C;n&gt;&lt;/code&gt; URL) — classified as a
PR/commit reference.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;line-scoped&lt;/strong&gt; context marker anywhere on the line: &lt;code dir=&quot;auto&quot;&gt;Follow-up:&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;baseline-red&lt;/code&gt; — the whole statement, and every reference in it, is context.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;positional&lt;/strong&gt; citation label: &lt;code dir=&quot;auto&quot;&gt;see #&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;parent&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;epic&lt;/code&gt;. These bind to the
reference they lead into, not to the line: in
&lt;code dir=&quot;auto&quot;&gt;**Input**: Issue #6926 (part of epic #6100)&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;epic&lt;/code&gt; label demotes
&lt;code dir=&quot;auto&quot;&gt;#6100&lt;/code&gt; and leaves &lt;code dir=&quot;auto&quot;&gt;#6926&lt;/code&gt; gating (#7011).&lt;/li&gt;
&lt;li&gt;A cross-repo reference (&lt;code dir=&quot;auto&quot;&gt;owner/repo#NN&lt;/code&gt;, or a full &lt;code dir=&quot;auto&quot;&gt;/issues/&amp;#x3C;n&gt;&lt;/code&gt; URL for a
different repository) — already excluded from discovery entirely; it never
becomes a row of any kind.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Ambiguity never fails open: if none of the above signals is present, the
reference gates.&lt;/p&gt;
&lt;h3 id=&quot;the-missions-own-source-issue-is-never-non-gating&quot;&gt;The Mission’s own source issue is never non-gating&lt;/h3&gt;
&lt;p&gt;The issue a Mission exists to fix always gates, whatever its prose looks like
(#7011). The source issue is read from the Mission’s own record — every one of
these sources that is present contributes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;source_description&lt;/code&gt;, when it &lt;strong&gt;opens&lt;/strong&gt; with the issue form
(&lt;code dir=&quot;auto&quot;&gt;Issue #N: …&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;GitHub issue N …&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;Ticket #N …&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#N …&lt;/code&gt;); a passing mention
of another number deeper in the blurb is not a source issue.&lt;/li&gt;
&lt;li&gt;the spec’s &lt;code dir=&quot;auto&quot;&gt;**Input**:&lt;/code&gt; header line — its first same-repo reference;&lt;/li&gt;
&lt;li&gt;any &lt;code dir=&quot;auto&quot;&gt;Closes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Fixes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Resolves #NNNN&lt;/code&gt; line in the spec.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A source issue that some scanned artifact cites is promoted to
&lt;code dir=&quot;auto&quot;&gt;implementation_target&lt;/code&gt; before classification reaches any consumer, so the
scaffold writes it an &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt; row and the approval gate forces an explicit
verdict. Promotion never invents a row for a number no artifact cites, and it
never demotes: it is a guarantee layered on top of the heuristic, not a
replacement for it. The &lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt; verdict remains legitimate for
references the Mission genuinely owes no work — it just cannot be reached by
automatic classification for the Mission’s own issue (ADR
&lt;a href=&quot;/adr/3.x/2026-09-20-1-issue-matrix-not-applicable-verdict/&quot;&gt;2026-09-20-1&lt;/a&gt;
unchanged).&lt;/p&gt;
&lt;h3 id=&quot;multi-occurrence-aggregation-implementation-target-wins&quot;&gt;Multi-occurrence aggregation: implementation-target wins&lt;/h3&gt;
&lt;p&gt;A &lt;code dir=&quot;auto&quot;&gt;#NNNN&lt;/code&gt; cited once as context (e.g. &lt;code dir=&quot;auto&quot;&gt;parent: #200&lt;/code&gt;) and once as an
implementation target (e.g. “fixes the defect from #200”) is classified
&lt;strong&gt;gating&lt;/strong&gt; — the least-demoted occurrence wins across the whole aggregate. A
reference is never silently downgraded because one of its several citations
happened to carry a demoting marker.&lt;/p&gt;
&lt;h2 id=&quot;the-evidence-token-rule-deferred-with-followup&quot;&gt;The evidence-token rule (&lt;code dir=&quot;auto&quot;&gt;deferred-with-followup&lt;/code&gt;)&lt;/h2&gt;
&lt;p&gt;A &lt;code dir=&quot;auto&quot;&gt;deferred-with-followup&lt;/code&gt; verdict’s &lt;code dir=&quot;auto&quot;&gt;evidence_ref&lt;/code&gt; must contain either:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;an issue reference in &lt;code dir=&quot;auto&quot;&gt;#NNN&lt;/code&gt; form (the follow-up issue), or&lt;/li&gt;
&lt;li&gt;a literal &lt;code dir=&quot;auto&quot;&gt;Follow-up:&lt;/code&gt; token.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A bare &lt;code dir=&quot;auto&quot;&gt;deferred-with-followup&lt;/code&gt; with no follow-up handle in &lt;code dir=&quot;auto&quot;&gt;evidence_ref&lt;/code&gt; is
rejected. &lt;code dir=&quot;auto&quot;&gt;issue-verdict --help&lt;/code&gt; documents this rule directly so it is
discoverable before the gate rejects a submission, not only after.&lt;/p&gt;
&lt;h2 id=&quot;early-discoverability&quot;&gt;Early discoverability&lt;/h2&gt;
&lt;p&gt;The specify/plan/tasks/analyze prompt templates carry a non-gating heads-up
that approvals require an issue-matrix verdict for every referenced
implementation-target issue — so the gate is not a surprise encountered only
at the first blocked approval.&lt;/p&gt;
&lt;h2 id=&quot;see-also&quot;&gt;See also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/api/agent-subcommands/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent issue-verdict&lt;/code&gt;&lt;/a&gt; — the generated CLI reference for the commands that read and write issue-matrix rows, including &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;--actor&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--reason&lt;/code&gt; aliases and &lt;code dir=&quot;auto&quot;&gt;issue-verdict&lt;/code&gt;’s full &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; text.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/api/cli-commands/&quot;&gt;CLI Command Reference&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/4.x/2026-10-26-1-done-judges-every-issue-matrix-row/&quot;&gt;ADR 2026-10-26-1&lt;/a&gt; — at &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, every issue-matrix row is judged, cited or not.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/3.x/2026-09-20-1-issue-matrix-not-applicable-verdict/&quot;&gt;ADR 2026-09-20-1&lt;/a&gt; — the design record for the &lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt; verdict, the classification narrowing, and how it supersedes the never-implemented WP09 &lt;code dir=&quot;auto&quot;&gt;not_applicable&lt;/code&gt; Gate-4 intent noted in &lt;code dir=&quot;auto&quot;&gt;merge_gates.py&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
