79 lines
3.5 KiB
Markdown
79 lines
3.5 KiB
Markdown
# DGR-015 — Blocked handoff
|
|
|
|
Status: blocked
|
|
Date: 2026-07-16
|
|
|
|
## Blocker
|
|
|
|
This story cannot be completed in the current workspace state because its
|
|
mandatory prerequisite, DGR-014, is still not passed.
|
|
|
|
Verified blocker chain:
|
|
|
|
- `.scratch/distributed-gguf-runtime/prd.json` still marks `DGR-014` as
|
|
`"passes": false`, so DGR-015 is not released for completion.
|
|
- `.scratch/distributed-gguf-runtime/evidence/DGR-014/BLOCKED.md` records the
|
|
release-gate blocker: the certified dense-Llama artifact required for the
|
|
comparable real-model comparison is not mounted on this machine.
|
|
- `DGR-014` depends on `DGR-011`, which is also blocked because `DGR-010`
|
|
cannot run without that same certified dense-Llama artifact.
|
|
- The current codebase still fails closed for `qwen3` / `qwen3-moe` in
|
|
`packages/node/meshnet_node/boundary_adapter.py`, which is correct for the
|
|
current state but means no Qwen3 family recipe is certified yet.
|
|
|
|
## Verified current state
|
|
|
|
- Dense-Llama boundary semantics, Hot KV isolation, batching, and failure
|
|
semantics are already implemented and covered by prior stories.
|
|
- Qwen3 strings are present in tracker/model metadata, but they are not yet
|
|
backed by a certified architecture adapter or real-model acceptance evidence.
|
|
- No `evidence/DGR-015/README.md` exists yet because the acceptance criteria
|
|
could not be completed.
|
|
|
|
## Commands run
|
|
|
|
```bash
|
|
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/15-add-and-certify-a-qwen3-qwen3-moe-adapter.md
|
|
sed -n '1,260p' .scratch/distributed-gguf-runtime/architecture.md
|
|
sed -n '1,260p' CONTEXT.md
|
|
sed -n '1,260p' .scratch/distributed-gguf-runtime/prd.json
|
|
sed -n '1,260p' .scratch/distributed-gguf-runtime/evidence/DGR-014/BLOCKED.md
|
|
sed -n '1,260p' .scratch/distributed-gguf-runtime/evidence/DGR-013/README.md
|
|
sed -n '1,260p' .scratch/distributed-gguf-runtime/evidence/DGR-012/README.md
|
|
sed -n '1,260p' packages/node/meshnet_node/boundary_adapter.py
|
|
sed -n '1,260p' packages/node/meshnet_node/model_catalog.py
|
|
sed -n '1,220p' packages/node/meshnet_node/model_metadata.json
|
|
sed -n '1,260p' packages/tracker/meshnet_tracker/capability.py
|
|
sed -n '1,260p' packages/tracker/meshnet_tracker/server.py
|
|
rg -n "qwen3|qwen3-moe|Qwen3|MoE|router|top-k|shared expert|shared_expert|expert" packages/node/meshnet_node packages/tracker/meshnet_tracker tests -g '!**/__pycache__/**'
|
|
git status --short
|
|
```
|
|
|
|
## Known limitations
|
|
|
|
- No certified dense-Llama artifact is mounted, so DGR-014 cannot complete and
|
|
DGR-015 remains blocked behind it.
|
|
- No real consumer-hardware Qwen3 acceptance run was possible in this workspace.
|
|
- No code was changed in this iteration.
|
|
|
|
## Compatibility notes
|
|
|
|
- The current boundary adapter intentionally fails closed for uncertified
|
|
architectures. That is the correct behavior until a dedicated Qwen3 adapter is
|
|
implemented and certified.
|
|
- Existing dense-Llama coverage and Hot KV semantics remain the source of truth
|
|
for the shared protocol and cache behavior.
|
|
|
|
## Dependent-story handoff
|
|
|
|
- Finish `DGR-010`, `DGR-011`, and `DGR-014` first with a certified dense-Llama
|
|
artifact on mounted storage.
|
|
- Once the release gate passes, implement the Qwen3 family adapter as a separate
|
|
certified architecture rather than by extending dense-Llama with unchecked name
|
|
substitutions.
|
|
- Record the real-model Qwen3 parity, admission, memory, and communication
|
|
evidence in `evidence/DGR-015/README.md`, then update the issue status only
|
|
after the gate passes.
|