Skip to content

Added Project scope and intent for AI workflow interoperability#2163

Open
nataliesea wants to merge 1 commit into
cncf:mainfrom
nataliesea:patch-1
Open

Added Project scope and intent for AI workflow interoperability#2163
nataliesea wants to merge 1 commit into
cncf:mainfrom
nataliesea:patch-1

Conversation

@nataliesea
Copy link
Copy Markdown

Updating the README to provide more detail on the project's scope, goals, and interoperability requirements.

Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
@nataliesea nataliesea requested a review from a team as a code owner May 14, 2026 22:38
@github-actions github-actions Bot added needs-triage Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied) needs-kind Indicates an issue or PR that is missing an issue type or kind (a kind/foo label) needs-group Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied) and removed needs-triage Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied) needs-kind Indicates an issue or PR that is missing an issue type or kind (a kind/foo label) needs-group Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied) labels May 14, 2026
### Overview and Intent
AI developers today frequently work in fragmented local environments that are disconnected from cloud-native operational workflows. While emerging standards like ModelPack and OCI-aligned AI artifact initiatives provide the “packaging” foundations, there is no unified interoperability specification that defines how these artifacts must be structured, secured, and described to move seamlessly from a developers laptop into a Kubernetes-based production system.

The goal of this initiative is to define a minimal Interoperability Specification (a “Compliance Profile”) for AI Artifacts. Rather than rebuilding the OCI layer structure, this initiative defines the **Standardized Metadata Contract** that must exist on top of packaging formats like **ModelPack**. This ensures that any <a href="https://github.com/cncf/foundation/blob/main/style-guide.md#1-cloud-native-and-open-source" target="_blank">“Cloud-Native Ready”</a> AI artifact contains the mandatory identity, security, and runtime information required that enables a cohesive developer inner loop and GitOps-driven delivery.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't "Cloud-Native Ready" be better not to use a hyphen along with the style (https://github.com/cncf/foundation/blob/main/style-guide.md#1-cloud-native-and-open-source)?

## Project Scope & Intent - Cloud-Native AI Developer Workflow Interoperability

### Overview and Intent
AI developers today frequently work in fragmented local environments that are disconnected from cloud-native operational workflows. While emerging standards like ModelPack and OCI-aligned AI artifact initiatives provide the “packaging” foundations, there is no unified interoperability specification that defines how these artifacts must be structured, secured, and described to move seamlessly from a developers laptop into a Kubernetes-based production system.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be better to use "cloud native operational..." along with https://github.com/cncf/foundation/blob/main/style-guide.md#1-cloud-native-and-open-source?


### In-Scope Areas
#### 1. The Interoperability Specification
Define a structured, minimal specification for AI artifacts to be considered “Cloud-Native Interoperable”. This does not define OCI layering but specifies the mandatory metadata:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cloud-Native Interoperable ==> same comment in the above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants