How jonimoni09/hydra-stone works
Hydra-Stone combines two model formats and inference paths with a CLI, web console, Android app, and model-conversion/training workflows. The v1 engine runs ternary .hydra weights; the v2 container and MoE engine support transformer-style inference. The README documents the major cross-surface capabilities, while source excerpts are partial, so some connections below rely on that documentation and uncertain native wiring is omitted or marked unverified.
Main entry points: main.c CLI runner · server.js Console server · MainActivity.kt App coordinator · EngineInterface.kt Engine interface
Components 21
Model preparation
- GGUF converters
tools/gguf_to_hydra2.py - GGUF reader
tools/gguf_reader.py - Model training
tools/hydra_train.js
Inference runtime
- V1 engine
src/hydra_engine.c - V2 container
src/hydra_v2_container.c - MoE engine
src/hydra_moe.c - CLI runner
src/main.c
Web console
- Web console UI
public/app.js - Console server
server.js
Android app
- Chat UI
android/app/src/main/java/dev/hydrastone/ui/HydraApp.kt - App coordinator
android/app/src/main/java/dev/hydrastone/MainActivity.kt - Engine interface
android/app/src/main/java/dev/hydrastone/EngineInterface.kt - Android Hydra engine
android/app/src/main/java/dev/hydrastone/HydraEngine.kt - Android llama engine
android/app/src/main/java/dev/hydrastone/LlamaEngine.kt - Hydra JNI bridge
android/app/src/main/java/dev/hydrastone/HydraBridge.kt - Llama JNI bridge
android/app/src/main/java/dev/hydrastone/LlamaBridge.kt - Native Hydra JNI
android/app/src/main/cpp/hydra_jni.c - Native llama JNI
android/app/src/main/cpp/llama_jni.cpp
Other components
- User
- Training corpus
- GGUF model
Connections 23
- User → CLI runner: runs inference
- GGUF model → GGUF reader: decodes tensors
- GGUF reader → GGUF converters: supplies decoding
tools/gguf_to_hydra2.py - GGUF model → GGUF converters: converts model
- Training corpus → Model training: trains model
- User → Console server: uses console
- Console server → Web console UI: serves UI
- Web console UI → Console server: calls API
- Console server → Model training: invokes training
server.js - Console server → CLI runner: runs engine
- CLI runner → V1 engine: runs v1 inference
- CLI runner → V2 container: inspects v2
src/main.c - CLI runner → MoE engine: runs v2 inference
src/main.c - V2 container → MoE engine: provides model data
src/hydra_moe.c - User → App coordinator: uses app
- App coordinator → Chat UI: hosts UI
android/app/src/main/java/dev/hydrastone/MainActivity.kt - App coordinator → Engine interface: selects engine
android/app/src/main/java/dev/hydrastone/MainActivity.kt - Android Hydra engine → Engine interface: implements
android/app/src/main/java/dev/hydrastone/HydraEngine.kt - Android llama engine → Engine interface: implements
android/app/src/main/java/dev/hydrastone/LlamaEngine.kt - Android Hydra engine → Hydra JNI bridge: calls bridge
android/app/src/main/java/dev/hydrastone/HydraEngine.kt - Android llama engine → Llama JNI bridge: calls bridge
android/app/src/main/java/dev/hydrastone/LlamaEngine.kt - Hydra JNI bridge → Native Hydra JNI: native dispatch
- Llama JNI bridge → Native llama JNI: native dispatch