From 84c1f83f877557b7354699f455b046b299d3e5a9 Mon Sep 17 00:00:00 2001
From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com>
Date: Tue, 22 Sep 2026 23:58:28 +0100
Subject: [PATCH] docs(policy): cross-reference the six booked KYAML adoption
 issues
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

§5 fixed a six-step dependency order and said each step is a separate issue,
but carried no issue numbers, so a reader of the policy could not find them.

Step 1 is discharged: a two-arm same-commit probe on pons-asinorum proved
GitHub Actions parses a KYAML workflow — jobs=1 and an executed-step marker
on BOTH the KYAML arm and its plain-YAML control, with the absent-from-lock
confound excluded by construction (no actions.lock, no uses:). Closed as
standards#1020.

Steps 2-6 are booked as #1021-#1025 in dependency order.

The added text states explicitly that closing step 1 does NOT advance the
scope question: §5 step 4 remains an owner ruling and forbids inferring
scope from the probe.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WRvDivYwLSeVCJUrfjic3f
---
 3-practice/YAML-POLICY.adoc | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/3-practice/YAML-POLICY.adoc b/3-practice/YAML-POLICY.adoc
index 0e0e9a13..73e3d3fb 100644
--- a/3-practice/YAML-POLICY.adoc
+++ b/3-practice/YAML-POLICY.adoc
@@ -251,6 +251,21 @@ failed. The bar is comment-preserving and idempotent, with a dead mutant.
 Each step is a separate issue. The order is a dependency order, not a
 preference: no step may start before its predecessor has landed evidence.
 
+These issues are now booked, in this dependency order:
+
+* Step 1 — `hyperpolymath/standards#1020` — *closed, gate met.* GitHub Actions
+  does parse a KYAML workflow: a two-arm same-commit probe gave `jobs = 1` and
+  an executed-step marker on both the KYAML arm and its plain-YAML control.
+  This settles the *parser* dimension only.
+* Step 2 — `hyperpolymath/standards#1021` — comment-preservation proof.
+* Step 3 — `hyperpolymath/standards#1022` — formatter/linter for arbitrary YAML.
+* Step 4 — `hyperpolymath/standards#1023` — owner ruling on scope.
+* Step 5 — `hyperpolymath/standards#1024` — migrate non-bot estate YAML.
+* Step 6 — `hyperpolymath/standards#1025` — workflows, if step 4 rules them in.
+
+Step 1 closing does *not* advance the scope question. Step 4 remains an owner
+ruling and §5 explicitly forbids inferring scope from the probe.
+
 [cols="1,6,6",options="header"]
 |===
 | Step | Work | Gate to pass
@@ -310,4 +325,10 @@ preference: no step may start before its predecessor has landed evidence.
 | Document created. Y-1 in force. Y-2 sequenced behind the comment proof.
   Y-3 sequenced, scope deferred to the GitHub Actions probe; estate-wide
   adoption booked as ordered issues per §5.
+
+| 2026-09-22
+| Probe result
+| §5 step 1 discharged: GitHub Actions proven to parse KYAML
+  (standards#1020, closed). Steps 2–6 booked as #1021–#1025 in
+  dependency order and cross-referenced from §5.
 |===