From ab7386edf9f6457d05182f4ce0841e903ec815af Mon Sep 17 00:00:00 2001 From: brettin Date: Thu, 4 Jun 2026 09:06:34 -0400 Subject: [PATCH] Add RFC 006: capability registry vs spec Capability. Proposes companion platform-capability schema for registration API. Co-authored-by: Cursor --- contracts/rfcs/006-capability-registry-platform.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 contracts/rfcs/006-capability-registry-platform.md diff --git a/contracts/rfcs/006-capability-registry-platform.md b/contracts/rfcs/006-capability-registry-platform.md new file mode 100644 index 0000000..4c2db32 --- /dev/null +++ b/contracts/rfcs/006-capability-registry-platform.md @@ -0,0 +1,9 @@ +# RFC 006: Capability registry vs spec Capability + +## Problem + +Spec `Capability` requires `profile`, `executionContext`, `artifact`, smoke-test status enum. Platform registry exposes `capabilityType`, `routing`, `owner`, MAG metadata. + +## Proposal + +Companion `platform-capability.schema.json` for registration API; keep spec Capability for scientific artifact binding.