AI Conformance is under SIG Architecture
Kubernetes AI Conformance moved from a Working Group to a permanent SIG Architecture subproject. The contributor blog dated October 29 is the record. A charter move is not a new.
The short version
As a permanent subproject under SIG Architecture after the Working Group archived, according to the Kubernetes contributor blog interview with AI Conformance leads dated October 29, 2026.
The document
A Kubernetes contributor blog dated October 29, 2026, describes AI Conformance's move from a temporary Working Group into a permanent SIG Architecture subproject. Leads say the Working Group shipped initial requirements and a certification path, then archived. The CNCF AI Conformance repository remains the program home for checklists. A governance spotlight is not a vulnerability advisory. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.Workload conformance.
The numbers that matter
The figures and dates in the sources are the dependency. Outlet paraphrases yield to the primary document when they disagree. Naming the product or program and the public number is enough. See also the linked note on aac pin. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.AAC pin.
Who is named
The parties named in the primary are the people and organizations in scope. Readers outside those parties are not counterparties to this filing. See also the linked note on hyprland 0.57. Asked directly, Does this page list every MUST requirement? No. It files the governance move and points to the public program repos. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.Hyprland 0.57.
What stays out of scope
This page will not invent winners, site lists, exploit paths, or delivery calendars the sources do not support. A rumor stays labeled as an outlet's expectation. Asked directly, Is this the workload conformance charter brief? Related desk, different document. Workload conformance was a separate charter filing. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.EPICS 7.0.11.
A related filing
A nearby Futureweb brief already files a related dependency. Linking it once keeps the desks from collapsing two documents into one headline. See also the linked note on a patch window. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.A patch window.
Another desk boundary
Another desk may carry a story from the same week. The link only separates the mechanisms. The short answer this page will stand on is this: As a permanent subproject under SIG Architecture after the Working Group archived, according to the Kubernetes contributor blog interview with AI Conformance leads dated October 29, 2026. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.
Second accounts
Secondary outlets repeated the primary's figures. When they add adjectives, the primary remains the record for the numbers this page will stand on. Asked directly, When is the spotlight dated? October 29, 2026, on the Kubernetes contributor blog. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.
What this page will not invent
Recipes, command lines, and reproduction steps stay out. Product, identifier where any, impact, and who is in scope are the filing. Asked directly, What changed organizationally? The AI Conformance Working Group archived after publishing initial requirements, and the work moved under SIG Architecture as a permanent subproject. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.
The record
The record is the primary named in the sources, plus the two supporting accounts. Until a later document revises the numbers, those pages are enough. Asked directly, What is the program's high-level aim? Vendor-neutral capabilities so AI and ML workloads behave more portably across conformant Kubernetes platforms. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
What changed organizationally?
The AI Conformance Working Group archived after publishing initial requirements, and the work moved under SIG Architecture as a permanent subproject.
When is the spotlight dated?
October 29, 2026, on the Kubernetes contributor blog.
What is the program's high-level aim?
Vendor-neutral capabilities so AI and ML workloads behave more portably across conformant Kubernetes platforms.
Is this the workload conformance charter brief?
Related desk, different document. Workload conformance was a separate charter filing.
Does this page list every MUST requirement?
No. It files the governance move and points to the public program repos.