Skip to content

Native bridge contract ​

Transport for native bridge calls uses stdio-json-v1.

Inside args.request, ISA Warden currently documents a native-json envelope.

8.1 Request frame ​

json
{
  "protocol": "native-json",
  "id": "req-1",
  "type": "request",
  "method": "task.start",
  "params": { "job": "demo" }
}

8.2 Response frame ​

json
{
  "protocol": "native-json",
  "id": "req-1",
  "type": "response",
  "result": { "taskId": "task-123" }
}

8.3 Event frame ​

json
{
  "protocol": "native-json",
  "type": "event",
  "event": "task.progress",
  "taskId": "task-123",
  "data": { "progress": 40 }
}

8.4 Error frame ​

json
{
  "protocol": "native-json",
  "id": "req-1",
  "type": "error",
  "error": "invalid params"
}

8.5 Native function naming ​

Use stable namespaced function names.

Examples already in the repo:

  • hello.native_server
  • data_warden.native_server
  • rsx.create_project

ISA Warden extension specification