DGR-025: Define exact artifact and runtime recipe identity #9
Reference in New Issue
Block 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-025: Define exact artifact and runtime recipe identity
passes: trueAFKM1DGR-018,DGR-021DGR-026,DGR-031,DGR-041,DGR-044area:identity,area:admission,type:domain,priority:p0,ready-for-agentmodel-freenonegenericnoObjective / description
Fresh Ralph session: read
.scratch/distributed-gguf-runtime/RALPH-CONTEXT.md, source issue.scratch/distributed-gguf-runtime/issues/025-define-exact-artifact-and-runtime-recipe-identity.md, and evidence READMEs for dependencies (DGR-018, DGR-021) before changing code. Inspect live source/tests rather than trusting legacy pass states. Objective: Ensure the tracker and worker only combine numerically and operationally compatible shards.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
Verified evidence:
.scratch/distributed-gguf-runtime/evidence/DGR-025/README.md. Legacy evidence remains provenance only and grants no implementation completion credit.Controller verification complete for DGR-025. Published commits
ad66f7aand independent-review repairdb59caatoralph/distributed-gguf-runtime. Gates: 202 impacted identity/admission tests passed, 108 PRD-schema tests passed, conformance vectors matched, 55-story validation passed, compileall/diff-check passed. Independent re-review: PASS, no remaining P0/P1. Native identity now derives the committed lock-backed pin; node and tracker independently reject forged/noncanonical llama.cpp runtime pins.Reopened after a later independent controller review reproduced two additional exact-identity blockers: mutable tokenizer references are accepted, and native identity attests the repository manifest rather than the executing runtime/build. DGR-031 continuation is paused while these acceptance gaps are repaired.
Controller tick ended with no worker process active. The fixed Fable worktree preserves the DGR-025 repair. Controller added executing-artifact SHA-256 to runtime identity so a different binary copying public lock values receives a different recipe fingerprint; 105 focused and 235 impacted tests passed, compileall/diff-check and 55-story PRD validation passed. Final independent no-P0/P1 review is still pending. Claim released to
status:ready; no work was reset or discarded.Policy audit: no worker is active and the dirty identity/attestation repair has not received final independent no-P0/P1 acceptance. Released to status:ready while preserving the detached worktree; no completion or integration credit is granted.
Policy audit: no worker is active and the dirty identity/attestation repair has not received final independent no-P0/P1 acceptance. Status remains ready; the detached worktree is preserved and no completion or integration credit is granted.
REAL-IMPLEMENTATION CONTINUATION (2026-07-19): the durable workers are now executing repair/verify passes under the hard no-fake/stub/synthetic policy. Fake/in-memory artifacts are being removed and replaced with real generated-gRPC / upstream-patch / runtime-identity behavior. No completion credit is granted until independent review and integrated-branch gates pass.