neuron-tai/.scratch/distributed-gguf-runtime/evidence/DGR-043

DGR-043 evidence — GGUF inputs through existing tracker routing

Date: 2026-08-01
Authority: .scratch/distributed-gguf-runtime/prd.json (passes remains false; this is model-free integration evidence, not a hardware certification).

Implemented

• Added optional backend-neutral RoutingMeasurements to the existing capability report. It carries measured tokens/second, queue depth, seam latency, health, and reliability; reports that omit it retain their exact previous serialized shape.
• Extended the tracker’s existing sanitized CapabilityState and network-map capability view to retain the routing measurements with exact recipe, artifact/runtime fingerprint, half-open-range-derived coverage, capacity, backend, and certification facts.
• NativeShardRegistration now accepts this generic measurement block and adapts throughput and queue depth to the existing registration/heartbeat scoring inputs. The tracker continues to apply its established queue-adjusted throughput selection; no GGUF routing, balancing, billing, relay, provider, quantization, topology, or architecture branch was added.
• Added deterministic coverage tests showing that existing route formation excludes a dark candidate, forms a complete route only from matching exact fingerprints, and rejects a range otherwise covered only by a mismatched recipe.

Changed files

• packages/node/meshnet_node/capability.py
• packages/node/meshnet_node/native_registration.py
• packages/tracker/meshnet_tracker/capability.py
• packages/tracker/meshnet_tracker/server.py
• tests/test_native_registration.py
• .scratch/distributed-gguf-runtime/evidence/DGR-043/README.md
• .ralph-tui/progress.md

Commands and results

PYTHONPATH=packages/node:packages/tracker /home/popov/.hermes/hermes-agent/venv/bin/python -m pytest -q \
  tests/test_native_registration.py tests/test_node_capability.py \
  tests/test_runtime_recipe_identity.py

96 passed in 0.23s

PYTHONPATH=packages/node:packages/tracker /home/popov/.hermes/hermes-agent/venv/bin/python -m pytest -q \
  tests/test_dgr_performance_contract.py tests/test_native_activation_seam.py \
  tests/test_native_worker_supervisor.py tests/test_native_registration.py \
  tests/test_ralph_prd_schema.py

151 passed in 1.78s

/home/popov/.hermes/hermes-agent/venv/bin/python -m ruff check \
  packages/node/meshnet_node/capability.py \
  packages/node/meshnet_node/native_registration.py \
  packages/tracker/meshnet_tracker/capability.py \
  packages/tracker/meshnet_tracker/server.py tests/test_native_registration.py
python3 -m compileall -q packages tests
git diff --check

All checks passed; both remaining commands exited 0.

Default tests were model-download-free, API-credit-free, and GPU-free. No native source, protobuf, patch, model artifact, or mounted-drive content was changed; therefore native CMake/CTest, patch-stack, and real-hardware gates do not apply to this Python-only adapter.

Limitations

• The full HTTP tracker/admission and tracker-routing suites cannot bind an AF_INET listener in this sandbox. The attempted focused suite had 132 passes and 14 failures, all PermissionError: [Errno 1] Operation not permitted during socket creation. Model-free direct tracker parsing and route-formation tests cover this change; HTTP/billing/relay regression suites must be rerun in an environment that permits localhost sockets.
• Measurements are inputs, not self-certification. An exact native recipe remains dark until the existing tracker-owned certification ledger admits it, and worker health loss continues to withdraw the native capability.
• Seam latency is retained as a measured tracker capability input. Existing route latency learning remains the tracker-owned mechanism for end-to-end seam cost; this story intentionally does not alter its scoring algorithm.

Dependency handoff

• DGR-041: NativeShardRegistration, ExecutionCapacity, exact ShardIdentity, and the tracker certification ledger remain the only registration/admission path. Supply RoutingMeasurements from verified worker/telemetry observations; do not infer values from backend names, quantization labels, architecture, or stage topology.
• DGR-053/DGR-061: use the exposed opaque measurements and existing tracker routing mechanisms for real certified routes. Any real-run evidence must add artifact/split hashes, worker/upstream pins, backend/driver, hardware/network details, commands, and raw metrics.