amadan
steering: the door accepts a host outside the apps domain that the converger will never steer Issue open
Migrated from github.com/carlosframework/platform issue #306, opened 2026-08-26. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".
Still outstanding: The steering door accepts a host outside the apps domain that the converger will never steer.
---
Seen on tito 2026-08-26: carlos steering -app titogo -host bill.go.tito.io latency succeeded ("steering set to latency"), the record and registry row converged to latency, and then the converger declined every tick:
> steering: route bill.go.tito.io excluded: host is not under the apps domain "platform.tito.io" — custom domains steer via CNAME to edge.<apps-domain>; a direct Route53 record only ever lives in the steering zone itself
The converger is right (writing that name into the steering zone would wedge the batch). But the door already knows the apps domain, so it should refuse the request up front with the same guidance — "this host isn't under platform.tito.io; point it at edge.platform.tito.io with a CNAME instead" — rather than accept a flag that can only ever produce an exclusion line per tick. Same shape as the wildcard-label refusals elsewhere: fail at the door, not in the loop. The CLI's "the fleet only ACTS on this once a deployment arms its converger" hint then stays honest.
Relatedly for #299: static wildcard domains (CARLOS_WILDCARD_DOMAINS, tito's go.tito.io) steer as a whole by replacing their *.domain A with *.domain CNAME edge.<apps-domain> — worth stating in the steering docs as the operator move.