Skip to main content

​
What Are Memories?

A memory is a short, durable note about how your organization works. Memories might encode, for example, which team owns which service, how a particular person likes their reports written, a decision made by your team lead and the rationale behind it, or a configuration step that often gets skipped and leads to bug reports. PlayerZero automatically creates, organizes, and updates memories as work happens throughout your enterprise.

​
Why They Matter

Without memories, new channels often require specific prompting to use a skill or knowledge base artifact that encodes your work preferences. With memories, PlayerZero brings in that relevant information without you needing to say anything. You can spend more time on problem solving and less time on setup.

​
What Gets Remembered

Memories are created about organization-wide ways of working. They may include personal preferences, such as how you want a summary formatted or how much detail you want in a work report. They may also include best practices, such as the order in which the Support team checks different information sources when triaging a new issue. They may also include memories about specific areas of responsibility, such as who reviews a particular area of the codebase, or who can authorize a security-layer change. Finally, memories can be created about related work, such as the number of times a particular issue has been raised in the last few days.

​
Finding Earlier Work

Memories also make earlier work findable when you cannot remember what it was called. Ask for the thread where someone was working on data migrations a few weeks ago, and PlayerZero can find it from what the work was about rather than from a title you would have to guess.

​
Correcting a Memory

PlayerZero will check with you on memory correctness. If something it remembered is wrong or out of date, it will update its record. That said, memories never outrank specific prompts. What you say in the conversation will win out over what was remembered if there is a conflict.

​
Memories and Knowledge Bases

Memories and knowledge bases are two halves of a whole. A memory is a preference that carries over into future work. A knowledge base document is longer material about processes or references, such as an incident runbook, a product specification, or a walkthrough of how a system fits together. A memory may point at a knowledge base document in a similar way to how a skill’s prompt works together with the skill’s artifacts, though memories and knowledge bases are dynamically refined based on production behavior, while skills remain static until a deliberate update choice is made.

​
Get Started

👉 Knowledge Bases 👉 AI Player overview