Distributed GGUF Runtime milestones

Specification status: planning artifacts only. No distributed GGUF runtime is implemented by this materialization, no story has completion credit, and legacy files remain for the DGR-017 audit. prd.json is authoritative.

M0 — Truth and contracts

Stories: DGR-017..DGR-020
Outcome: Reconciled legacy truth, canonical metadata, immutable gates, and a controlled whole-model baseline.

M1 — Protocol and native substrate

Stories: DGR-021..DGR-033
Outcome: Versioned gRPC protocol, exact identities/artifacts, pinned upstream, reproducible builds, ShardEngine, and fake worker.

M2 — Dense vertical proof

Stories: DGR-034..DGR-043
Outcome: Dense ranged execution, parity, local state, worker integration, and GGUF inputs to existing routing.

M3 — DeepSeek V4 Flash alpha

Stories: DGR-044..DGR-054
Outcome: Pinned V4 adapter around upstream llama.cpp, real route certification, and pre-locked alpha decision with MTP off.

M4 — Performance and beta hardening

Stories: DGR-055..DGR-067
Outcome: Batching, backpressure, recovery, scale certification, optimization, MTP, and hardware matrix.

M5 — Release and maintenance

Stories: DGR-068..DGR-071
Outcome: Reproducible packages, upstream collaboration, beta decision, and sustainable recertification.

Release semantics

Alpha is DGR-054 and requires correctness plus the immutable useful-speed contract; MTP remains off. Beta is DGR-070 and requires DGR-066 MTP evidence plus concurrency, recovery, long-context, 10+ scenario, compression/optimization where certified, hardware matrix, and packaging. Failed gates remain failed evidence; they are not relabeled as success.

1.7 KiB Raw Blame History