amadan
multi-region: backhauled egress — ruling record (containment + attribution; pricing open) Idea open
Migrated from github.com/carlosframework/platform issue #284, opened 2026-08-24. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".
Still outstanding: Decision record awaiting Paul's pricing call on backhauled egress: bill hopbytesout or keep absorbing it.
---
The T7 egress ruling (backhaul plan item 5) landed 2026-08-24 in PR #283: sender-side per-home-box in-flight cap (CARLOSBACKHAULMAXINFLIGHT, default 64; 503 + Retry-After: 2 at the cap; throttled backhaul-saturated <box> log) + home-box hop annotation (usage.EdgeRow `hoprequests/hopbytesout as SUBSET counters inside the existing totals; backhaul_gb` meter name reserved, wired into nothing). Bills unchanged by construction.
OPEN HALF — Paul's pricing call: price hop_bytes_out (a rate-card line or an egress multiplier) or absorb it as a platform cost of any-edge serving. Safe default shipped: absorbed. The counters accumulate either way, so the decision can be made on real data after stage 5.
Secondary flag in the same lane: whether unsolicited/scanner traffic should ever be carved out of tenant-billed bytes (pre-existing posture, unchanged by the ruling).