[waleedlatif1]

Summary

Mothership's private memory (the memory sidecar, live only in hosted dev) is now erased when its owner is offboarded (Mothership D106, simstudioai/mothership#878). Account deletion already queues the worker's memory cleanup. This PR also queues it, in the same transaction as the change it follows, when:

• a member is removed from an organization (removeUserFromOrganization): target organization_member
• an external collaborator is removed from an organization's workspaces (removeExternalUserFromOrganizationWorkspaces): target organization_member, since their workspace chats used that organization's memory
• a member is moved to another organization: organization_member for the source organization
• an organization is deleted (enqueueOrganizationResourceCleanup, called by the admin delete): target organization

lib/mothership/generated/memory-notes-access.ts is regenerated from the worker contract (bun run contracts:sync).

Companion: simstudioai/mothership#878

Product update (if relevant)

None visible. Private memory is limited to effective super-users with the benchmark deployment opt-in, and only hosted dev runs the memory sidecar. On staging and production the worker answers these cleanup events without erasing anything.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation
• Other: ___________

Testing

• lib/mothership/memories/offboarding.integration.ts runs against real Postgres (bun run test:integration lib/mothership/memories/offboarding.integration.ts, passing locally). A removal whose actor lacks authority rolls back and queues nothing. A committed member removal and an external-collaborator removal each queue organization_member for that user. enqueueOrganizationResourceCleanup in a rolled-back transaction queues nothing, and in a committed one queues organization.
• It fails with membership.ts and resource-cleanup.ts reverted to staging (expected 2 queued erasures, received none).
• Ordering: merge after the worker side is deployed to the environment this Sim talks to. An older worker answers 400 to the new targets, so the outbox retries and eventually dead-letters them; nothing is lost that the worker holds today.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Oct 31, 2026 7:11am UTC

[github-actions]

⚠️ Cross-repo companion check

One or more companion PRs aren't merged into staging yet. Merging this without them will leave copilot and sim out of sync — merge them in lockstep.

• ❌ simstudioai/mothership#878 — OPEN, not merged (targets staging) — feat(worker): erase private memory when its owner is offboarded

[cubic-dev-ai]

No issues found across 5 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge after the companion worker changes are deployed, as noted in the PR description.

Summary

Queues private memory cleanup in the same transaction as member removal, external collaborator removal, organization transfer, or organization deletion.

• Leaving an organization now queues erasure of that person's private memory.
• Deleting an organization now queues erasure of its private memory.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Member leaves or organization is deleted] --> B[Database transaction]
  B --> C[Change organization access or resources]
  C --> D[Queue memory cleanup]
  D --> E{Transaction commits?}
  E -->|Yes| F[Outbox delivers cleanup to worker]
  E -->|No| G[Discard changes and cleanup event]

Loading

_{Reviews (4) · Last reviewed commit: "test(mothership): cover a successful ext..." · Reviewed by Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@greptile

[waleedlatif1]

@greptile