Skip to content

docs(policy): cross-reference the six booked KYAML adoption issues #1026

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hyperpolymath merged 1 commit into from
Sep 22, 2026
Merged

docs(policy): cross-reference the six booked KYAML adoption issues #1026

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions 3-practice/YAML-POLICY.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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.
|===
Loading