haeres
Latin: heir, inheritor
Knowledge inheritance for AI agents. DNA for LLMs.
pip install haeres
The idea
Tasks execute and die. The knowledge they discover shouldn't die with them.
In biology, organisms are ephemeral but genes persist across generations. The same pattern applies to AI agents: each instance is temporary, but the knowledge it produces can outlive it — shaping how future instances think and act.
haeres is the mechanism of inheritance. A shared directory where agents leave knowledge for future agents to find. No server, no framework, no SDK. Just files.
| Biology | AI system |
|---|---|
| Genes | Skills (persistent knowledge) |
| Organisms | Tasks (executed, then gone) |
| Bodies | Agents (commodity instances) |
| Heredity | haeres |
| Natural selection | Human review |
Usage
Python
from haeres import post, read, clear
# A task discovers something — leave it for the next generation
post("KIID shows 0.42% TER but Morningstar shows 0.45%",
sender="avantis-verify", to="finance-tasks", severity="action")
# Next generation reads what predecessors learned
msgs = read(to="finance-tasks")
# Knowledge consumed — clear it
clear(msgs[0]["id"])
CLI
haeres post "Found NAV discrepancy" --from avantis-verify --to terry -v action
haeres list --to terry
haeres clear 2026-03-20-1915-nav-discrepancy
haeres archive --all
MCP
haeres includes an MCP server, making it available as native tools for any MCP-connected LLM:
haeres-mcp # starts the MCP server
Any agent, any platform
No SDK needed. Any agent that can read and write files can inherit:
cat > ~/notes/ACTA/2026-03-20-message.md << 'EOF'
---
from: my-skill
to: all
severity: info
ts: 2026-03-20T19:15+0800
---
Knowledge that should outlive this task.
EOF
Design principles
- Agents are commodity instances. Every LLM invocation is interchangeable.
- Skills are the identity. Knowledge comes from what you load, not who you are.
- Files are the communication layer. Durable, cross-platform, survives reboots.
- Async over sync. Like the endocrine system, not the nervous system.
Configuration
export ACTA_DIR=/path/to/shared/board # default: ~/notes/ACTA
License
MIT
Metadata
Release files for haeres 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| haeres-0.1.0.tar.gz | 6.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| haeres-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.8 kB
Release files / haeres-0.1.0.tar.gz
| Download URL | haeres-0.1.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7391e1283f7076ec361fda2e9c03a25d91efe81eb43fad2c7383d5956a1625d6
|
|
BLAKE2b-256 checksum How to use checksums |
0e2dcd6b8c1ee73958544349fc8c65ca888cc035d4487b85d307495aae5cfed5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / haeres-0.1.0-py3-none-any.whl
| Download URL | haeres-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c5816bdb346d916192bf09fc8bb9dbd1da22496e897c06bf0c0e5e91175bfd2e
|
|
BLAKE2b-256 checksum How to use checksums |
99eb16b2b4946f057b36636da751f89928a91eb9296eb146b608924cdd394a76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for haeres 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.