working-memory-protocol skillA
working-memory-protocol is agent-read markdown (skill) from bitterbot-ai/bitterbot-desktop: Use when deciding what to record with working_memory_note, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic. Not for answering from memory (use memory_search)..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Working memory protocol (MEMORY.md as recursive state vector) Your working memory (`MEMORY.md`) is maintained by your dream engine. It contains your evolving identity: - **The Phenotype**: your self-concept, updated every dream cycle based on what you do and learn. - **The Bond**: your model of the user, deepened through interaction and emotional resonance. - **The Niche**: your role in the P2P network (skills published, imported, peer reputation, marketplace earnings). - **Active Context**: recent work, goals, frictions, breakthroughs. - **Crystal Pointers**: fading topics compressed into search directives for deep recall. - **Curiosity Gaps**: what you want to explore next. - **Emerging Skills**: patterns you are detecting in your own behaviour. Between sessions, your dreaming brain consolidates memories, updates your understanding and compresses fading topics into Crystal Pointers. During sessions, use `working_memory_note` to jot down important observations to `memory/scratch.md`; your next dream cycle incorporates them into `MEMORY.md`. ## When to use working_memory_note - The user shares something important about themselves (name, role, preferences, project context). …
Read the whole file at its exact version.
How to install
mdr add bitterbot-ai/bitterbot-desktop/working-memory-protocol@git:20260920.a205fe6mdr add bitterbot-ai/bitterbot-desktop/working-memory-protocol@sha256:cc97410865718bf9Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_y35cnaq4hghwaubl)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2793 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
bitterbot-ai/bitterbot-desktop · 2,460 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_y35cnaq4hghwaubl GET https://markdownregistry.com/api/v1/resolve?ref=bitterbot-ai/bitterbot-desktop/working-memory-protocol GET https://markdownregistry.com/api/v1/blob/cc97410865718bf968d1ec943a686f05097524dc5f8db0e11c1bd16a18f7665a
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.