Architecture

Kunagi is scoped as four separate systems. Each can be built and validated independently, which keeps the hardest parts of the compute protocol from blocking the initial product.

App and API

Chat interface, model selection, streamed responses, account state, usage accounting, and API access.

Inference backend

Model serving, job queues, route selection, fallback GPU supply, and real time response streaming.

Token and staking vault

Holder staking, reward distribution, and later worker boosts. Holder staking and worker bonding stay separate in the implementation.

Compute marketplace

Worker client, worker registry, capability benchmarks, job assignment, earnings, reputation, and verification.