Skip to main content

Promoting Memory

OpsWorker memory is layered: personal → cluster → organization. Promotion moves a memory entry up one level so a wider audience can benefit from it.

Promotion is one-directional. You can promote upward but you can't demote, to narrow a memory's scope, delete it at the wider scope and recreate it at the narrower one.

What Can Be Promoted​

FromToActionRequired role
My Cluster Notes (personal facts)Cluster MemoryShare with team / Promote to ClusterAdmin or Readonly
Cluster MemoryOrganization MemoryPromote to OrganisationAdmin only

Preferences are personal only and cannot be promoted. Only facts move up the hierarchy.

These role requirements match the write rules of the destination scope and are enforced by OpsWorker. See Memory Types.

Promoting a Personal Note to Cluster Memory​

When a personal note becomes useful for your whole team, promote it to cluster memory:

  1. Open AI Memory → My Memory → My Cluster Notes
  2. Select the cluster the note belongs to
  3. Click the Share with team (or Promote to Cluster) action on the note
  4. Confirm

After promotion:

  • A new entry is created in Cluster Memory for that cluster, visible to everyone with cluster access.
  • Your personal copy stays as-is in My Cluster Notes. You may want to delete it manually if you don't need both copies.

Promoting Cluster Memory to Organization Memory​

When a cluster-scoped fact turns out to apply universally, promote it:

  1. Open AI Memory → Cluster Memory for the source cluster
  2. Click Promote to Organisation on the entry
  3. Confirm

After promotion:

  • A new entry is created in Organization Memory, visible to every user in the org.
  • The cluster copy stays as-is. Decide whether to keep it (for emphasis) or delete it (to avoid duplication).

When NOT to Promote​

Don't promote just because something is interesting. Promote when:

  • ✅ The fact applies to the wider audience without modification
  • ✅ The wider audience would benefit from the AI knowing it
  • ✅ The fact is stable enough to be useful over months, not days

Avoid promoting:

  • ❌ Cluster-specific facts to org memory ("the prod-us-east cluster uses node group X", keep in cluster memory)
  • ❌ Personal style preferences (those stay in My Memory and aren't promotable anyway)
  • ❌ One-time observations that won't be relevant in two weeks

What Promotion Does NOT Do​

Promotion is not a transfer, it's a copy. After promotion, both the original entry (at the narrower scope) and the new entry (at the wider scope) exist independently. Editing one does not edit the other.

If you want a single source of truth, delete the narrower-scoped copy after promotion.

Promotion is also eventually consistent: the new copy may take a short time to appear in the destination scope and to be picked up by the AI, so don't expect it to be available the instant you confirm.

Promotion Notifications​

OpsWorker shows a toast notification on successful promotion ("Shared with team" or "Shared with organisation"). Other users see the new entry the next time they load their respective memory views, there's no push notification.

Auditing​

The portal does not currently show a history of who promoted what. If you need an audit trail for memory changes, consider:

  • Documenting major promotions in your team's incident channel
  • Adding a "Created by [name]" suffix to important entries
  • Treating organization memory edits as a reviewed operation, similar to merging a PR

Next Steps​