Skip to content

Added Project scope and intent for AI workflow interoperability#2163

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

Added Project scope and intent for AI workflow interoperability#2163
nataliesea wants to merge 2 commits 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
Signed-off-by: Natalie Fisher <53450897+nataliesea@users.noreply.github.com>
@github-actions github-actions Bot requested a review from danieloh30 May 18, 2026 21:39
Copy link
Copy Markdown
Author

@nataliesea nataliesea left a comment

Choose a reason for hiding this comment

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

Resolved feedback from @danieloh30

Copy link
Copy Markdown
Contributor

@danieloh30 danieloh30 left a comment

Choose a reason for hiding this comment

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

LGTM!

Ensure the approach accounts for:
* Air-gapped and regulated environments
* Enterprise security and compliance requirements
* Regulated environments
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

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

* **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.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

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.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

nit: add a link


#### 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.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

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

@savitharaghunathan
Copy link
Copy Markdown
Member

@caldeirav - do you have time for a quick review? thanks

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.

3 participants