Jido.Plugin.Manifest
(Jido v2.0.0-rc.4)
View Source
The manifest representation of a plugin's metadata and capabilities.
Contains all compile-time metadata about a plugin for discovery,
introspection, and ecosystem tooling. Unlike Jido.Plugin.Spec,
the manifest focuses on what the plugin provides rather than
per-agent runtime configuration.
Fields
module- The plugin modulename- Plugin name stringdescription- Optional descriptioncategory- Optional category for organizationtags- List of tag strings for categorizationvsn- Optional version stringcapabilities- List of atoms describing what the plugin providesrequires- List of requirements like{:config, :token},{:app, :req},{:plugin, :http}state_key- Atom key for plugin state in agentschema- Zoi schema for plugin stateconfig_schema- Zoi schema for per-agent configactions- List of action modulessignal_routes- List of signal route tuples like{"post", ActionModule}schedules- List of schedule tuples like{"*/5 * * * *", ActionModule}signal_patterns- Legacy signal patterns for routingsubscriptions- Sensor subscriptions provided by this plugin
Summary
Types
@type t() :: %Jido.Plugin.Manifest{ actions: [atom()], capabilities: [atom()], category: binary(), config_schema: any(), description: binary(), module: atom(), name: binary(), otp_app: atom(), requires: [any()], schedules: [any()], schema: any(), signal_patterns: [binary()], signal_routes: [any()], singleton: boolean(), state_key: atom(), subscriptions: [any()], tags: [binary()], vsn: binary() }
Functions
@spec schema() :: Zoi.schema()
Returns the Zoi schema for Manifest.