Memory infrastructure for the Hero stack — collections, conversion, Q&A, ontology extraction, embeddings, retrieval
- Rust 73.3%
- HTML 15.9%
- Shell 9.6%
- JavaScript 1%
- CSS 0.2%
7413da68c3
After `lab build ... --upload` publishes the 4 gnu daemons to the `latest` release, fetch ONNX Runtime 1.25.0 from microsoft/onnxruntime and upload three soname variants of the runtime as additional release assets: - libonnxruntime.so.1.25.0 (real file content) - libonnxruntime.so.1 (likely DT_NEEDED — same content) - libonnxruntime.so (link target — same content) Forgejo release assets are flat, so each variant carries the full ~10MB real-file payload. lab consumer-side (--download --install) drops each into ~/hero/lib/ verbatim and writes ~/hero/cfg/env/lib.sh so a bootstrap that sources both env.sh and lib.sh can launch hero_memory daemons against the bundled runtime without apt installing onnxruntime system-wide. ORT_VERSION matches the comment in crates/*/Cargo.toml pinning ort = "=2.0.0-rc.12" (paired with ONNX 1.25.x). Bump both if either moves. DELETE-then-POST gives upload idempotency on workflow_dispatch reruns. |
||
|---|---|---|
| .forgejo/workflows | ||
| crates | ||
| docs | ||
| scripts | ||
| .gitignore | ||
| build.sh | ||
| Cargo.lock | ||
| Cargo.toml | ||
| Cargo.toml.hero_builder_backup | ||
| download_models.sh | ||
| favicon.svg | ||
| install.sh | ||
| MACOS_ONNX_FIX.md | ||
| MAKEFILE_ROBUSTNESS.md | ||
| OAUTH_DEBUG.md | ||
| openrpc.json | ||
| PURPOSE.md | ||
| README.md | ||
Hero Memory
Hero Memory is the memory infrastructure for the Hero stack. A single service that ingests documents and code, organises them into collections, extracts Q&A pairs and ontological graph structure, generates embeddings, and serves retrieval to agents.
It owns the pipeline from raw bytes to retrievable memory. It is not a
database (hero_db stores graph rows it produces) and it is not a model
server (hero_aibroker answers LLM calls; hero_memory_inference runs
the embedding models). It is the layer in between.
Documentation
- PRD — product requirements: what hero_memory does and the interfaces it exposes.
- ADRs — architecture decisions, with rationale.
Status
Specification phase. Implementation tracked via Forgejo issues against this repository.