Expand description
Capability manifest schema for subc modules.
All v1 modules are supervised singletons: one long-lived process per
per-user machine. The manifest intentionally has no cardinality field.
subc routes by module kind plus channel, while any finer demultiplexing
(for example, AFT’s per-project actor map) remains internal to the singleton
module.
Structs§
- Bindings
- External storage, vault, and identity bindings supplied through subc.
- Circuit
Breaker - Identity
Binding - Management
Operation - Operation exposed on the management plane.
- Model
Policy - Model selection policy for the LLM-runner that executes a scheduled task.
- Module
Manifest - A module’s full declared participation in the subc mesh.
- Observability
Surface - Observable state exposed on the management plane.
- Pipeline
Applies To - Provider/model selector for a pipeline stage.
"*"denotes wildcard. - Scheduled
Task - Scheduler-owned task declaration. The runner module executes the loop; subc owns eligibility checks and the lease.
- Storage
Binding - Storage backend supplied by subc; the module owns its schema.
- Task
Eligibility - Time/window gates for a scheduled task. Values are serialized policy strings (for example, durations or cron/window expressions) owned by the scheduler.
- Tool
- Tool-plane capability exposed by a
tool_provider. - Vault
Grant
Enums§
- Concurrency
- How subc may deliver concurrent in-flight calls to the provider.
- Consumer
Role - Consumer capabilities requested by a module.
- Execution
Mode - How a tool’s side effects are fenced for durable at-most-once handling.
- Identity
Scope - Identity keys that route or scope a call.
- Internal
Transport - Lease
Scope - Scope at which subc enforces one active scheduler lease.
- Management
Operation Kind - Observability
Kind - Pipeline
Stage Kind - Proxy-plane stage kind.
- Provider
Role - Provider capabilities exposed by a module.
- Storage
Kind - Storage
Scope - Trust
Tier - Trust gate applied by subc before routing capabilities.