Skip to content

Commit 899d121

Browse files
committed
docs(migrate): add the migrate glossary and the forced-pass obligation ADR
The review of #1193 kept reopening the same question: whether a forced backfill pass may resume without force. The rule was being worked out per run and per command. This records the vocabulary agreed for the follow-up design in #1217 (column migration, direction, twin, backfill pass, run, obligation, waiver, abort) and the decision that a forced pass is an obligation on the column migration, enforced by @cipherstash/migrate for every caller, CLI or embedded worker. Refs #1217
1 parent d168a94 commit 899d121

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

‎CONTEXT-MAP.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,8 @@
77
- [Stack Encrypt](./packages/stack-encrypt/CONTEXT.md) — encrypts values under
88
per-value ZeroKMS data keys and derives searchable terms from them, for Rust
99
and, through a WASI guest, Go.
10+
- [Migration Harness](./e2e/migration-harness/CONTEXT.md) — tests the
11+
Protect.js upgrade guide by having agents follow it and judging the result.
1012
- [Migrate](./languages/typescript/packages/migrate/CONTEXT.md) — moves an
1113
existing column between plaintext and encrypted form, resumably, for the
1214
Stack CLI and customer workers.

0 commit comments

Comments
 (0)