Ayuriel/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: clarify extension and adapter terms

Browse Source
This commit is contained in:
Gustavo Madeira Santana 2026-03-15 18:12:31 +00:00
parent 88cf5ef972
commit 1548728a28
No known key found for this signature in database
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/.internal/extension-host-migration/openclaw-extension-contribution-schema-spec.md
View File

@ -641,6 +641,12 @@ Ownership rule:
- extensions may own interaction logic and channel-specific rendering details
- the host owns namespace registration, dedupe, callback routing, approval persistence, and binding policy
Terminology clarification:
- plugin-specific behavior lives in the extension package
- transport-specific runtime behavior lives in that extension's `adapter.runtime` contribution
- the kernel only consumes generic contracts and must not learn Telegram-, Discord-, or plugin-specific behavior directly
### `capability.rpc`
Represents internal callable methods that are not agent tools.

7
docs/.internal/extension-host-migration/openclaw-kernel-extension-host-transition-plan.md
View File

@ -1004,6 +1004,13 @@ Decision:
In this model, a channel is not a special plugin subtype. It is an adapter contribution plus related optional descriptors.
Terminology clarification:
- the extension package is the installable unit
- a contribution is a normalized runtime or host surface emitted by that package
- transport-specific runtime behavior belongs in the package's `adapter.runtime` contribution
- the kernel remains generic and should not own product-specific behavior for any one extension or channel
An adapter runtime contribution should include only transport behavior:
- normalize ingress events