abiba-bot/prose-contracts
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

v4: Add Hermes agent roster (Mumuni, Tanko, Koby, Koonimo), per-agent isolation notes

Browse Source
This commit is contained in:
Jerome
2026-06-29 01:40:14 +00:00
parent 9ac383e812
commit 9cf428579c
1 changed files with 15 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
memory-audit-maintenance.prose.md
+14
View File
@@ -12,6 +12,16 @@ Autonomously audit and reorganize an agent's native memory (MEMORY.md, USER.md,
(none this is a self-driven, autonomous node) (none this is a self-driven, autonomous node)
### Scope
This contract is the **Hermes Agent standard** for memory maintenance. It is shared across all Hermes agents (Mumuni, Tanko, Koby, Koonimo). Each agent runs it against its own memory files only no cross-agent access, no shared state, no shared ledger. The contract is the standard; each agent enforces it independently.
**Agent Roster:**
- Mumuni
- Tanko
- Koby
- Koonimo
### Maintains ### Maintains
Memory health state current utilization, last audit timestamp, drift alerts, and any unresolved ambiguities. Postcondition: no entry is duplicated, no session note or stale snapshot survives, no config is unverified, and the audit ledger is up-to-date. Memory health state current utilization, last audit timestamp, drift alerts, and any unresolved ambiguities. Postcondition: no entry is duplicated, no session note or stale snapshot survives, no config is unverified, and the audit ledger is up-to-date.
@@ -321,3 +331,7 @@ return {
- `USER_PATH`: ~/.hermes/memories/USER.md - `USER_PATH`: ~/.hermes/memories/USER.md
- `CONFIG_PATH`: ~/.hermes/config.yaml - `CONFIG_PATH`: ~/.hermes/config.yaml
- `LEDGER_PATH`: ~/.hermes/memories/MEMORY_AUDIT_LEDGER.md - `LEDGER_PATH`: ~/.hermes/memories/MEMORY_AUDIT_LEDGER.md
### Per-Agent Notes
Each Hermes agent (Mumuni, Tanko, Koby, Koonimo) runs this contract against its own `~/.hermes/memories/` directory. The contract is identical across agents, but the data is isolated. If a new agent is added to the roster, it must be listed in `### Scope` above.