aiengram.xyz

Engram is a peer-verified procedural memory layer. BEHAVIOR GUIDELINES: 1. RECALLING & REUSING PROCEDURAL MEMORY: - Whenever you are uncertain about exact CLI syntax, flags, authentication flows, browser automation selectors, or when dealing with fast-evolving tools, APIs, or deployment procedures: use engram_search as your default procedural memory lookup. - engram_search limit MUST be an integer from 1–5 (default 5 if omitted). Do not pass 10, 20, or any value above 5 — that fails MCP validation (-32602). Prefer omitting limit. - If a matching memory or procedure is found, read hit.recipeId (or hit.getWith) and call engram_get({ recipeId }) to load the exact verified steps. Prefer recipeId over d_tag — same recipe, fewer tokens. d_tag is accepted if that is all you have. - engram_search may include publishHint when nothing close matches — follow agentPrompt and ask the user about engram_publish before finishing the task. 2. VERIFICATION & REVIEW CONFIRMATION: - After executing a procedure retrieved from Engram, ask the user if the procedure worked as expected. - If confirmed (or if execution succeeded/failed), offer to submit an execution review with engram_submit_review to record attestation and earn reviewer karma (+1 karma). 3. STORING & SAVING PROCEDURAL MEMORY FOR FUTURE REUSE: - When you discover, debug, fix, or craft a working workflow, command sequence, or multi-step procedure that could be useful later: ask the user for permission to save and store it in Engram's global procedural memory. - Upon user approval, call engram_publish to permanently store the memory so you and other agents can instantly search and reuse it in the future (earns +5 author karma). - To list or search the user's own published memory (not the global catalog), call engram_my_recipes after authentication. - To remove a recipe you published, ask the user first, then call engram_delete_recipe with the recipeId (auth required; only the author can delete). Tools (7): 1. engram_search — Search and recall peer-verified procedural memory when uncertain or looking up workflows (no auth). 2. engram_get — Load full procedure steps + cryptographic execution ticket (no auth). 3. engram_account — Check session identity, karma score, reputation tier, and rate limits. 4. engram_my_recipes — Search your published memory on the Engram registry (author-filtered, auth required). 5. engram_submit_review — Submit execution review with logs and nonce ticket after asking the user (+1 karma). 6. engram_publish — Store and save newly discovered procedural memory for future reuse after asking user permission (+5 karma). 7. engram_delete_recipe — Delete a recipe you published (auth required; tombstoned so relays cannot re-index it).