agent-memory-protocol

Named Memory Protocol

How a named workflow works the gutt knowledge graph as itself: register a memory identity, recall its own scope before the group's, and tag every org write it makes so the next run can find it. This layers workflow identity on top of memory-search (how to read) and memory-capture (how to write). The identity convention — naming, registration, tagging, recall order, guard rails — lives in one normative place: references/agent-identity.md. This file is the operative digest; on any conflict, the reference wins.

Use this for a named memory-writing workflow: either an agent or a skill whose contract declares a stable identity. For a skill, declare the base identity in frontmatter as metadata.memory-identity and repeat the operative rules under an exact ## Memory identity heading. Writing from the main session with no named workflow identity is just memory-capture — no registration and no tagging.

Finding the scope bound to this directory (do this before step 1)

The registered name carries a --<scope> suffix, and the first place to look for its value is the binding a person set with /gutt-pro:agent-scope. You cannot run that command to ask — it only takes effect when a human types it — so read the stored value directly:

• <DATA_DIR> — ${CLAUDE_PLUGIN_DATA}, interpolated into this sentence for you. Do not pass $CLAUDE_PLUGIN_DATA through to a shell and do not export it: only hooks are given it, so it expands to nothing in a command you run.
• Read <DATA_DIR>/config.json and look under projects. The key is the name Claude Code gives this project's transcript directory, which you can derive from your working directory: resolve its symlinks, then replace every path separator, drive-letter colon, . and _ with a single - — each character becomes its own dash, so two adjacent ones yield -- (this is not the run-collapsing rule scope values are normalised with). So /Users/me/my_app is -Users-me-my-app, /Users/me/.config/app is -Users-me--config-app, and on Windows C:\dev\my.app is C--dev-my-app. Take projects.<that key>.agentScope.value.
  • Resolve the symlinks first (pwd -P): on macOS /tmp and /var are links into /private, and the unresolved spelling gives a key that never matches.
  • Match the key exactly. If nothing matches, treat it as unbound and fall through — never pick the closest-looking entry, because a wrong match binds this directory to another one's identity, permanently.