dapack β€” catalogue manifest and router

The glue that turns the three dapack packs into one routed catalogue:

file what it is
manifest.json domains, measured capability manifests, TF-IDF detector, embedding-router centroids, file hashes
embed/nomic-embed.gguf the embedding model for the ensemble router (nomic-embed-text-v1.5 Q8, 140 MB)

Setup

Download the three packs and this repo's files into one directory:

mycatalog.dapack/
  manifest.json                  <- from this repo
  embed/nomic-embed.gguf         <- from this repo
  gguf/math.gguf                 <- R3n3r0/dapack-math      (graded_math.gguf)
  gguf/language.gguf             <- R3n3r0/dapack-language  (graded_language.gguf)
  gguf/code.gguf                 <- R3n3r0/dapack-code      (graded_code.gguf)

Then run it with the dapack runtime (binaries under Releases, nothing to compile):

./dapack serve mycatalog.dapack --addr :8080

The router is yours to choose

--router tfidf      bag-of-words, zero extra memory, ~0.1 ms
--router embed      dense centroids, ~145 MB VRAM, ~5 ms per request
--router ensemble   both mixed 30/70 β€” 44% β†’ 89% routing accuracy on a
                    frozen holdout; the two err on different prompts
--router auto       (default) ensemble when this repo's files are present,
                    tfidf otherwise

Whichever router runs, the capability gate is identical: a request needing a capability a pack has measurably lost is routed to a pack that has it, or refused with a reason.

Runtime, measurements and docs: https://github.com/R3n3r0/dapack

Downloads last month
16
GGUF
Model size
0.1B params
Architecture
nomic-bert
Hardware compatibility
Log In to add your hardware

We're not able to determine the quantization variants.

Inference Providers NEW
This model isn't deployed by any Inference Provider. πŸ™‹ Ask for provider support