Apply signed four-format routing correction across canonical bot guidance #1341

diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md
index eae9337..a0ab905 100644
--- a/.claude/CLAUDE.md
+++ b/.claude/CLAUDE.md
@@ -68,6 +68,15 @@ ### Canonical sources
 
 ## Machine-Readable Artefacts
 
+**Estate data route (owner clarification, 2026-10-25):** kyq handles gates,
+queries and migration for exactly **TOML, Dhall, KYAML, I-JSON/JCS**. Preserve
+TOML/Dhall; YAML/YML migrates to KYAML, and JSON variants to the estate profile
+in **hyperpolymath/ijson-jcs** through kyq. kyX owns wider projection. This is
+the estate route, not a Kubernetes-only tool recommendation. Read
+`3-practice/DATA-FORMAT-ROUTING.adoc` for boundaries, current implementation
+blockers and the standards-update contract. Never equate planned support or
+placeholder validator success with a deployed gate.
+
 **A2ML is retired** (owner rulings D99, D269c, D312, D313). Never create,
 restore, regenerate or extend a `.a2ml` file, and never write a "new" A2ML
 file in a different shape. Machine-readable repo metadata has three forms.
diff --git a/0-AI-MANIFEST.deed b/0-AI-MANIFEST.deed
index 3b1c3fd..9c11a2a 100644
--- a/0-AI-MANIFEST.deed
+++ b/0-AI-MANIFEST.deed
@@ -14,6 +14,7 @@
     :human "README.adoc")
 
   (routing
+    (data-formats :paths ("3-practice/DATA-FORMAT-ROUTING.adoc" "3-practice/YAML-POLICY.adoc" "3-practice/JSON-POLICY.adoc"))
     (k9-foundation :paths ("1-formats/k9/" "1-formats/contractiles/"))
     (language-policy :paths (".claude/CLAUDE.md"))
     (protocols :paths ("2-protocols/" "*-protocol/"))
diff --git a/3-practice/DATA-FORMAT-ROUTING.adoc b/3-practice/DATA-FORMAT-ROUTING.adoc
new file mode 100644
index 0000000..003eae0
--- /dev/null
+++ b/3-practice/DATA-FORMAT-ROUTING.adoc
@@ -0,0 +1,89 @@
+// SPDX-License-Identifier: CC-BY-SA-4.0
+// SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
+= Estate data-format routing: kyq, ijson-jcs and kyX
+:revdate: 2026-10-25
+:toc:
+
+Owner clarification, 25 October 2026: *kyq is the estate route for repository
+data-format gates and migration, limited to exactly four format families.*
+This corrects descriptions that restrict kyq to Kubernetes or make it a
+general-purpose converter for an unlimited collection of formats. It does
+not assert that the implementation is production-ready.
+
+== Four formats, one gate interface
+
+[cols="1,3",options="header"]
+|===
+| Format family | Estate route
+| TOML | Retain TOML and its types; kyq reads, validates and queries it.
+| Dhall | Retain Dhall and its semantics; kyq handles its data-format gate.
+| KYAML | Migrate YAML/YML content to KYAML through kyq. Use `.kyaml` for
+estate-owned configuration; retain names required by consumers, such as
+GitHub workflow `.yml` files. D280's lock-coverage prerequisite still applies.
+| I-JSON/JCS | Migrate JSON and variants through kyq using the implementation
+and estate profile in https://github.com/hyperpolymath/ijson-jcs[hyperpolymath/ijson-jcs].
+This name identifies the owner's repository, not a substitute library with
+similar RFC claims. Keep consumer-required extensions and framing.
+|===
+
+NDJSON and JSONL retain one canonical record per line, with no blank lines.
+JSON-LD retains its contexts and graph meaning. JCS canonicalises JSON bytes;
+it is not RDF dataset canonicalisation. Never flatten a stream into an array
+or fetch remote JSON-LD contexts as an implicit formatting side effect.
+Review tool-demanded JSONC and other extensions against their consumers;
+do not rename a file and claim its syntax or semantics migrated.
+
+TOML and Dhall are not intermediate spellings to replace with JSON or KYAML.
+Gate evaluation must make Dhall import/network policy and resource limits
+explicit. Invalid fixtures and third-party material retain their declared
+roles; a migration must not turn a negative test into a passing example.
+
+== Wider projection: kyX
+
+*kyX* is the name for the wider projection route (D334, formerly kcX).
+Earlier rulings describe DEED/K9/coordination as semantic sources and wider
+representations as projections, with legacy A2ML conversion as the first
+front end (D309/D313). Those wider formats do not expand kyq's four-family
+scope. No deployed kyX executable or repository location is asserted here.
+
+DEED, K9 components and coordination retain their own authorities:
+
+* `1-formats/deed/spec/abnf/deed.abnf` for DEED;
+* `1-formats/k9/spec/K9-CONTRACT-SPEC.adoc` and its Nickel contract for
+  components (there is no interchangeable generic `k9.abnf`);
+* `2-protocols/k9-coordination/spec/abnf/coordination-k9-grammar_v1.2.abnf`
+  for root `coordination.k9`.
+
+The four data formats do not replace those semantic contracts. Launcher
+provisioning continues to consume `launcher/launcher-standard_praxis.deed`
+and its paired prose specification.
+
+== Implementation and transition evidence
+
+At kyq main `4370c76`, build/test recipes still refuse to claim an executable,
+and the I-JSON/JCS source contains unconditional-success validation stubs.
+The 2026-10-24 compiler census records three passing files out of eleven;
+that is not an operational data-format gate. Do not install an alias named
+kyq around another tool, pass unsupported formats through unchanged, or
+accept stub success as conformance.
+
+Until a pinned kyq executable passes positive and negative tests for the
+applicable format, existing yq and hyperpolymath/ijson-jcs checks are explicit
+transitional enforcement. YAML-POLICY Y-1 still forbids regex parsing in
+gates. Replace those readers through verified kyq adapters when available;
+do not weaken working checks to make a migration appear complete.
+
+== Standards updates
+
+`hyperpolymath/ijson-jcs` must track this standards repository. Automated
+updates should propose a new immutable standards revision and execute both
+the library/CLI suite and the standards JSON-policy fixtures against the
+candidate. A green proposal is evidence for that revision, not authority
+to alter JSON-LD semantics or signed historical bytes. An unavailable tool,
+missing fixture, or failed compatibility test blocks promotion.
+
+kyq must consume a pinned, tested ijson-jcs contract and its regression
+vectors. Automatic update detection and reviewable update proposals are
+required; a floating `main` dependency and silent mass rewriting are not
+standards synchronisation. The workflow and receipt must say which exact
+standards and implementation revisions were exercised.
diff --git a/3-practice/JSON-POLICY.adoc b/3-practice/JSON-POLICY.adoc
index 764d802..23ab4b6 100644
--- a/3-practice/JSON-POLICY.adoc
+++ b/3-practice/JSON-POLICY.adoc
@@ -7,6 +7,14 @@ Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 Canonical policy for how JSON and JSON Lines are *written* across all
 hyperpolymath and metadatastician repositories.
 
+*Route clarification (2026-10-25):* JSON and its variants migrate through
+kyq to the estate profile implemented by
+https://github.com/hyperpolymath/ijson-jcs[hyperpolymath/ijson-jcs]. kyq owns
+exactly TOML, Dhall, KYAML and I-JSON/JCS; wider projection belongs to kyX.
+Direct CLI calls below remain transitional enforcement. The implementation
+repository must track standards through tested, immutable update proposals.
+See link:DATA-FORMAT-ROUTING.adoc[Estate data-format routing].
+
 Ruled by the owner on 2026-10-06 as D306 (recorded on `standards#787`). As in
 `YAML-POLICY.adoc`, every rule below says whether it is *in force*, and what
 enforces it. A rule with no tool behind it is labelled as such.
diff --git a/3-practice/YAML-POLICY.adoc b/3-practice/YAML-POLICY.adoc
index 2dc98ad..299ee41 100644
--- a/3-practice/YAML-POLICY.adoc
+++ b/3-practice/YAML-POLICY.adoc
@@ -1,5 +1,5 @@
 // SPDX-License-Identifier: CC-BY-SA-4.0
-= Hyperpolymath YAML, KYAML and yq Policy
+= Hyperpolymath YAML and KYAML Policy
 Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 :toc:
 :toc-placement: preamble
@@ -7,6 +7,12 @@ Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 Canonical policy for how YAML is *read*, *written* and *authored* across all
 hyperpolymath and metadatastician repositories.
 
+*Route clarification (2026-10-25):* kyq is the estate gate interface for
+TOML, Dhall, KYAML and I-JSON/JCS; wider projection belongs to kyX. The yq
+commands below are transitional enforcement while kyq lacks a working
+validated executable, not the destination architecture. See
+link:DATA-FORMAT-ROUTING.adoc[Estate data-format routing].
+
 Ruled by the owner on 2026-09-22. This document distinguishes sharply between
 rules that are *in force now* and rules that are *sequenced behind a proof*.
 A rule that is not yet in force must not be cited by a gate, and must not be
diff --git a/README.adoc b/README.adoc
index 7324c54..90e1559 100644
--- a/README.adoc
+++ b/README.adoc
@@ -135,6 +135,16 @@ decide where former A2ML content goes; anything a mapping spec does not list
 does not translate. Do not hand-convert A2ML in bulk: conversion becomes
 kyX's first front end (D313).
 
+=== Estate data-format route
+
+https://github.com/metadatastician/kyq[kyq] is the estate gate interface for
+exactly TOML, Dhall, KYAML and I-JSON/JCS. Preserve TOML/Dhall; YAML/YML moves
+to KYAML, and JSON variants use
+https://github.com/hyperpolymath/ijson-jcs[the owner's ijson-jcs repository]
+through kyq. kyX covers wider projection. Read
+link:3-practice/DATA-FORMAT-ROUTING.adoc[the routing contract] before claiming
+support, updating consumers, or migrating files.
+
 === Monorepo Architecture
 
 NOTE: This section is history. The A2ML formats specified under
diff --git a/standards_chora.deed b/standards_chora.deed
index fc805eb..cb8d671 100644
--- a/standards_chora.deed
+++ b/standards_chora.deed
@@ -12,6 +12,7 @@
     :licensing "3-practice/LICENCE-POLICY.adoc"
     :agent-policy ".claude/CLAUDE.md")
   (routing
+    :data-formats "3-practice/DATA-FORMAT-ROUTING.adoc"
     :deed "1-formats/deed/"
     :contracts "1-formats/k9/"
     :coordination "2-protocols/k9-coordination/"