T724 tracked recurring intermittent 503s across COMMS/memory-pipeline/inbox APIs, reported independently by Finance(K147)/Server(K143)/Master. This session's earlier work (K215/K216, same day) traced the actual cause via curl -v: TLS cert on the connection is issued by Anthropic's own egress gateway, not yttcom.net's real cert - the failures are proxy-side congestion, confirmed via two burst tests (23%% success then 100%% success 5 min later, zero platform changes) and independently corroborated by USR369's own browser loading the same URLs cleanly during a failing window. Documented platform-wide in RULES-REG.md's new EGRESS RETRY DISCIPLINE section. T724 does not need a platform-side fix - closing as root-caused/understood rather than leaving it as an open unsolved bug.