Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Replacement migrations must close legacy creation paths
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
When a workflow is replaced, keep pinned historical records resolvable while removing, archiving, or explicitly gating the superseded option on every new-creation surface. Referential stability for old records does not require continued discoverability for new records. This applies when records pin immutable configuration identifiers. If historical records resolve configuration dynamically, first define a separate compatibility and migration strategy. Validate both halves: intended new inputs reach the replacement, and new work cannot enter the legacy path except through an intentional compatibility override.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review