amadan
replica_regions: an additive record field carrying an instance's replica-region set Feature Request open
Migrated from github.com/carlosframework/platform issue #330, opened 2026-08-28. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".
Still outstanding: Add the additive replica_regions field carrying an instance's replica-region set.
---
Second ask from titogo's residence design (titogo docs/superpowers/specs/2026-08-27-multi-region-residence-design.md §1, §8.2). Companion to #329.
The residence shape is home region + replica-region list, a list from day one so multi-region replication later is "widen the list", never a migration. The ask: an additive, omitempty replica_regions field (JSON array of placement codes) on the route record and registry — wire-shape rule applies, every pre-change record parses unchanged. v1 always writes [<region>]; validation is subset-of-armed-regions. No behavior keys on it yet — it is the committed shape for the read-local/replica-role future the ingress spec already anticipates.
🤖 Generated with Claude Code