Decide whether a completed Matryca change belongs in CHANGELOG.md and add one concise Unreleased entry when required. Use before concluding runtime, security, architecture, integration, performance, operator, or public-contract changes.
Apply Matryca maintainer standards for GitHub issues, pull requests, branches, reviews, merges, milestones, tags, releases, and remote comments. Use before any GitHub-facing action or artifact.
ZettelForge v2.0.0 — Production CTI agentic memory system. Hybrid TypeDB (STIX 2.1 ontology) + LanceDB (vector search). Zero external AI dependencies: fastembed for embeddings, llama-cpp-python for LLM. 75% accuracy on CTI queries, 18% on LOCOMO. Use when agents need persistent memory, threat intel retrieval, entity…
Set up and use the Noosphere memory provider in Hermes Agent. Use when a user gives Hermes a Noosphere API key, asks to connect Hermes to Noosphere, configure durable memory, verify the provider, or troubleshoot Hermes Noosphere memory setup.
Review and optimize the MeMesh memory database. Analyzes health score, finds stale/conflicting/redundant memories, shows work patterns, and suggests cleanup actions. Use when asked to "review memories", "check memory health", "clean up knowledge", or "what's in my memory".
Use MeMesh to remember, recall, and manage AI knowledge across sessions, and to exchange durable task-focused messages with local agents. Triggers when the user asks to remember something, recall past decisions, forget outdated info, learn from mistakes, analyze work patterns, contact another agent, or handle a…
Render evaluation run reports and interpret gate metrics. Use for: reading eval JSONL logs as a markdown report (uv run python -m eval.seedreader --run-id ID), listing available run-ids, scoring the GO/STOP/ITERATE gate decision, understanding what each metric means, diagnosing why an arm won or lost, reviewing probe…
Send, poll, wait for, and acknowledge durable addressed agent-to-agent messages in Aionforge Memory (messagesend, messagepoll, messagewait, messageack) and subscribe to room resources. Use to hand a brief to another agent, page a teammate, wait for a reply, coordinate a multi-agent workflow, or drain an inbox …
One-time setup that lays a foundational Aionforge Memory substrate for a fresh project — resolve identity, seed conventions and architecture decisions as captures, stand up a work-item backlog skeleton, and verify recall. Use when a project's memory is empty or new, or when the user asks to set up, bootstrap…
Capture durable Aionforge Memory records for decisions, user preferences, project facts, release outcomes, validation results, handoffs, corrections, and reusable failure patterns. Use proactively during substantial work and whenever the user asks to remember or update memory.
Build, query, test, and optimize a local agent memory CLI where durable memories are represented as retrieval unit tests. Use when the user asks Codex to create, maintain, inspect, or improve a memory-cli project; when a workspace already contains a memory-cli, .memory, or memories project; or when Codex must add…
Use when storing, recalling, or auditing memory inside enterprise B2B agents built on Anthropic's platform — agents that operate on tenant-scoped data (matters, cases, deals, accounts, workspaces, projects) where citation, provenance, and tenant isolation matter. Trigger on: "remember this for this…