From e067080409074fb44f1f7d3d7d83d8714186c5f9 Mon Sep 17 00:00:00 2001 From: Jon Langevin Date: Sun, 24 May 2026 04:35:37 -0400 Subject: [PATCH] docs: clarify compute-core contract boundary --- README.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index b52bca2..c910416 100644 --- a/README.md +++ b/README.md @@ -3,10 +3,16 @@ Public Workflow plugin and Go module for compute protocol and provider catalog contracts. -Provider plugins use this module for shared JSON-compatible protocol types, -validation helpers, and canonical hashing. They also declare a plugin dependency -on `workflow-plugin-compute-core` in `plugin.json`, giving Workflow a registry -dependency anchor separate from runtime execution plugins. +Provider plugins use this module for shared compute provider-catalog data +types, validation helpers, and canonical hashing. They also declare a plugin +dependency on `workflow-plugin-compute-core` in `plugin.json`, giving Workflow a +registry dependency anchor separate from runtime execution plugins. + +This is distinct from the Workflow plugin runtime contract: external plugins +still expose their runtime capabilities through Workflow's gRPC/protobuf plugin +service contracts. The provider-catalog structs in `protocol/` are the typed +declaration data that provider plugins publish and `workflow-plugin-compute` +validates. This plugin intentionally advertises no module, step, trigger, or IaC runtime capabilities.