article: Governed Models — how KYE Protocol™ brings authority to AI models

README.md

@@ -4,6 +4,7 @@ pretty_name: "Governed Models: How KYE Protocol™ Brings Authority to AI Models
 tags:
 - ai-governance
 - model-governance
+- data-governance
 - ai-bom
 - compliance
 - eu-ai-act
@@ -62,6 +63,26 @@ provenance   training     Hub       AI-BOM ·         EU AI Act · GDPR    Repla
 - **Replay-Proof™ evidence** — every governance decision seals into an
   evidence pack an auditor can re-verify from public artifacts.
 
+## Datasets are governed assets, not just files
+
+The Chain of Authority starts at the dataset — so dataset governance is
+not optional garnish. In KYE Protocol™ a dataset is a **governed data
+asset**, declared with the open `kye.data_asset.v1` contract:
+classification, per-field PII inventory, provenance, licence, retention.
+And every *use* of it by an agent — read, summarise, export,
+**train_model**, share, disclose — is checked at decision-time against
+an active `kye.data_use_manifest.v1`: does the purpose match, is the
+classification supportable, is the residency allowed, is the retention
+window still open? **Default-deny on every axis, one signed evidence
+row per access.**
+
+That is the [KYE Data Governance Pack™](https://kyeprotocol.com/data-governance.html),
+and it closes the question model governance alone cannot: *was this
+model even allowed to be trained on that data?* The datasets in the
+[KYE-Protocol org](https://huggingface.co/KYE-Protocol) dogfood the
+posture — each is declared as a public, Apache-2.0, provenance-pinned
+governed data asset.
+
 ## Declare → Assess → Certify
 
 Model governance in KYE Protocol™ is a short path, climbed one posture