3.4 KiB
3.4 KiB
11 — Pass a real heterogeneous two-machine route
Status: ready-for-agent
Mandatory fresh-session context
- Read RALPH-CONTEXT.md completely before changing code.
- This issue is
DGR-011in prd.json. - Read the evidence README for every dependency listed below.
- Inspect current code and
git status; historical text and previous agent claims are not evidence.
Description
As a consumer-hardware operator, I need two physical machines to execute one GGUF model so that the distributed claim is real.
Expected durable outputs
- Two-machine hardware/network/runtime manifest
- Raw real-route metrics and output evidence
- evidence/DGR-011/README.md
Acceptance criteria
- Tracker selects two physical nodes with disjoint Shards and one exact certified recipe/compatibility class.
- Actual CPU/GPU execution occurs on both nodes; synthetic workers do not satisfy acceptance.
- Prefill/decode, concurrent-session isolation, telemetry, cancellation, and cleanup pass over the real transport/relay path.
- Exact hardware, network, backend, model hash, route, commands, and raw metrics are recorded.
- A model or recipe larger than one participating node's admitted memory is exercised when available.
- Output drift is measured and incompatible mixed backends fail closed.
- Targeted pytest tests pass
- python -m compileall packages tests passes for Python changes
- git diff --check passes
- Default tests remain deterministic, model-download-free, API-credit-free, and GPU-free
- Full deterministic pytest -q passes, or the exact pre-existing unrelated failure is recorded with a clean-tree reproduction
- Pinned native C++ target builds and focused CTest/protocol tests pass where native code is touched
- llama.cpp patch stack applies cleanly to the exact pinned commit where patch code is touched
- Real-model execution is opt-in through MESHNET_ENABLE_REAL_INFERENCE_TESTS=1 and records exact artifact/runtime/hardware evidence
- Model artifacts remain on the configured mounted-drive storage and never under /home
- Read .scratch/distributed-gguf-runtime/RALPH-CONTEXT.md and this story issue completely before changing code
- Read and verify every dependency evidence README before relying on dependency behavior
- Preserve all pre-existing working-tree changes and stage only files belonging to this story
- Write .scratch/distributed-gguf-runtime/evidence/DGR-011/README.md with files changed, exact commands and real results, limitations, compatibility notes, and dependent-story handoff
- Update only this story issue to Status: done after every acceptance criterion and quality gate passes
Dependency handoff
DGR-010must havepasses: true; read../evidence/DGR-010/README.mdand verify its referenced files/commands.
Finish contract
- Create the task evidence directory and durable handoff required above.
- Preserve real failures and blockers; never fabricate benchmark, model, test or hardware output.
- Change this issue to
Status: doneonly after all criteria pass. - Emit
<promise>COMPLETE</promise>only after the evidence handoff exists.