amadan
Instance space for attached domains: widen manifest Domain to claimed hostnames Feature Request open
Migrated from github.com/carlosframework/platform issue #174, opened 2026-08-12. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".
Still outstanding: Instance space is still one domain; instances create -host should accept any hostname the account has attached.
---
#82 shipped route-only by ruling (spec 2026-08-12-domain-attach-design.md §2): an attached custom domain serves the app, but carlos instances create -host tenant.example.com is still refused — provision.ValidHost pins instance space to <sqid>.<apps-domain>. This issue is the named follow-up: widen the manifest's Domain to "any domain this account has attached" (the claim record is the evidence), widen ValidHost's check to that set, and decide the sibling-apex guard's shape for claimed domains. lazyatom's echo.example.com case on #82 is the motivating scenario.
🤖 Generated with Claude Code