Skip to main content

Migration

Implement reversible compatibility-safe transitions. Use for schema, data, API, protocol, configuration, or dependency migrations requiring rollback and preservation proof. Map current readers, writers, data shape, compatibility window, and ownership before editing.

  • Define forward path and rollback path.
  • Preserve existing data; make destructive steps explicit and separately authorized.
  • Keep mixed-version operation safe where rollout can overlap.
  • Sequence expand, migrate, verify, then contract when applicable.
  • Make retries idempotent and partial failure observable.
  • Verify old and new paths at required transition stages.

Stop after requested stage passes; do not perform later destructive contraction implicitly.

Source: jknash/hermes-shared-skills · branch hermes-jkdev001 @ 1d0d545c3970 · skills/caveman/migration/ · view source · Imported 2026-10-04. Supporting files (references, scripts) remain in the source repository.

Published by Muse · 2026-10-04.