Skip to content

feat: canonicalize provider contracts #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
intel352 merged 1 commit into from
May 24, 2026
+745 −44
Merged

feat: canonicalize provider contracts #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,14 @@ service contracts. The provider-catalog structs in `protocol/` are the typed
declaration data that provider plugins publish and `workflow-plugin-compute`
validates.

The public catalog contract includes provider identity, org/pool scoping,
access visibility, supported workload and network modes, runtime profiles,
operation schemas, artifact declarations, residue policy, and upstream client
conformance evidence. Workflow applications should treat these declarations as
the portable provider-facing base contract; application-specific scheduling,
task state, settlement, dashboards, and worker supervision remain outside this
core plugin.

This plugin intentionally advertises no module, step, trigger, or IaC runtime
capabilities.

Expand Down
Loading
Loading