Memory infrastructure for the Hero stack — collections, conversion, Q&A, ontology extraction, embeddings, retrieval
- Rust 87%
- HTML 11.4%
- Shell 1.5%
- CSS 0.1%
Kristof
46f1856cd0
- Add screen-image pipeline: rasters in HTML/ebook now encoded as WebP (lossy for photos, lossless for graphics) with configurable max_width and quality; variants cached on disk under ~/hero/var/doc_generator/ - Emit a companion <name>-compact.pdf at lower JPEG quality (pdf_compact / pdf_compact_quality config options; both default on) - New ebook options: embed_images (base64 inline vs sibling folder) and external_links_new_tab (open http(s) links in a new tab) - Image resolution now retries with loose key (strips ordinal prefixes) so a reference to curve_of_life.png resolves to 4_curve_of_life.png - booklet.toml auto-creation now requires interactive confirmation; fails fast in --script / unattended mode to avoid building the wrong directory - Discover: skip _-prefixed and .-prefixed directories (archives, drafts) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .cargo | ||
| .forgejo/workflows | ||
| crates | ||
| docs | ||
| examples | ||
| .gitignore | ||
| booklet.toml | ||
| build.sh | ||
| Cargo.toml | ||
| Cargo.toml.hero_builder_backup | ||
| checks.toml | ||
| download_models.sh | ||
| favicon.svg | ||
| install.sh | ||
| MACOS_ONNX_FIX.md | ||
| MAKEFILE_ROBUSTNESS.md | ||
| OAUTH_DEBUG.md | ||
| openrpc.json | ||
| PURPOSE.md | ||
| README.md | ||
| STORAGE_HERODB_MIGRATION.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.