Flowchart · Kandev · doc-wide · balanced
How a plugin reaches the host
Validation and extraction lead to one supervised go-plugin process. Kandev delivers events and webhooks to that process, which calls back through the Host API; the SPA bundle remains optional.
How a plugin reaches the host
Kandev installs, verifies, and extracts a plugin before spawning a supervised go-plugin subprocess. The runtime receives bus events and external webhooks, calls the Host API, and can optionally load a native UI bundle in the SPA.
PACKAGE PIPELINE
SUPERVISED PLUGIN PROCESS
SPA SURFACE
DELIVER EVENT
WEBHOOK
PLUGIN CALLBACK
OPTIONAL UI
Install
plugin archive
Verify
manifest + package
Extract
safe contents
Spawn subprocess
supervised go-plugin
kandev delivers bus events
DeliverEvent
kandev relays webhook
HandleWebhook · external
Host API
plugin callbacks
SPA native UI
optional frontend bundle
PACKAGE / RUNTIME
EVENT / WEBHOOK
HOST API FOCAL