docs: define distributed GGUF runtime plan
This commit is contained in:
@@ -1,5 +1,7 @@
|
||||
# Distributed GGUF Technical Challenge Register
|
||||
|
||||
> **Historical challenge register.** Route Session, binary activation, local Hot KV State, and transport performance work have advanced since this file was written. Current implementation gates live in [PRD.md](PRD.md), [implementation-strategy.md](implementation-strategy.md), [architecture.md](architecture.md), and [prd.json](prd.json). Preserve this file for detailed risk context; do not treat its “current constraint” section as live system state.
|
||||
|
||||
This document focuses on the engineering problems that decide whether the distributed GGUF path is viable. The important distinction is:
|
||||
|
||||
- **Model artifacts move like torrents.**
|
||||
|
||||
Reference in New Issue
Block a user