amadan
docs: rails-poc spec §7 — link the filed platform issues (#152, #153)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 file changed,
+5
−4
docs/superpowers/specs/2026-08-11-rails-behind-carlos-edge-poc-design.md+5 −4
diff --git a/docs/superpowers/specs/2026-08-11-rails-behind-carlos-edge-poc-design.md b/docs/superpowers/specs/2026-08-11-rails-behind-carlos-edge-poc-design.md| index 7408f692c..04eacc6e6 100644 |
| --- a/docs/superpowers/specs/2026-08-11-rails-behind-carlos-edge-poc-design.md |
| +++ b/docs/superpowers/specs/2026-08-11-rails-behind-carlos-edge-poc-design.md |
| @@ -221,10 +221,11 @@ the migration evaluation: |
| - **CARLOS concerns** (roadmap candidates, priced by whether |
| Rails-on-CARLOS graduates from migration tactic to product): |
| multi-upstream health-checked `addr` routes at the edge — the |
| - platform-native replacement for the NLB rung; and the edge's own HA |
| - posture (standby/EIP failover), which is a whole-deployment question |
| - every CARLOS tenant shares — the Rails apps widen the blast radius of |
| - a risk `go.tito.io` already carries, they don't create it. |
| + platform-native replacement for the NLB rung (filed as platform |
| + #152); and the edge's own HA posture (standby/EIP failover), which |
| + is a whole-deployment question every CARLOS tenant shares — the |
| + Rails apps widen the blast radius of a risk `go.tito.io` already |
| + carries, they don't create it (filed as platform #153). |
| - Data HA is out of scope by construction: Postgres/MySQL/Valkey/ |
| Memcached stay in RDS/Elasticache with their own multi-AZ story — |
| the apps' state was never on k8s, so the migration never touches the |