Slightly more serious answer, for posterity:
For networking, Ames gets its public keys (and breach notifications) from Jael, which in turn gets them from the Azimuth userspace agent (in /app/azimuth). Jael's code has that (%azimuth) hardcoded into it, but could be made to talk to a different agent pretty easily, as long as it communicates key change & sponsorship events in the same way.
> remove it without creating problems with the rest of urbit
If by "urbit" you mean the rest of arvo, I don't _think_ too much on the setup above using /app/azimuth, so you should be able to replace it pretty easily.
If by "urbit" you mean the rest of the network, well: to talk to other urbits over ames, you're going to need the public keys they published through the Azimuth contract, and they expect your public keys to be published there too (comets and moons being exceptions to this).
--
~palfun-foslup
https://tlon.io