Develop a Plugin
Invoke one Plugin locally, choose its distribution path, and prepare evidence before publication.
This page does not substitute for an unavailable published version. Check an exact version
- Locale
- en
- Content revision
sha256:7bfc24d60313ef6f7062d2d4a104a71c17b4b5b103e5ad9f3b89a27badd2c5da
A Plugin owns behavior behind a Capability. Its logical ID is separate from its package and release version. Choose a distribution path before copying commands from another Plugin; linked Rust, portable Rust, and Bun do not have the same build or installation steps.
Tutorial: invoke one Plugin
Create your first Plugin follows the standalone CLI path to scaffold, call, check, and package a portable Plugin. It is a Plugin development result, not a complete App or a signed Directory publication.
Tasks after the first call
| When you need to | Use |
|---|---|
| Select linked Rust, portable Rust, or Bun | Choose a Plugin path |
| Implement a native Plugin inside a Host | Linked Rust Plugin |
| Implement a Bun process Plugin | Bun Plugin authoring |
| Define a new typed role | Author a Capability |
| Describe documentation and source ownership | File conventions and Document sync |
Packaging a Plugin does not publish a signed catalog entry. The Plugin directory shows only the signed releases ingested and verified by this Site build; an unsigned candidate remains separate. Release availability, compatible targets, and installation must be checked against the exact release and the consuming App.
Reference and explanation
The Repository map identifies the current Rust and JavaScript owners. Plugins and Capabilities explains identity and binding; Drivers and Adapters explains what changes when the execution environment changes.