Step 4 of 6 in the KYAML adoption order fixed by 3-practice/YAML-POLICY.adoc §5.
Blocked by #1022.
Work
Decide KYAML scope on the evidence from steps 1–3.
Gate (§5)
An owner ruling recorded as a decision row. Not an inference from the probe.
Why this is its own step
§3.4: the owner considered mandating KYAML estate-wide including workflows and
chose instead to probe workflows first and decide after. The policy therefore
mandates KYAML nowhere today, and nothing in the estate is out of compliance
with Y-3, because Y-3 imposes nothing yet.
⚠ Step 1 (#1020) proved only that GitHub parses KYAML. That is one input to
this decision and explicitly not the decision itself — the §5 gate rules out
inferring scope from the probe.
Acceptance criteria
🤖 Generated with Claude Code
https://claude.ai/code/session_01WRvDivYwLSeVCJUrfjic3f
Step 4 of 6 in the KYAML adoption order fixed by
3-practice/YAML-POLICY.adoc§5.Blocked by #1022.
Work
Decide KYAML scope on the evidence from steps 1–3.
Gate (§5)
Why this is its own step
§3.4: the owner considered mandating KYAML estate-wide including workflows and
chose instead to probe workflows first and decide after. The policy therefore
mandates KYAML nowhere today, and nothing in the estate is out of compliance
with Y-3, because Y-3 imposes nothing yet.
⚠ Step 1 (#1020) proved only that GitHub parses KYAML. That is one input to
this decision and explicitly not the decision itself — the §5 gate rules out
inferring scope from the probe.
Acceptance criteria
long-term arm labelled as such.
(
hyperpolymath/standards#787), appended — never renumbered.step 6 does not start without that.
🤖 Generated with Claude Code
https://claude.ai/code/session_01WRvDivYwLSeVCJUrfjic3f