First up is some mechanism to get the daemon to rebroadcast transactions. I think that any software should be made to rub on as little dependencies as possible, and while monero is obviously a network dependent thing, it could be made to function in the absence of the network,nor instance if internet connectivity is interrupted. And by work I mean that the daemon will accept a transaction.

If I understand things correctly,band I prolly don't, a transaction has the following path. Wallet -> daemon mempool -> peer mempool. And apparently, this is a single hop event, as in if the second arrow is broken, the transaction will never leave the daemon mempool.

I don't understand why the single broadcast event is required. I guess the question is what would be the signal that would cause a rebroadcast event?