Memory Pages

Memory pages are persistent context for Dawn. Workspace memory stores shared team knowledge; personal memory stores private user-owned preferences and context that can travel with the user.

Workspace Memory vs Personal Memory

Dawn has two memory scopes:

• Workspace memory stores shared team knowledge such as runbooks, architecture notes, escalation rules, and project conventions.
• Personal memory stores user-owned context such as preferences, personal conventions, recurring projects, decisions, and notes.

Use workspace memory when the page should help the whole workspace. Use personal memory when the context belongs to one user and should not become shared team knowledge.

What belongs in memory

Workspace memory is best for:

• Stable processes (on-call rules, escalation paths, release checklists).
• Canonical references (service map, environment conventions, naming standards).
• Team agreements (triage policy, severity definitions).
• Well-tagged pages that map cleanly to the agents and workflows that should use them.

Personal memory is best for:

• personal response preferences;
• how you like reviews, plans, specs, and release notes structured;
• recurring projects or domains you work across;
• user-owned decisions and notes that should be useful later;
• context that should follow you without becoming workspace-wide guidance.

What to avoid

• Temporary discussion fragments better suited to conversation history.
• Sensitive credentials or secrets.
• Huge unstructured dumps that degrade retrieval quality.

Do not store passwords, API keys, tokens, or credentials in either memory scope.

Managing Personal Memory

Open account settings in Dawn Web and select My Memory to manage personal memory pages. Personal memory is organized as pages, with common roots for profile, preferences, conventions, projects, decisions, and notes.

You can also ask Dawn to remember personal context from a conversation:

Remember that I prefer PR review summaries to start with blockers, then risks, then test gaps.

Personal memory can be used by Dawn when it is acting on behalf of your signed-in identity. It should not be used to expose private notes to other people in a shared conversation unless you explicitly ask Dawn to share or explain them.

Maintenance workflow

1. Create short, purpose-specific pages.
2. Add tags so related pages are easier to manage and scope to agents.
3. Review revisions regularly and remove stale entries.
4. Use scheduled tasks for periodic memory updates (weekly summaries).
5. Track ownership so someone is accountable for each critical page.

Tags and agent access

Tags and agent memory access apply to workspace memory.

• Use tags to group pages by workflow, team, or domain.
• Agents can be configured for no memory access, all workspace memory, or tag-scoped access.
• Tag-scoped agents only read pages whose tags overlap with the agent’s allowed tags.
• Tag-scoped agents must keep at least one allowed tag on the pages they create or update.

Example: if a support agent is limited to support and billing, it will not use a page tagged only release or engineering.

Validation checklist

• Create or update a page with a distinctive rule or phrase, then ask the agent about that exact rule and confirm the answer reflects the page.
• Outdated memory revisions are superseded and documented.
• Pages are discoverable in the Memory UI by title, and topic-specific questions reach the intended page content.
• Tag-scoped agents can see only the pages that match their allowed tags.
• Personal memory appears under My Memory and remains separate from workspace memory pages.

List memory pages relevant to this workspace onboarding flow.

Identify stale memory pages that should be updated or archived.