Memory protocol
Skill IrfanSadiqRahat/constellation/methodology/memory-protocol
Persistent role-scoped memory across sessions. The agent that worked on your codebase yesterday knows things today.From its SKILL.md
npx -y skills add IrfanSadiqRahat/constellation --skill memory-protocolAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, 399 tokens by cl100k_base, as published. Nobody here has run it
memory-protocol
The problem
Stateless agents re-learn your codebase, your conventions, your past decisions every session. That's tax. Constellation's memory protocol lets each role accumulate role-scoped notes that survive sessions.
Storage layout
.constellation/memory/
<project_id>/
<role_id>/
decisions.md # ADR-style, append-only
conventions.md # codebase-specific patterns
gotchas.md # surprises learned the hard way
cache.json # structured fact cache (TTL'd)
Read rules
At session start, for role R:
- Load
.constellation/memory/<project>/<role>/*into the briefing - Cap to N lines per file (default 200) — older content stays on disk
- Decisions and conventions are authoritative — never silently overwrite
Write rules
End of session OR on confirmed decision:
- Append, don't rewrite. Decisions get superseded entries, not edits.
- Sign each entry with timestamp + run-id
- Compact opportunistically — merge near-duplicates with a
compactoragent
Cross-role boundaries
- Role memory is private to that role by default
- Shared memory under
<project>/shared/for cross-role facts (e.g. tech stack, key URLs) - Privacy: PII never written to memory; redact on write
Forbidden
- Hallucinated memory — only write what was observed or decided in this session
- Memory as gossip — facts about teammates / users
- Memory as PII store — actively redacted
Why this matters
Constellation's value compounds across sessions. After a month, the backend-architect "knows" your repo. After a year, the security-architect remembers every threat-model decision and its outcomes. Constellation gets more useful the longer you use it.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.