Processor Protocol

Attaches, drives, cancels, and detaches a plugin-owned processor.

Attaches, drives, cancels, and detaches a plugin-owned processor.

Field	Value
Protocol ID	`aster.processor`
Version	`1.0.0`
Compatibility range	`^1.0.0`
Requirement helper	`aster.processor.require(settings?)` via the protocol module
Provider helper	Not available until the protocol module declares a runtime service tag.

Settings

DefaultProtocolSettingsSchema (Record<string, unknown> | null).

Operation	Summary	Request	Response
`resolveProcessorLaunchCandidates`	Resolve compatible launch candidates for a plugin-owned processor.	Effect Schema (Objects)	Effect Schema (Union)
`invoke`	Run one Work-rooted delegated processor invocation through the aster.processor face.	Effect Schema (Objects)	Effect Schema (Objects)
`proposeOperatorRoute`	Evaluate one immutable pre-admission Operator packet without acquiring Work execution authority.	Effect Schema (Objects)	Effect Schema (Union)
`attach`	Attach processor continuity for a Task thread and Role.	Effect Schema (Objects)	Effect Schema (Objects)
`respond`	Drive one Processor turn to streamed events and a settled result.	Effect Schema (Objects)	Effect Schema (Objects)
`prewarm`	Best-effort performance hint to prepare processor continuity.	Effect Schema (Objects)	Effect Schema (Objects)
`invalidatePrewarm`	Discard idle prewarmed processor continuity that is older than the current runtime inventory revision.	Effect Schema (Objects)	Effect Schema (Objects)
`cancel`	Abort an in-flight run owned by the processor.	Effect Schema (Objects)	Effect Schema (Void)
`detach`	Release session continuity held by the processor.	Effect Schema (Objects)	Effect Schema (Void)

Register with aster.processor at 1.0.0 inside ^1.0.0.
Implement every operation: resolveProcessorLaunchCandidates, invoke, proposeOperatorRoute, attach, respond, prewarm, invalidatePrewarm, cancel, detach.
Decode requests and responses against the operation schemas listed above.
Run the protocol conformance kit where one exists: No named kit yet; providers are still expected to satisfy the registry schemas..

[
  {
    "kind": "provider_right",
    "protocol": "aster.processor"
  },
  {
    "kind": "model_spend"
  }
]