3.3 KiB
3.3 KiB
05 — Implement dense-Llama range-aware GGUF ownership
Status: ready-for-agent
Mandatory fresh-session context
- Read RALPH-CONTEXT.md completely before changing code.
- This issue is
DGR-005in 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 node, I need to map only my assigned dense-Llama Shard so that aggregate consumer memory can hold a model larger than one node.
Expected durable outputs
- Dense-Llama range-aware ownership implementation
- Authoritative loaded-range introspection
- Mapped/resident memory evidence
- evidence/DGR-005/README.md
Acceptance criteria
- Register and allocate only
blk.N.*tensors in the assigned range. - Load embeddings only for the head and final norm/LM head only for the tail, including tied embeddings.
- Prefer range-aware mapping from one exact source GGUF; if derivative sub-GGUFs are used temporarily, verify source/slice hashes and avoid claiming final artifact semantics.
- Report authoritative loaded range and endpoint ownership from the model, not operator CLI claims.
- Demonstrate mapped/resident memory scales with owned tensors rather than full model size.
- 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
- 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-005/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-003must havepasses: true; read../evidence/DGR-003/README.mdand verify its referenced files/commands.DGR-004must havepasses: true; read../evidence/DGR-004/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.