DGR-024: Implement real generated-gRPC protocol harness #8
Closed
opened 2026-07-16 20:36:01 +00:00 by popov
·
6 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#8
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-024: Implement real generated-gRPC protocol harness
passes: trueAFKM1DGR-022,DGR-023DGR-033,DGR-042area:protocol,area:testing,type:vertical-slice,priority:p0,ready-for-agentmodel-freenonenonenoObjective / description
Build a real generated-gRPC protocol harness around the versioned shard_runtime.proto contract. Use generated Python and C++ stubs over an actual localhost transport and real process lifecycle; exercise captured deterministic protocol vectors and serialized protobuf bytes before a real model worker exists. Do not implement an in-memory fake transport, synthetic model outputs, or a production-looking stub/demo service.
Acceptance criteria
Shared quality gates
python -m compileall packages tests.git diff --checkpasses.Evidence handoff
Verified evidence:
.scratch/distributed-gguf-runtime/evidence/DGR-024/README.md. Legacy evidence remains provenance only and grants no implementation completion credit.Dependency reconciliation: DGR-022 and DGR-023 are now closed/completed. Moving to
status:ready.Claimed by the GPT-5.6 Terra protocol/testing lane after verified completion of DGR-023. One isolated Ralph iteration; controller review required before integration or closure.
Reclaimed after restart for independent-review repair. P1s: stale epoch isolation, prefill/decode flow-control plus in-band deadlines, bidirectional activation responses, and generated-stub-compatible in-memory gRPC lifecycle. Existing partial implementation is preserved; no completion until fresh review.
Controller tick ended with no worker process active. The fixed Terra worktree preserves the DGR-024 implementation; 76 focused/shared tests passed with 2 required skips, PRD validation/compileall/ruff/diff-check passed, and final independent no-P0/P1 review is still pending. Claim released to
status:ready; no work was reset or discarded.DGR-024: Implement in-memory fake gRPC seam transportto DGR-024: Implement real generated-gRPC protocol harnessPolicy audit completed: the former fake/in-memory seam specification was replaced in canonical PRD commit
54d19f9with a real generated Python/C++ gRPC localhost-process harness. The old dirty fake-seam files remain preserved but receive zero credit and must not be integrated.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.