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

story: DGR-037 Bind llama.cpp to the standalone worker

Browse Source
This commit is contained in:
Dobromir Popov
2026-08-01 01:28:06 +03:00
parent dfa403adc6
commit 8217b4c4a2
9 changed files with 482 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
packages/node/native/README.md
View File

@@ -76,3 +76,26 @@ self-consistent. Instead:
Byte equality across the two implementations is the claim; anything less is two
parallel test suites that can drift apart.
## DGR-037 standalone llama.cpp worker
`shard_worker` is no longer a model-free fixture. It refuses to start until it
can load one exact, range-attested GGUF identity through the pinned patched
llama.cpp library. Supply these environment variables from the node-owned
recipe/materialization layer (never from a stream request):
```bash
MESHNET_MODEL_ARTIFACT=/mounted/models/model.gguf \
MESHNET_MODEL_ARTIFACT_DIGEST=sha256:<artifact> \
MESHNET_RUNTIME_RECIPE_DIGEST=sha256:<recipe> \
MESHNET_RECIPE_ID=dense-llama MESHNET_RECIPE_VERSION=1 MESHNET_CATALOGUE_VERSION=1 \
MESHNET_SHARD_START_LAYER=0 MESHNET_SHARD_END_LAYER=32 \
build/native/shard_worker 127.0.0.1:50051
```
The worker publishes that loaded identity and llama.cpp-derived resident bytes
in capability/health responses, and only accepts the exact same range and
fingerprint at `SessionOpen`. `MESHNET_INJECT_PROCESS_DEATH_AFTER_EXECUTIONS=N`
is an opt-in test hook: after the Nth admitted execution the process exits 70,
which is intentionally observable by the future node supervisor; it is not a
recover-in-process mechanism.