carlos / platform Public

A replicated-unit route class: served by the local unit on every box, never backhauled Feature Request open

Migrated from github.com/carlosframework/platform issue #332, opened 2026-08-28. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".

Still outstanding: A replicated-unit route class, served by the local unit on every box and never backhauled.

---

Fourth ask from titogo's residence design (titogo docs/superpowers/specs/2026-08-27-multi-region-residence-design.md §3, §8.4). Companion to #329.

Today's serving classes (ingress spec Part 3) are everywhere (static/bake), everywhere-probed (addr), and home-boxed (unit/socket — backhauled). Titogo's root domain (go.tito.io) needs a fourth: a route whose unit runs on EVERY box of the deployment, each edge serving it from its own local socket, never backhauling — so a steered go.tito.io terminates AND serves at the nearest edge (titogo runs a router per region; identity reads come from an S3-CAS store, so any box's router can serve any request).

This is also the shape the ingress spec's read-local anticipation already commits to needing (the replica role note in Part 3): a replicated route claims no single home in the edges-file fold, so the home-map ruling for it needs stating (today's static-route "home" over-claim is the nearest precedent).

🤖 Generated with Claude Code