SyslogSolution/prose-contracts
7
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

v5: Full per-agent isolation separate ledgers, writer registries, canaries. No data crosses agent boundaries.

Browse Source
This commit is contained in:
Jerome
2026-06-29 01:47:10 +00:00
parent 9cf428579c
commit 9813c12895
1 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
memory-audit-maintenance.prose.md
+12 -4
View File
@@ -14,7 +14,7 @@ Autonomously audit and reorganize an agent's native memory (MEMORY.md, USER.md,
### 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.
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, no shared canary. The contract is the standard; each agent enforces it independently with fully isolated data.
**Agent Roster:**
- Mumuni
@@ -22,6 +22,13 @@ This contract is the **Hermes Agent standard** for memory maintenance. It is sha
- Koby
- Koonimo
**Isolation Principle:** Each agent has its own:
- `MEMORY.md` and `USER.md`
- `MEMORY_AUDIT_LEDGER.md` (audit trail)
- `MEMORY_WRITERS.md` (writer registry)
- Canary entries
- No data crosses agent boundaries
### 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.
@@ -39,7 +46,7 @@ Any entries that could not be autonomously categorized. Material: the entry text
Active alerts from drift detection (e.g., deletions accelerating, unverified configs growing). Material: the alert list.
#### ledger
Persistent audit trail stored at `~/.hermes/memories/MEMORY_AUDIT_LEDGER.md`. Material: append-only, never modified or deleted.
Persistent audit trail stored at the agent's own `~/.hermes/memories/MEMORY_AUDIT_LEDGER.md`. Material: append-only, never modified or deleted. Each agent has its own ledger no shared ledger across agents.
### Continuity
@@ -70,8 +77,9 @@ Persistent audit trail stored at `~/.hermes/memories/MEMORY_AUDIT_LEDGER.md`. Ma
- No duplicate entries survive across MEMORY.md and USER.md
- No session note or temporary state survives past 14 days
- No config is trusted without verification (or marked UNVERIFIED)
- The audit ledger is append-only never modified or deleted
- The audit ledger is append-only never modified or deleted, and is isolated per agent
- The canary entry survives every audit unmodified
- No data crosses agent boundaries
### Execution
@@ -334,4 +342,4 @@ return {
### 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.
Each Hermes agent (Mumuni, Tanko, Koby, Koonimo) runs this contract against its own `~/.hermes/memories/` directory. The contract is identical across agents, but all data is fully isolated: separate ledgers, separate writer registries, separate canaries. If a new agent is added to the roster, it must be listed in `### Scope` above and given its own isolated memory directory.