contenox
Browse docs/

modeld Blueprints

modeld is the native inference daemon behind the pure-Go contenox CLI. It exists because one user is never one process: VS Code windows, ACP clients, CLI sessions, and background commands all point at the same machine, the same data directory, and often the same workspace. Local inference cannot survive each of them owning the GPU independently.

The runtime’s ownership model:

Multiple frontends are allowed.
One per-user local runtime owner controls resident model sessions and live KV state.
Workspace mutations are serialized by lease.
Model artifacts are immutable once published.

modeld is that owner: started on demand by the first client, attached to by every frontend over local IPC, holding the single active model slot, hardware probing, capacity planning, and KV/session state behind the runtime/transport session contract. It serves the llama.cpp and OpenVINO backends and versions independently of the runtime.

Coordination and ownership

DocStatusWhat it covers
multi-client-coordination.mddecisionThe founding decision above: option analysis, invariants, decision matrix, acceptance tests
owner-coordination.mddecisionHow the owner is elected, reached, and recovered across Linux/macOS/Windows

Daemon architecture and lifecycle

DocStatusWhat it covers
interface-boundary.mddecisionState vs. compute: why modeld exposes a stateful session boundary, not the stateless provider interface
single-active-model-slot.mddecisionOne resident model per daemon; slot lifecycle, generations, eviction
provisioning-detection.mddecisionHow the runtime discovers/installs modeld and fails honestly when it is absent
version-decoupling.mdarchitecturemodeld versions independently of the runtime; selection by protocol compatibility
release-artifacts.mdpackagingDevice-built native dep bundles and final packages in the artifact store
setup-artifact-detection.mddesigncontenox setup download/verify/install flow; version-selection model updated by version-decoupling.md

Runtime strategy

DocStatusWhat it covers
effective-context/strategyLong effective context on one consumer accelerator: north star, architecture, parity contract, bench findings
coldstore-sizing-plan.mdplanDerived hot/cold KV sizing and the host-RAM cold store
lora-adapters.mdR&DLoRA adapters as “model variants”; identity, cache keying, native attach
speculative-execution.mdR&D / visionGuess-ahead decode strategies for modeld

Backends

DocStatusWhat it covers
llama/binding-ownership-options.mddecision recordContenox-owned direct llama.cpp shim over third-party bindings
llama/coding-node-plan.mdgraduation planThe local coding node on llama.cpp
llama/plumbing-log.mdlogImplementation record of the llama provider plumbing
openvino/coding-node-plan.mdresearch planThe local coding node on OpenVINO; proven out by the S-series logs
openvino/plumbing-handover.mdhandoverLocked decisions and state of the OpenVINO provider plumbing
openvino/s1-embedded-controls.mdlogS1: embedded pipeline controls
openvino/s1-5-genai-provider.mdlogS1.5: GenAI provider
openvino/s2-prefix-reuse.mdlogS2: prefix-cache reuse proof
openvino/s2-7-protocol-registry.mdlogS2.7: parser protocol registry
tensorrt-llm-backend.mdR&D / visionTensorRT-LLM against the modeld boundary
ortgenai-windows-ai.mdspikeORT GenAI / Windows ML as an AI PC backend track; can it express the modeld session shape
alternative-silicon.mdstrategyAI PC / alternative-silicon runtime strategy across candidate backends (NPU, QNN, Ryzen AI, RKLLM)

Contributor build/release docs live in docs/development/ (modeld-source-build.md, modeld-release-runbook.md, modeld-llama-backend.md).

Esc to close