popov/neuron-tai
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Projects Releases Wiki Activity

DGR-070: Enforce the DeepSeek V4 Flash beta gate #54

New Issue
Open
opened 2026-07-16 20:36:08 +00:00 by popov · 0 comments
popov commented 2026-07-16 20:36:08 +00:00
Owner
Copy Link

DGR-070: Enforce the DeepSeek V4 Flash beta gate

  • Status / triage: specification only; ready-for-human; passes: false
  • Execution mode: HITL
  • Milestone: M5
  • Dependencies: DGR-057, DGR-059, DGR-060, DGR-062, DGR-064, DGR-066, DGR-067, DGR-068
  • Blocks (derived): DGR-071
  • Labels: area:deepseek-v4, area:release, milestone:beta, priority:p0, gate:hitl, ready-for-human
  • Evidence class: release
  • Hardware: required
  • Model: deepseek-v4-flash
  • Upstream: yes

Objective / description

Fresh Ralph session: read .scratch/distributed-gguf-runtime/RALPH-CONTEXT.md, source issue .scratch/distributed-gguf-runtime/issues/070-enforce-the-deepseek-v4-flash-beta-gate.md, and evidence READMEs for dependencies (DGR-057, DGR-059, DGR-060, DGR-062, DGR-064, DGR-066, DGR-067, DGR-068) before changing code. Inspect live source/tests rather than trusting legacy pass states. Objective: Promote beta only after concurrency, resilience, long-context, MTP, scale, packaging, and speed gates pass.

Acceptance criteria

  • Evaluate all beta metrics against DGF-004 without changing thresholds after observing results.
  • Require V4 parity, batching/fairness, bounded backpressure, failure recovery, long-context correctness, MTP evidence, and dynamic 10+ stage evidence.
  • Publish the exact certified hardware/backend/recipe matrix; all other lanes remain dark.
  • Decision is beta, targeted optimization, or stop/rollback, with unresolved failures listed explicitly.
  • Applicable shared quality gates in prd.json pass, and the evidence handoff records exact commands/results, changed files, limitations, and dependency handoff.

Shared quality gates

  • Targeted deterministic tests pass; Python changes also pass python -m compileall packages tests.
  • git diff --check passes.
  • Default tests are model-download-free, API-credit-free, and GPU-free.
  • Evidence README records exact changed files, commands/results, limitations, and dependency handoff; no fabricated evidence or inherited completion credit.

Evidence handoff

Write and verify .scratch/distributed-gguf-runtime/evidence/DGR-070/README.md. Until every criterion and applicable gate has real evidence, this story remains passes: false. Legacy evidence is provenance only, not completion credit.

<!-- GENERATED FROM prd.json — DO NOT EDIT AS AN INDEPENDENT SOURCE. prd.json IS AUTHORITATIVE. --> # DGR-070: Enforce the DeepSeek V4 Flash beta gate - **Status / triage:** specification only; `ready-for-human`; `passes: false` - **Execution mode:** `HITL` - **Milestone:** `M5` - **Dependencies:** `DGR-057`, `DGR-059`, `DGR-060`, `DGR-062`, `DGR-064`, `DGR-066`, `DGR-067`, `DGR-068` - **Blocks (derived):** `DGR-071` - **Labels:** `area:deepseek-v4`, `area:release`, `milestone:beta`, `priority:p0`, `gate:hitl`, `ready-for-human` - **Evidence class:** `release` - **Hardware:** `required` - **Model:** `deepseek-v4-flash` - **Upstream:** `yes` ## Objective / description Fresh Ralph session: read `.scratch/distributed-gguf-runtime/RALPH-CONTEXT.md`, source issue `.scratch/distributed-gguf-runtime/issues/070-enforce-the-deepseek-v4-flash-beta-gate.md`, and evidence READMEs for dependencies (DGR-057, DGR-059, DGR-060, DGR-062, DGR-064, DGR-066, DGR-067, DGR-068) before changing code. Inspect live source/tests rather than trusting legacy pass states. Objective: Promote beta only after concurrency, resilience, long-context, MTP, scale, packaging, and speed gates pass. ## Acceptance criteria - [ ] Evaluate all beta metrics against DGF-004 without changing thresholds after observing results. - [ ] Require V4 parity, batching/fairness, bounded backpressure, failure recovery, long-context correctness, MTP evidence, and dynamic 10+ stage evidence. - [ ] Publish the exact certified hardware/backend/recipe matrix; all other lanes remain dark. - [ ] Decision is `beta`, `targeted optimization`, or `stop/rollback`, with unresolved failures listed explicitly. - [ ] Applicable shared quality gates in `prd.json` pass, and the evidence handoff records exact commands/results, changed files, limitations, and dependency handoff. ## Shared quality gates - Targeted deterministic tests pass; Python changes also pass `python -m compileall packages tests`. - `git diff --check` passes. - Default tests are model-download-free, API-credit-free, and GPU-free. - Evidence README records exact changed files, commands/results, limitations, and dependency handoff; no fabricated evidence or inherited completion credit. ## Evidence handoff Write and verify `.scratch/distributed-gguf-runtime/evidence/DGR-070/README.md`. Until every criterion and applicable gate has real evidence, this story remains `passes: false`. Legacy evidence is provenance only, not completion credit. <!-- ralph-story-id: DGR-070 -->
popov added this to the M5 milestone 2026-07-16 20:36:08 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Blocked by incomplete dependencies or human gate
 status:completed
Completed and verified in prd.json
 status:in-progress
Currently selected by Ralph
 status:ready
Ready for Ralph execution
 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
No Label area:deepseek-v4 area:release gate:hitl milestone:beta priority:p0 ready-for-human status:blocked
Milestone
No items
No Milestone M5
Projects
Clear projects
No project
Assignees
Clear assignees
deploy popov
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: popov/neuron-tai#54
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?