Expand description
Universal operation registry (spec §§6-8): every SCC capability
gets a stable operation ID; engine.operations().list() explains the
API and engine.invoke(id, input) executes it. Typed namespaces
(engine.context().task(..)) and dynamic invoke share ONE
implementation — there are never two paths to the same behavior.
Structs§
Enums§
Constants§
Functions§
- capabilities
- Capability vocabulary (§9): the permission names plugins request, the
extension-point names they register under, and the mutation classes
operations declare. Derived from the
scc_plugin_api::Permissionenum (single source) so docs can never drift from enforcement. - describe
- ids
- input_
schema - JSON Schema for one operation’s input (§9): generated from the canonical scc-api request type via schemars — the same struct invoke deserializes, so the schema can never drift from the implementation. Alias ops share their canonical op’s schema. Returns None for unknown ids.