go-exotic explores distributed inference planning in Go, inspired by exo. It uses go-pherence as the local runtime and separates deterministic placement from actual shard execution.
The current project is an orchestration and validation experiment, not a networked distributed-inference service.
The CLI and local web server expose peer capabilities, memory-weighted layer placement and route previews. An in-process simulator checks orchestration before any execution path is enabled.
The shard endpoint is disabled by default. Supplying a local model installs a go-pherence layer executor for bounded local development; it does not enable peer discovery or LAN generation.
Assigns model layers to advertised peer memory with stable, inspectable plans.
Shows the proposed layer and peer path without executing shards or modifying local models.
Uses go-pherence for model metadata, tokenisation, smoke generation and layer-range execution.
Exercises orchestration and failure paths without requiring several machines.
POST /shards/execute returns 503 shard execution disabled until a local executor is explicitly configured.
A Bun-built Preact/D3 dashboard presents status, capabilities, placement, routes and bounded local model inventory.