Filipe-Soares-de-Almeida

memai-checkpoints

The lifecycle of MemAI CHECKPOINTS: deciding which bearing is still current and which one is superseded, archiving the checkpoint of work that is closed or an intra-session trail that a newer one already covers, keeping the single bearing a live effort still needs, correcting a fact in a kept checkpoint that has gone out of date, pushing out its recheck date, and re-filing its domain path. Use when the user asks to TRIAGE or CLEAN UP checkpoints, "archive the old checkpoints", "retire this checkpoint", "what is still active", "which of these is the current one", and as the checkpoint step of the [[memai-maintenance]] pass. Conceptual base: [[memai-memory]] — a checkpoint is a bearing, not an archive.

memai-confidence

Verify a MemAI memory's claims against live facts and set its `confidence` (unverified | confirmed | contradicted). Checks the `anchors` a scan already extracted — file:line, symbol, table/column, domain, URL — against today's source, promotes or demotes each memory, stages a `reword` for a detail that drifted, and pushes `review_after` out with a `review` once a claim has actually been rechecked. Use when asked to "validate the memories", "set confidence", "check whether the facts still hold", "recheck what has gone stale", or when invoked as a step of the [[memai-maintenance]] pass. The store's own model is [[memai-memory]].

memai-distill

Distill and MOVE knowledge between MemAI types: pull what is durable out of one checkpoint (or several) into a note/reasoning/anti_pattern, change a memory's type (checkpoint→note when the content is timeless), and merge near-duplicates. Use when the user asks to "distill memory", "turn a checkpoint into a note", "move a memory to another type", "merge duplicate memories", or as a step of the [[memai-maintenance]] pass. Knows that `distill` ARCHIVES its sources — and when not to use it. Conceptual base: [[memai-memory]] (the checkpoint × note × reasoning boundary).

memai-link

Stitch the MemAI relations GRAPH: typed edges between memories (supersedes / relates_to / contradicts / links_to), turning [[wikilinks]] written in a body into real edges, connecting complementary memories that share a domain, and preserving lineage (checkpoint to note, archived to successor). Uses dedup_scan to find candidate pairs and get_relations before every edge, so a rerun creates nothing twice. Use when asked to "link memories", to "connect" or "relate" two memories, to "materialize the wikilinks", to "stitch the relations graph", or when invoked as the linking step of the [[memai-maintenance]] pass. Conceptual base: [[memai-memory]]. Siblings in the same pass: [[memai-checkpoints]], [[memai-distill]], [[memai-confidence]].

memai-maintenance

Orchestrator of the MemAI MAINTENANCE pass (long-term agent memory). Runs [[memai-checkpoints]], [[memai-distill]], [[memai-confidence]] and [[memai-link]] as one curation pass, owns what none of them covers — the DOMAIN TREE (nested paths, cross-listing, casing), the DIAGRAMS and the store's DECAY (`review_after`) — and consolidates everything into ONE `optimize_stage` run the human applies or rejects in the dashboard. Use when asked to "optimize / maintain / curate / clean up / review my MemAI memories", "run the memory maintenance pass", "validate and set confidence", "set confidence in bulk", "archive old checkpoints", "link memories up", "fix the domain tree", or for any broad sweep over the store. Conceptual base: [[memai-memory]].

memai-memory

How to use the MemAI MCP server (long-term agent memory: one ACID SQLite store, BM25 keyword search) — which tool family to call when: pulse/search/recall/list_by_domain/list_recent/ list_domains/get_memory/help to read; note, reasoning, anti_pattern, checkpoint, handoff, diagram to write; diagram_*/get_diagram for flows; edit_memory/link_memories/set_confidence/also_domain/forget/purge_memory to curate — plus the session/domain/tags convention, with domains as nested PATHS and cross-listing (also), and review_after/source_ref for a memory that will go stale. Use at the START of a session or when RESUMING work (warming a cold session), whenever SAVING or LOOKING UP durable knowledge (a fact, a decision, a rule, a pitfall), when DOCUMENTING a routine as a flow, and before PAUSING or ENDING work (checkpoint). Also on "MemAI", "memory", "long-term memory", "warm up the session", "checkpoint", "what did the last session leave", "save this lesson", "anti-pattern", "diagram of the flow".