DGR-067: Certify the backend capability matrix #51
Open
opened 2026-07-16 20:36:07 +00:00 by popov
·
0 comments
No Branch/Tag Specified
Labels
Clear labels
area:admission
area:artifacts
area:attention
area:backpressure
area:batching
area:boundary
area:build
area:certification
area:cleanup
area:compression
area:concurrency
area:deepseek-v4
area:engine
area:failure
area:gitea
area:grpc
area:hardware
area:identity
area:integration
area:kv-cache
area:lifecycle
area:llama
area:long-context
area:maintenance
area:meshnet
area:mhc
area:moe
area:mtp
area:node
area:packaging
area:parity
area:patches
area:performance
area:planning
area:protocol
area:provenance
area:recovery
area:relay
area:release
area:reliability
area:routing
area:routing-state
area:scale
area:scheduler
area:supervision
area:testing
area:tracker
area:upstream
area:weights
area:worker
gate:hitl
milestone:alpha
milestone:beta
priority:p0
priority:p1
priority:p2
ready-for-agent
ready-for-human
status:blocked
status:completed
status:in-progress
status:ready
type:architecture
type:audit
type:benchmark
type:certification
type:collaboration
type:contract
type:delivery
type:domain
type:fixture
type:hardening
type:infrastructure
type:integration
type:operations
type:optimization
type:performance
type:protocol
type:provenance
type:research-spike
type:runtime
type:simulation
type:toolchain
type:tooling
type:vertical-slice
Blocked by incomplete dependencies or human gate
Completed and verified in prd.json
Currently selected by Ralph
Ready for Ralph execution
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: popov/neuron-tai#51
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
DGR-067: Certify the backend capability matrix
ready-for-human;passes: falseHITLM4DGR-030,DGR-053,DGR-062,DGR-066DGR-068,DGR-070area:hardware,area:admission,type:certification,priority:p1,gate:hitl,ready-for-humanreal-hardwarerequireddeepseek-v4-flashyesObjective / description
Fresh Ralph session: read
.scratch/distributed-gguf-runtime/RALPH-CONTEXT.md, source issue.scratch/distributed-gguf-runtime/issues/067-certify-the-backend-capability-matrix.md, and evidence READMEs for dependencies (DGR-030, DGR-053, DGR-062, DGR-066) before changing code. Inspect live source/tests rather than trusting legacy pass states. Objective: Publish only backend/model/recipe lanes proven on actual CPU, CUDA, ROCm, Vulkan, or Metal hardware.Acceptance criteria
prd.jsonpass, and the evidence handoff records exact commands/results, changed files, limitations, and dependency handoff.Shared quality gates
python -m compileall packages tests.git diff --checkpasses.Evidence handoff
Write and verify
.scratch/distributed-gguf-runtime/evidence/DGR-067/README.md. Until every criterion and applicable gate has real evidence, this story remainspasses: false. Legacy evidence is provenance only, not completion credit.