Capabilities & Policy (meta)
meta-cluster:capabilities-policy
MetaClustercatalog-meta/meta-registry/meta-registry-capabilities-policy.yaml·Open in Graph → {
"id": "meta-cluster:capabilities-policy",
"_kind": "MetaCluster",
"_file": "catalog-meta/meta-registry/meta-registry-capabilities-policy.yaml",
"_cluster": "catalog-meta",
"attributes": {
"displayName": "Capabilities & Policy (meta)",
"clusterNumber": 8,
"scope": "Conceptual aggregation of NodeKinds describing the capability surface: Capability (a named, discriminated capability that versioned entities can support and extensions can require) and InstallMethod (a canonical install method — npm, brew, gh-extension, curl, … — referenced by AgentVersion.installMethods, Plugin install records, and Blueprint setup). The catalog update remodel removed CapabilitySupport as a NodeKind and moved its (entity, capability, version-range, level, evidence) tuple onto edge attributes of supports. Members live in editorial cluster 8-capabilities in ontology-schema.yaml.",
"parentClusterId": null
},
"outgoingEdges": [
{
"from": "meta-cluster:capabilities-policy",
"to": "meta-node-kind:capability",
"kind": "contains_meta_node_kind",
"attributes": {}
},
{
"from": "meta-cluster:capabilities-policy",
"to": "meta-node-kind:install-method",
"kind": "contains_meta_node_kind",
"attributes": {}
}
],
"incomingEdges": [
{
"from": "meta-node-kind:capability",
"to": "meta-cluster:capabilities-policy",
"kind": "in_cluster",
"attributes": {}
},
{
"from": "meta-node-kind:install-method",
"to": "meta-cluster:capabilities-policy",
"kind": "in_cluster",
"attributes": {}
},
{
"from": "ontology:v6-current",
"to": "meta-cluster:capabilities-policy",
"kind": "defines_meta_cluster",
"attributes": {}
}
]
}