Added Project scope and intent for AI workflow interoperability#2163
Open
nataliesea wants to merge 2 commits into
Open
Added Project scope and intent for AI workflow interoperability#2163nataliesea wants to merge 2 commits into
nataliesea wants to merge 2 commits into
Conversation
Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
github-actions
Bot
added
needs-triage
danieloh30
reviewed
May 17, 2026
danieloh30
reviewed
May 17, 2026
danieloh30
reviewed
May 17, 2026
Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
nataliesea
commented
May 18, 2026
nataliesea
left a comment
nataliesea
left a comment
Author
There was a problem hiding this comment.
Resolved feedback from @danieloh30
| Ensure the approach accounts for: | ||
| * Air-gapped and regulated environments | ||
| * Enterprise security and compliance requirements | ||
| * Regulated environments |
Member
There was a problem hiding this comment.
feels like a repeat of line 86. If its a separate deployment consideration, can you add more detals? if not, lets keep line 86 in favor of this
There was a problem hiding this comment.
Recommend that we separate air-gapped and regulated environment as they are separate concerns
| * **A Published Interoperability Spec:** A validated specification that existing tools can adopt to ensure cloud native readiness. | ||
| * **Cross-Tool Portability:** Demonstrated ability for an artifact built by one tool to be verified and deployed by a different runtime. | ||
| * **The "10-Minute Flow":** A successful reference implementation demonstrating the journey from a local idea to a running inference service on Kubernetes. | ||
| * **Ecosystem Alignment:** Broad adoption of the "Compliance Profile" metadata across CNCF and LF AI & Data communities. |
Member
There was a problem hiding this comment.
is the adoption achievable in the given timeframe of the initiative? This initiative will get the conversation started and adoption can be a follow up. wdyt?
| * **Agentic Assets:** Standardizing the packaging of “skills”, prompt templates and workflow definitions. | ||
| * To ensure interoperability, the internal format for skills will align with the <a href="https://agentskills.io/home" target="_blank">agentskills.io</a> community standard. | ||
| * The spec defines how these standardized skills are encapsulated into the OCI layers for consistent distribution and discovery. | ||
| * The initiative may leverage Skill DLC as the primary reference for demonstrating how these assets are dynamically loaded and managed. |
|
|
||
| #### 5. GitOps and Kubernetes Integration Patterns | ||
| Define the "Handoff" patterns for how artifacts transition into production cloud native systems. | ||
| * **GitOps Delivery Patterns:** Reference architectures for pulling compliant artifacts into Flux or Argo CD workflows. |
Member
There was a problem hiding this comment.
Should this support a step for verification of artifacts? like kitops init container, that deploys and verifies the artifacts before exiting - https://kitops.org/docs/deploy/#init-container
Member
|
@caldeirav - do you have time for a quick review? thanks |
sabre1041
reviewed
Jun 8, 2026
| ## Initiative description | ||
|
|
||
| Focus on the developer inner loop, everything an AI engineer does on a laptop/desktop before code or models ever reach CI/CD in a cloud-native environment: | ||
| Focus on the developer inner loop, everything an AI engineer does on a laptop/desktop before code or models ever reach CI/CD in a cloud native environment: |
There was a problem hiding this comment.
Suggested change
| Focus on the developer inner loop, everything an AI engineer does on a laptop/desktop before code or models ever reach CI/CD in a cloud native environment: | |
| Focus on inner loop development which incorporates everything an AI engineer does on a local environment before code or models ever reach CI/CD in a cloud native environment: |
| Focus on the developer inner loop, everything an AI engineer does on a laptop/desktop before code or models ever reach CI/CD in a cloud-native environment: | ||
| Focus on the developer inner loop, everything an AI engineer does on a laptop/desktop before code or models ever reach CI/CD in a cloud native environment: | ||
|
|
||
| * Local container workspaces: Reference inner loop workflow using desktop tooling such as Podman Desktop / Podman AI Lab for root-less, GPU-aware experimentation, including template images for PyTorch/LLM stacks and volume-mounted datasets. |
There was a problem hiding this comment.
Would a cloud IDE (such as Eclipse Che / Coder, etc) also be in scope?
Member
There was a problem hiding this comment.
For simplicity, I prefer that we stick to laptop/desktop. If we decide to include cloud IDE in scope, I would like the setup and management of it be out of scope, mainly to avoid any integration issues.
| Focus on the developer inner loop, everything an AI engineer does on a laptop/desktop before code or models ever reach CI/CD in a cloud native environment: | ||
|
|
||
| * Local container workspaces: Reference inner loop workflow using desktop tooling such as Podman Desktop / Podman AI Lab for root-less, GPU-aware experimentation, including template images for PyTorch/LLM stacks and volume-mounted datasets. | ||
| * Unified model build & run CLI: Hardening inference on developer machine and agentic frameworks to leverage container-based tooling so engineers can easily spin-up inference, RAG and multi-agent services locally with one command. |
There was a problem hiding this comment.
Unified model build & run CLI sounds awkward. Recommend a different set of terms for this goal
| Integrating the AI developer inner loop into an end-to-end CI/CD process leveraging cloud-native technologies and tooling | ||
| Integrating the AI developer inner loop into an end-to-end CI/CD process leveraging cloud native technologies and tooling | ||
|
|
||
| ## Initiative description |
There was a problem hiding this comment.
Should packaging and retrieval of AI artifacts/resources also be included i the description?
| ## Deliverable(s) or exit criteria | ||
|
|
||
| * An technical POC showing <10 min “idea-to-inference” path for cloud-native agent development on a developer laptop. | ||
| * An technical POC showing <10 min “idea-to-inference” path for cloud native agent development on a developer laptop. |
There was a problem hiding this comment.
Suggested change
| * An technical POC showing <10 min “idea-to-inference” path for cloud native agent development on a developer laptop. | |
| * An technical POC showing <10 min “idea-to-inference” path for cloud native agent development on a developer environment. |
Contributor
There was a problem hiding this comment.
shouldn't this be "in" a developer environment?
| * **Transparency Manifests:** Mandatory requirements for SBOM (Software Bill of Materials) generation and attachment for all artifact layers. | ||
| * **Provenance Metadata:** Defining the "Hardened Provenance" requirements to ensure the journey from local experimentation to a secure registry is immutable and documented. | ||
|
|
||
| The goal is to ensure artifacts are trusted and verifiable before entering CI/CD pipelines. |
There was a problem hiding this comment.
Some of the signing tools require that assets be made available in an OCI registry before signatures can be applied
| The goal is to ensure artifacts are trusted and verifiable before entering CI/CD pipelines. | ||
|
|
||
| #### 4. Developer Inner-Loop & Workflow Interoperability | ||
| Define the operational patterns that allow the specification to be utilized in a portable "laptop-to-cluster" journey. |
There was a problem hiding this comment.
Suggested change
| Define the operational patterns that allow the specification to be utilized in a portable "laptop-to-cluster" journey. | |
| Define the operational patterns that allow the specification to be utilized in a portable "local environment-to-cluster" journey. |
| Ensure the approach accounts for: | ||
| * Air-gapped and regulated environments | ||
| * Enterprise security and compliance requirements | ||
| * Regulated environments |
There was a problem hiding this comment.
Recommend that we separate air-gapped and regulated environment as they are separate concerns
| #### 7. Ecosystem Collaboration | ||
| This initiative will be developed in collaboration with: | ||
| * ModelPack and related OCI-aligned initiatives | ||
| * CNCF projects |
There was a problem hiding this comment.
ModelPack in the bullet point above is a CNCF project. Should we consolidate bullet points?
Contributor
There was a problem hiding this comment.
CNCF projects, such as ModelPack (if you also call out multiple projects here)
| * **A Published Interoperability Spec:** A validated specification that existing tools can adopt to ensure cloud native readiness. | ||
| * **Cross-Tool Portability:** Demonstrated ability for an artifact built by one tool to be verified and deployed by a different runtime. | ||
| * **The "10-Minute Flow":** A successful reference implementation demonstrating the journey from a local idea to a running inference service on Kubernetes. | ||
| * **Ecosystem Alignment:** Broad adoption of the "Compliance Profile" metadata across CNCF and LF AI & Data communities. |
There was a problem hiding this comment.
Would a blog post highlighting the outputs of this effort also be a desired success criteria?
Member
There was a problem hiding this comment.
+1. My hope is that this initiative will lead to more smaller and focussed initiatives within ecosystem and/or more opportunities to collaborate outside of CNCF ecosystem. A blog post with future direction/goals will be really helpful.
angellk
requested changes
Jun 9, 2026
| ## Deliverable(s) or exit criteria | ||
|
|
||
| * An technical POC showing <10 min “idea-to-inference” path for cloud-native agent development on a developer laptop. | ||
| * An technical POC showing <10 min “idea-to-inference” path for cloud native agent development on a developer laptop. |
Contributor
There was a problem hiding this comment.
shouldn't this be "in" a developer environment?
| ## 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. |
| ## 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. |
| Within this scope, the initiative will explore and document: | ||
| * **An Interoperability Profile Spec:** A set of mandatory annotation conventions and metadata requirements (the “Manifest Contract”). | ||
| * **Compliance & Trust Requirements:** Standards for signing, SBOMs, and openness classification. | ||
| * **Workflow Reference Patterns:** Validating the spec through “Laptop-to-Cluster” GitOps and runtime integration. |
Contributor
There was a problem hiding this comment.
yes, this is correct -- it doesn't have to be a laptop
| Ensure the approach accounts for: | ||
| * Air-gapped and regulated environments | ||
| * Enterprise security and compliance requirements | ||
| * Regulated environments |
| #### 7. Ecosystem Collaboration | ||
| This initiative will be developed in collaboration with: | ||
| * ModelPack and related OCI-aligned initiatives | ||
| * CNCF projects |
Contributor
There was a problem hiding this comment.
CNCF projects, such as ModelPack (if you also call out multiple projects here)
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
5 participants
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.