Added Project scope and intent for AI workflow interoperability#2163
Open
nataliesea wants to merge 1 commit into
Open
Added Project scope and intent for AI workflow interoperability#2163nataliesea wants to merge 1 commit into
nataliesea wants to merge 1 commit into
Conversation
Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
danieloh30
reviewed
May 17, 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. |
Contributor
There was a problem hiding this comment.
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)?
danieloh30
reviewed
May 17, 2026
| ## 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. |
Contributor
There was a problem hiding this comment.
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?
danieloh30
reviewed
May 17, 2026
|
|
||
| ### 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: |
Contributor
There was a problem hiding this comment.
Cloud-Native Interoperable ==> same comment in the above
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updating the README to provide more detail on the project's scope, goals, and interoperability requirements.