amadan
docs: fix a section reference
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+1
−1
docs/superpowers/specs/2026-09-24-instance-moves-for-every-app-design.md+1 −1
diff --git a/docs/superpowers/specs/2026-09-24-instance-moves-for-every-app-design.md b/docs/superpowers/specs/2026-09-24-instance-moves-for-every-app-design.md| index 86cab28e3..589b1233b 100644 |
| --- a/docs/superpowers/specs/2026-09-24-instance-moves-for-every-app-design.md |
| +++ b/docs/superpowers/specs/2026-09-24-instance-moves-for-every-app-design.md |
| @@ -121,7 +121,7 @@ stated as the proposal; §14 lists the ones still genuinely open. |
| - Moving addr-backed or unit-backed routes as such. An addr-backed instance |
| first becomes a platform instance (§9); then it moves like any other. |
| - `replica_regions` and the replica role (#330, discussion #162): a move |
| - moves the serving home. What happens to replicas is §13. |
| + moves the serving home. What happens to replicas is §14. |
| - Automatic scheduling ("move at 03:00"). The door takes a request now; the |
| app schedules if it wants to. Tito already does. |
| - Region-aware billing and unit economics. |