waittim/MemoryCustodian / skills/memory-custodian
memory-custodian
FlaggedUse when a project contains docs/memory/, or when the user asks to remember, retrieve, update, compact, forget, or audit project memory. MemoryCustodian manages local plain-text project memory with minimal context loading.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.6 KB |
| references/admission-policy.md | markdown | 1.1 KB |
| references/compaction-policy.md | markdown | 4.2 KB |
| references/examples.md | markdown | 2.1 KB |
| references/forgetting-policy.md | markdown | 6.9 KB |
| references/local-overlay-policy.md | markdown | 1.5 KB |
| references/manifest-policy.md | markdown | 2.9 KB |
| references/memory-file-protocol.md | markdown | 22.3 KB |
| references/migration-policy.md | markdown | 2.7 KB |
| references/output-contract.md | markdown | 4.3 KB |
| references/platform-adapters.md | markdown | 3.9 KB |
| references/quality-audit.md | markdown | 15.4 KB |
| references/routing-policy.md | markdown | 2.0 KB |
| references/transaction-policy.md | markdown | 4.1 KB |
references/output-contract.md
View on GitHub# Protocol 0.8 Output and Audit Contract
MemoryCustodian 0.12 uses Protocol 0.8, Entry schema 3, transaction schema 1,
audit schema 1, output schema 1, and ErasureScope schema 1. Subject,
conflict, routing, and local-overlay schema versions remain independently
declared by the manifest/state authority described in `manifest-policy.md`.
## Public envelope
`--format text` is the human renderer and `--format json` emits exactly one
UTF-8 JSON document on stdout. `--json` MAY remain a compatibility alias, but
documentation and fixtures use `--format json`. Fatal argument/runtime errors
are written to stderr; domain validation failures in JSON mode still return a
valid envelope:
```json
{
"output_schema_version": 1,
"command": "audit",
"protocol_version": "0.8",
"status": "REVIEW",
"exit_class": "success-with-review",
"data": {"audit_schema_version": 1},
"findings": [],
"disclaimers": []
}
```
Top-level `status` is only `PASS`, `REVIEW`, or `FAIL`. `exit_class` is one of
`success`, `success-with-review`, `domain-failure`, `blocker`, or `fatal`.
PASS/REVIEW return 0, ERROR/domain-failure returns 1, and BLOCKER/fatal
returns 2. A finding has a stable code, one of `INFO`, `WARNING`, `ERROR`, or
`BLOCKER`, a repository-relative POSIX path (or a stable private alias), an
optional Entry ID, message, and remediation. WARNINGS produce REVIEW; ERROR
or BLOCKER produces FAIL. Text and JSON render the same result model.
Project audit (`audit`) checks persistent project state; invocation audit
(`read --explain` or `audit --routing-input`) checks one context route; the
repository check scripts check this source tree. They MUST NOT become three
independent routing, conflict, or severity implementations. `audit --format
json` places `audit_schema_version: 1` in `data`, not in the shared manifest.
## Internal/public separation
Internal execution plans MAY carry selectors and protected digests required to
rebuild a mutation. They are never serialized directly as public JSON. A
public preview uses opaque operation references, stable repo-relative or
root-qualified aliases, and no hard/purge topic, removed body, or
selector-dependent fingerprint. The private transaction journal retains only
the protected metadata needed for stale-plan and recovery checks.
## Canonical ErasureScope
Forget, `forget --id`, hard/purge, local reset, and recovery all expose the
same versioned child object at `data.erasure_scope`:
```json
{
"erasure_scope_schema_version": 1,
"operation_phase": "preview",
"active_memory": "pending-removal",
"managed_archive": "not-targeted",
"local_overlay": "not-applicable",
"git_worktree_modified": "on-apply",
"git_history_modified": false,
"distributed_copies_revoked": false,
"history_check_status": "not-requested",
"topic_retained_in_new_records": true
}
```
`operation_phase` is `preview`, `applied`, `no-op`, `recovered-complete`, or
`recovered-rollback`. `active_memory`, `managed_archive`, and `local_overlay`
use `not-targeted`, `no-match`, `pending-removal`, `removed`, `restored`, or
`not-applicable`. `git_worktree_modified` uses `no`, `on-apply`, or `yes`.
`history_check_status` uses `not-requested`, `unavailable`,
`reachable-copy-detected`, or `no-reachable-copy-detected`.
`no-match` means the selector found no managed unit. `pending-removal` means
matching content remains and this operation did not remove it; during
`recovered-rollback`, it can mean every target was still at its journaled base
content before recovery. It does not mean a transaction remains open or that
deletion is queued. Start a new forget preview and apply if removal is still
intended. `restored` means rollback actually returned content from a different
transaction output to its base content. `git_worktree_modified` reports shared
managed-file changes made by the current command: recovery that only cleans
committed transaction state and local reset both report `no`.
`git_history_modified` and `distributed_copies_revoked` are false for normal
0.12 operations. `unavailable` is WARNING/REVIEW, not PASS. A bounded
`no-reachable-copy-detected` result is not evidence that dangling objects,
other refs, remotes, clones, forks, backups, caches, or exports do not exist.
The canonical boundary is:
> Forgetting controls what remains available to future agents through MemoryCustodian. It is not a guarantee of erasure from Git history or previously distributed copies.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |