feat: checkpoint distributed gguf runtime stories
This commit is contained in:
@@ -0,0 +1,70 @@
|
||||
# DGR-011 — Blocked handoff
|
||||
|
||||
Status: blocked
|
||||
Date: 2026-07-15
|
||||
|
||||
## Blocker
|
||||
|
||||
This story cannot be completed in the current workspace state because its
|
||||
mandatory dependency, DGR-010, is still not passed.
|
||||
|
||||
Verified blockers:
|
||||
|
||||
- `.scratch/distributed-gguf-runtime/prd.json` still marks `DGR-010` and
|
||||
`DGR-011` with `"passes": false`.
|
||||
- `.scratch/distributed-gguf-runtime/evidence/DGR-010/README.md` does not
|
||||
exist, and the only DGR-010 evidence artifact present is
|
||||
`.scratch/distributed-gguf-runtime/evidence/DGR-010/BLOCKED.md`.
|
||||
- Mounted storage search found Qwen model artifacts and llama.cpp vocab files,
|
||||
but no certified dense-Llama GGUF artifact suitable for the required real
|
||||
acceptance run.
|
||||
|
||||
## Verified current state
|
||||
|
||||
- The repo already contains the Meshnet-facing GGUF backend seam and the
|
||||
recipe-gated startup path from DGR-009.
|
||||
- The architecture and Ralph context require real-model execution for this
|
||||
story, not synthetic workers or unit-only coverage.
|
||||
- The current environment does not expose the dense-Llama artifact required to
|
||||
run the prerequisite local real-model acceptance, so the two-machine route
|
||||
cannot be proven end to end.
|
||||
|
||||
## Commands run
|
||||
|
||||
```bash
|
||||
sed -n '1,260p' .scratch/distributed-gguf-runtime/RALPH-CONTEXT.md
|
||||
sed -n '1,260p' .scratch/distributed-gguf-runtime/issues/11-pass-a-real-heterogeneous-two-machine-route.md
|
||||
sed -n '1,260p' .ralph-tui/progress.md
|
||||
sed -n '1,240p' .scratch/distributed-gguf-runtime/evidence/DGR-010/BLOCKED.md
|
||||
sed -n '1,220p' CONTEXT.md
|
||||
sed -n '1,260p' docs/adr/0024-distributed-gguf-runtime.md
|
||||
sed -n '282,350p' .scratch/distributed-gguf-runtime/prd.json
|
||||
find /run/media/popov/d/DEV/models -maxdepth 3 \( -name '*.gguf' -o -name 'config.json' -o -name '*.safetensors' \)
|
||||
find /run/media/popov/d/DEV/llamacpp/llama.cpp/models /run/media/popov/d/DEV/models -maxdepth 4 \( -iname '*llama*' -o -iname '*dense*' -o -iname '*qwen*' -o -name 'config.json' -o -name '*.gguf' \)
|
||||
```
|
||||
|
||||
## Known limitations
|
||||
|
||||
- No certified dense-Llama artifact is available on mounted storage in this
|
||||
workspace.
|
||||
- No real two-machine execution was possible, so there are no real route,
|
||||
hardware, backend, or drift metrics to record for this story.
|
||||
- The story remains blocked until DGR-010 is completed with a real-model
|
||||
evidence README and a confirmed dense-Llama artifact on mounted storage.
|
||||
|
||||
## Compatibility notes
|
||||
|
||||
- DGR-009's recipe-gated GGUF backend seam is present and can be reused.
|
||||
- The acceptance path for this story still requires the upstream real-model
|
||||
evidence from DGR-010 before any heterogeneous two-machine route can be
|
||||
claimed.
|
||||
|
||||
## Dependent-story handoff
|
||||
|
||||
- Finish DGR-010 first, including its real-model evidence README and
|
||||
acceptance run.
|
||||
- Once DGR-010 passes, rerun the two-machine acceptance against the same
|
||||
certified dense-Llama artifact, then record the two-host hardware/network
|
||||
manifest, route, commands, and raw metrics in `evidence/DGR-011/README.md`.
|
||||
- Do not update the issue to `Status: done` until the real two-machine route
|
||||
has been executed and recorded.
|
||||
Reference in New Issue
Block a user