agentleFS
stevehansenstevehansen/eidet/.claude/skills/memory/SKILL.md

memory

Skill4 starsChanged 54 days agoMITView on GitHub

Prime on Eidet's Memory core before touching it — the MemoryEntry aggregate, its deterministic id (which doubles as a content commitment), validity intervals, supersession chains, forget/redact/edit verbs, and the Valence and FunctionalStage dimensions. Use when the task touches MemoryEntry, memory ids, MemoryType, Valence, Validity, provenance fields, supersession, version chains, forget, redact, links, or echo/fizzle feedback. Not for the gates that accept or reject a write (see writepath), not for ranking or context packing (see recall), not for scheduled rewrites (see maintenance).

110 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ecosystem-reference, fractal-delegation and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • naman10parikhSkill

    ecosystem-reference

    Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.

    Also in 5 projects that use this

  • naman10parikhSkill

    fractal-delegation

    Also in 5 projects that use this

  • roronoazoroshao369Skill

    memory-compression

    Also in 5 projects that use this

  • Maliot100XSkill

    send-user-message

    Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.

    Also in 4 projects that use this

  • jh941213Skill

    docs-ci

    문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.

    Also in 3 projects that use this

  • jh941213Skill

    docs-interfaces

    API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.

    Also in 3 projects that use this

  • +5 more from naman10parikh
  • +1 more from jh941213

The file

Files
SKILL.md

Memory core — priming

Canonical spec: docs/domains/memory.md — read it for the full entity shape, all invariants, key files, and gotchas. Terms of record: UBIQUITOUS_LANGUAGE.md § Memory core / Lifecycle. Design rationale: docs/specs/CoreSpec.md.

A Memory is a typed, repo-namespaced, append-only document with a deterministic id and a validity interval. This domain owns its shape and its lifecycle verbs. Whether a write is allowed belongs to writepath; how a memory comes back belongs to recall.

Core invariants (get these right)

  • The id is a frozen persisted format and doubles as the content commitment. Never hand-roll one, never regex its shape — ask MemoryIdGenerator.Matches. Changing a preimage silently de-boosts the entire corpus at recall instead of failing a build.
  • A git worktree is not its own repo. RepoPathResolver.Resolve maps a working directory to the repository it belongs to (a worktree's .git pointer file names the main checkout), and it runs where a path first becomes a repo — the CLI's and MCP's working directory, or the MCP client's first file:// root, which overrides the stdio launch cwd unless --repo/--workdir is given (#94) — but never from a shared-process client (local-agent-mode-*, whose unpinned tool calls are refused outright), and never after the root has moved mid-session: that means one process is answering for several sessions. Never put filesystem access in RepoIdNormalizer: that is a pure string map called on already-normalized ids at ~40 sites. Never resolve a scan root — intake reads the files in front of it and stores them under the resolved repo. Memories banked before this are moved with eidet repo rehome.
  • Every mutation goes through MemoryService's RunWriteAsync/RunMutationAsync. The storage write API is unreachable outside that file, and the cache generation bump lives in its finally. A bypassing write path serves stale recalls silently.
  • Content is never edited in place — a content change supersedes (new doc, IsLatest=false and a closed validity on the incumbent). Metadata-only edits update in place. RedactAsync is the sole content rewrite, and it keeps the id deliberately.
  • No hard delete. Forget closes the validity interval, records a reason, and writes a system audit Observation.
  • Provenance defaults to Unknown, not to a trusted origin — set it explicitly on any new write path.
  • Summary == null = awaiting enrichment; Summary == "" = redacted. Both are queried on; don't collapse them.
  • Valence.Neutral and FunctionalStage.None are 0 for free backfill, and None also means "applies to any stage" (recall's hard filter depends on it). Sign arithmetic lives only in ValencePolarity.

Key files / reuse

  • src/Eidet.Core/Domain/MemoryEntry.cs — the root; its field comments name each field's owner.
  • src/Eidet.Core/Domain/MemoryIdGenerator.cs — both id conventions and Matches.
  • src/Eidet.Core/Services/MemoryService.cs — every lifecycle verb + the mutation/cache gate.
  • src/Eidet.Core/Services/MemoryServiceOptions.cs — StoreOptions / EditOptions.
  • src/Eidet.Core/Memory/ValencePolarity.cs — the only home for stance signs.

Gotchas

  • EditAsync returns NotFound for a gate rejection too (legacy conflation) — the caller cannot tell the two apart.
  • A redaction tombstone deliberately fails its own id check and reads as Amended; scrubbing content without MemoryCommitment.Render reads as tampering.
  • src/Eidet.Core/Services/VersionHistory.cs is the installed-app-version log, not the memory version chain (MemoryService.GetVersionChainAsync).
  • Supersessions bypass the poison fast-path and conflict gate on purpose.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.