44 lines
1.6 KiB
Markdown
44 lines
1.6 KiB
Markdown
# DGR-001 downstream stop-condition handoff
|
|
|
|
Status: **DGR-001 is complete; native-track promotion is blocked by the immutable v1 verdict.**
|
|
|
|
This is no longer an execution-prerequisite blocker. The required real benchmark
|
|
ran successfully, every recipe completed at concurrency 1 and 4, artifacts were
|
|
verified, and deterministic/full test gates passed.
|
|
|
|
## Locked result
|
|
|
|
`contract-evaluation.json` records:
|
|
|
|
```text
|
|
verdict: stop
|
|
quality_lane_pass: false
|
|
speed_benefit: true
|
|
fit_benefit: true
|
|
stop_condition_met: true
|
|
```
|
|
|
|
The exact-revision BF16 GGUF quality lane compared every prompt but achieved
|
|
`0.3333` exact match and `0.9471` mean similarity against the Transformers BF16
|
|
reference. V1 requires `0.90` and `0.97`. Quantized Q4_K_M had substantial speed
|
|
and fit benefits, but the contract explicitly forbids speed from redeeming a
|
|
failed near-lossless quality lane.
|
|
|
|
## Scope of this stop
|
|
|
|
The measured baseline is Qwen2.5-0.5B on CPU using a CPU-only llama.cpp build.
|
|
It is not a Radeon, large-model, distributed, or native-shard result. Therefore:
|
|
|
|
1. Do not silently mark v1 promoted or weaken its thresholds after observing the
|
|
data.
|
|
2. Do not let DGR-004 or later runtime stories treat DGR-001 completion as a
|
|
positive promotion signal.
|
|
3. A human may choose one of these explicit paths:
|
|
- stop the native GGUF track as v1 directs;
|
|
- diagnose and fix the BF16 runtime divergence, then rerun the exact v1 plan;
|
|
- authorize a separately versioned GPU/large-model contract whose scope and
|
|
workload are locked before its measurements.
|
|
|
|
All raw evidence, configuration, artifacts, hashes, and reproduction commands
|
|
are in this directory and `README.md`.
|