Repository navigation
docs(openspec): Use the existing Owner column and migrate only proven legacy data - #2489
Merged
Merged
Conversation
… legacy data Co-Authored-By: David Cramer <david@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
2 screenshot changes — 2 changed · 0 added · 0 removed Review screenshots in Frameshift
|
dcramer
approved these changes
Oct 31, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #2439
Updates the Actor identity plan (
openspec/changes/actor-identity-end-state/) to the reevaluated plan that David answered in the #2439 Slack thread.David's answers, quoted in
proposal.md:junior_conversations.actor_identity_idstays as the Owner column. Code and docs call it the Owner.Plan decisions:
design.md, Legacy Data, lists the shapes that need it and the ones that do not (junior/<email>Identities, Redis and Turn checkpoints).New step order: 1 (#2443, done), 2 (#2473 done, finish #2482), 3 labels,
systemfor new system Conversations, child Owner, and root Owner readers, 4 real Identities and trust (needs #2260), 5 dry run and David's OK, 6 one data migration, 7 Owner repair, 8 delete fallbacks and stored Actors after the Redis window, 9 drop columns and delete the plan. Steps 1 and 2 keep their numbers, so the references in #2482 stay correct.All other decided rules stay the same.
TERMINOLOGY.mddoes not change.via David Cramer.
--
View Session [Sentry]