toki/iop
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
iop/apps/node
History
toki a704a2ce03 chore: 테스트 임시 산출물을 정리한다 
소스 트리에 남은 테스트 실행 부산물과 로컬 설정·DB·바이너리를 제거해 저장소 오염을 줄인다. 삭제한 디버그 스크립트의 readability 기준선도 함께 정리한다.
2026-08-06 20:01:57 +09:00
..
cmd/node refactor(execution): correct residual agent ownership wording 2026-08-02 21:12:36 +09:00
internal chore: 테스트 임시 산출물을 정리한다 2026-08-06 20:01:57 +09:00
README.md fix(transport): 터널 지연에 맞춰 heartbeat 경계를 보강한다 2026-08-02 22:30:25 +09:00

README.md

IOP Node

IOP Node connects to Edge, applies the provider configuration delivered during registration, and executes normalized inference or provider-tunnel requests.

Runtime boundary

  • Internal provider selection uses adapter + target.
  • session_id is opaque correlation only. Every request is an independent execution.
  • Cancellation requires a non-empty run_id and affects only that run.
  • Provider commands are limited to capabilities, transport status, and the Ollama API tunnel.
  • Standard inference, streaming, structured tools, usage, provider lifecycle, capacity, and reconnect behavior remain supported.
  • Edge and Node use a shared tunnel-tolerant liveness profile: a 30-second heartbeat interval and a 45-second response wait. This keeps long provider prefill or streamed-response backpressure from disconnecting a healthy Node; a connection that actually exceeds the wait closes as heartbeat_timeout and enters supervised reconnect.

Node does not manage interactive host programs, persistent conversations, terminal emulation, arbitrary host commands, local filesystem execution context, or local quota scraping.

Development

go test -count=1 ./apps/node/...
go test -race -count=1 ./apps/node/internal/node ./apps/node/internal/adapters/...
go vet ./apps/node/...

The wire contract is documented in agent-contract/inner/edge-node-runtime-wire.md. Shared provider primitives are documented in agent-contract/inner/execution-runtime.md.