io.github.billy12151/memory-arbiter-mcp

Daily memory operations: remember, find, batch_find, read, update, judge, status, help. Call memory(action="help") to discover accepted fields, judge requirements, value enums, update modes, and action_required paths before relying on a result that requests attention. update edits in place: <=3 local edits use patches=[{old_text,new_text}] (atomic all-or-nothing, one version bump); full rewrites use new_content; a single small edit may use old_text/new_text. batch_find runs up to 8 queries in one call and returns one merged index page (dedup by memory_id, matched_query_ids per item). find is an index page: results carry metadata + content_chars + a bounded outline (offsets usable directly as read span starts), not full content — content_mode (v0.15.10, preview default) is a single-choice enum: "hits" adds hit_spans (vector-matched unit text + span coordinates, never truncated; >=50% coverage upgrades an item to full text), "full" returns whole texts. Score compares only within the page; if the top page misses, reword the query or add tags_filter instead of deep paging. The size block meters the returned page (tokens_estimate + display_hint).

Read-only inspection: overview, doctor, conflicts, conflict_detail, history, expired, audit, entities, help. Use memory_review(view="help") for accepted fields. Inspect conflict_detail before judging a conflict so its members, value groups, revision, and apply state are visible.

Authorized governance: retire, merge near-duplicates, apply/replan/resolve conflicts, confirm, and manage workspaces. Every state-changing action requires explicit user authorization for that action, then authorized=true. Call memory_govern(action="help") for exact actions, accepted fields, impact notes, and confirmation semantics.

Maintenance: evidence rebuild, conflict scans (scheduled-task spec under help topic scheduled_tasks), full-library duplicate sweeps (scan_duplicates), history cleanup, entity assignment, pending activation, backup replay, notices, and semantic runtime control. Use memory_repair(task="help") for notice handling and semantic_control actions. Semantic notices are advisory; read both memories before dismiss or resolve, and never pass a notice directly to judge or resolve_conflict.