DGR-014 — Blocked handoff

Status: blocked Date: 2026-07-16

Blocker

This release-gate story cannot be completed in the current workspace state because the prerequisite real-model comparison chain is still missing its certified dense-Llama artifact on mounted storage.

Verified blockers:

DGR-011 is still not passed in .scratch/distributed-gguf-runtime/prd.json.
DGR-011 is explicitly blocked in .scratch/distributed-gguf-runtime/evidence/DGR-011/BLOCKED.md.
DGR-011 depends on DGR-010, and DGR-010 is blocked because there is no certified dense-Llama artifact available on the mounted drive.
Current mounted-model storage still only shows Qwen artifacts and llama.cpp vocab GGUFs, not the certified dense-Llama GGUF/safetensors pair needed for a comparable real run.

Verified current state

The DGR-001 performance contract exists and defines the benchmark lanes, metrics, and stop condition that later release gates must keep unchanged.
The DGR-012 scheduler and DGR-013 failure semantics evidence are present and usable as supporting context, but they do not satisfy the real final comparison required here.
packages/node/meshnet_node/performance_contract.py already contains the contract metadata and a live endpoint benchmark shim, but there is no recorded DGR-014 release-gate run and no final immutable comparison artifact.
evidence/DGR-014/README.md does not exist yet because the acceptance criteria could not be completed.

Commands run

sed -n '1,260p' .claude/memory/MEMORY.md
sed -n '1,260p' .scratch/distributed-gguf-runtime/RALPH-CONTEXT.md
sed -n '1,260p' .scratch/distributed-gguf-runtime/issues/14-enforce-the-gguf-versus-safetensors-release-gate.md
sed -n '1,260p' .ralph-tui/progress.md
git status --short
sed -n '1,260p' .scratch/distributed-gguf-runtime/prd.json
sed -n '1,260p' .scratch/distributed-gguf-runtime/evidence/DGR-001/README.md
sed -n '1,260p' .scratch/distributed-gguf-runtime/evidence/DGR-012/README.md
sed -n '1,260p' .scratch/distributed-gguf-runtime/evidence/DGR-013/README.md
sed -n '1,260p' .scratch/distributed-gguf-runtime/evidence/DGR-011/BLOCKED.md
sed -n '1,260p' .scratch/distributed-gguf-runtime/evidence/DGR-010/BLOCKED.md
find /run/media/popov/d/DEV/models /run/media/popov/d/DEV/llamacpp/llama.cpp/models -maxdepth 4 \( -iname '*llama*' -o -iname '*deepseek*' -o -iname '*dense*' -o -name '*.gguf' -o -name '*.safetensors' -o -name 'config.json' \)

Known limitations

No certified dense-Llama artifact is mounted, so the real distributed safetensors-versus-GGUF comparison cannot be executed.
No immutable release-gate evidence can be produced without that artifact and the completed DGR-011 route comparison.
No code was changed in this iteration.

Compatibility notes

The DGR-001 contract remains the source of truth for thresholds and metric names.
Any future DGR-014 run must keep those thresholds unchanged and compare the same certified model/hardware/network scenario for both routes.

Dependent-story handoff

Finish DGR-010 and DGR-011 first with a certified dense-Llama artifact on mounted storage.
Then run the current distributed safetensors and distributed GGUF routes on the same comparable scenario, record the final numbers in evidence/DGR-014/README.md, and update the issue status only after the gate passes.

3.3 KiB Raw Blame History