SILVER/NODEDC_MISSION_CORE
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

feat(plugins): add runtime handshake boundary

Browse Source
This commit is contained in:
DCCONSTRUCTIONS
2026-07-17 19:50:01 +03:00
parent 24a47318f2
commit 9d51080d2e
22 changed files with 856 additions and 138 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/plugin-sdk/README.md
+16 -12
View File
@@ -36,8 +36,9 @@ The separate SDK v0alpha2 package establishes executable contracts for:
- independently revisioned enrollment, connectivity, and acquisition states;
- operation policy, request, acknowledgement, progress, completion, failure,
timeout, cancellation, secret reference, and idempotency boundaries;
- immutable pre-session runtime-action invocation and result envelopes used by
the active backend dispatcher;
- immutable runtime descriptor, activation handshake, lifecycle health,
action-invocation and action-result envelopes used by the active backend
dispatcher;
- canonical point cloud, pose, image, encoded video, and device-status streams;
- immutable evidence handles, raw transport records, lineage, and store
protocol;
@@ -57,18 +58,21 @@ Current host implementation references:
that frontend surface;
- `apps/control-station/src/core/runtime/` — normalized runtime envelope;
- `src/k1link/web/plugin_catalog.py` — strict backend manifest validation;
- `src/k1link/web/plugin_runtime.py` — host-owned allowlisted SDK-envelope action dispatcher;
- `src/k1link/web/plugin_runtime.py` — transport protocol, laboratory in-process
implementation and host-owned SDK-envelope action dispatcher;
- `src/k1link/web/device_plugin_composition.py` — manifest factory loader and
startup parity checks;
- `docs/adr/0003-device-plugin-ui-and-runtime-boundary.md` — accepted boundary
and extraction sequence.
fail-closed descriptor/handshake checks;
- `docs/adr/0011-laboratory-plugin-runtime-handshake-and-transport-seam.md` —
accepted control-plane seam and its explicit laboratory limits.
The existing lifecycle is fail-closed: inactive provider shells perform no
I/O, events are scoped by plugin ID, and selection cannot change until the
active plugin confirms teardown. Process isolation remains a later host
milestone. v0alpha2 models secret references and operation policy, but host
authorization and the actual secret vault remain separate implementation
responsibilities.
The existing lifecycle is fail-closed: a backend runtime stays `starting` until
its ID, version, host API and exact action set pass the handshake; inactive
provider shells perform no I/O; events are scoped by plugin ID; and selection
cannot change until the active plugin confirms teardown. `ready` health means
only that this control-plane contract is admitted. Process isolation remains a
later host milestone. v0alpha2 models secret references and operation policy,
but host authorization and the actual secret vault remain separate
implementation responsibilities.
The React surface is not yet an independently published npm package. Its alias
is intentionally narrow so plugin source cannot import Control Station