story: DGR-034 Implement dense-Llama range-aware GGUF ownership
This commit is contained in:
@@ -28,6 +28,12 @@ One numbered patch per concern (ADR-0024 local seams only):
|
||||
5. `0005-worker-range-report-hook.patch` (worker hooks) exposes the
|
||||
`llama_model_meshnet_range_report` C API the project-owned worker binds to
|
||||
and registers a model-free native fixture test for it.
|
||||
6. `0006-meshnet-range-report-tool.patch` (range reporting) adds the
|
||||
project-owned `meshnet-range-report` tool: it loads one GGUF artifact
|
||||
through the owned-range loader and prints a JSON document derived from the
|
||||
loaded model state — the owned-range report, the registered tensor set
|
||||
audited against the requested ownership, and backend-buffer byte counts.
|
||||
It never builds or runs a compute graph.
|
||||
|
||||
Meshnet routing, Tracker, gRPC, relay, billing, authentication, and telemetry
|
||||
remain outside this directory; the stack is checked for such control-plane
|
||||
|
||||
Reference in New Issue
Block a user