toki/iop
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
iop/apps/node
History
toki 7b90b7e5af refactor(chronos): IOP 경계를 분리한다 
Chronos 이전 완료 증거를 보존하면서 IOP에는 provider 실행 책임만 남기기 위해 검토된 마일스톤 변경을 하나의 승격 커밋으로 고정한다.
2026-08-02 19:29:30 +09:00
..
cmd/node refactor(chronos): IOP 경계를 분리한다 2026-08-02 19:29:30 +09:00
internal refactor(chronos): IOP 경계를 분리한다 2026-08-02 19:29:30 +09:00
README.md refactor(chronos): IOP 경계를 분리한다 2026-08-02 19:29:30 +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.

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.