Memory infrastructure for the Hero stack — collections, conversion, Q&A, ontology extraction, embeddings, retrieval
- Rust 71.4%
- HTML 16.3%
- Shell 9.9%
- Makefile 1.1%
- JavaScript 1%
- Other 0.3%
despiegk
b8a184e78b
Some checks failed
Test / test (push) Failing after 3s
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| crates | ||
| docs | ||
| scripts | ||
| .gitignore | ||
| build.sh | ||
| Cargo.lock | ||
| Cargo.toml | ||
| download_models.sh | ||
| favicon.svg | ||
| install.sh | ||
| MACOS_ONNX_FIX.md | ||
| Makefile | ||
| MAKEFILE_ROBUSTNESS.md | ||
| OAUTH_DEBUG.md | ||
| openrpc.json | ||
| 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.