I would like to understand how Ethereum "messages" (originated from a smart contract) can transfer Ether to another account without a blockchain confirmation.
From the following SO answer I gathered that there are "formal" and "practical" definitions for "messages" and "transactions":
Message: Data (bytes) and Value (Ether) passed between two Accounts (either through the deterministic operation of a smart contract or the secure signature of a Transaction).
Transaction: Data sent from an EOA specifically. It represents either a Message or a new smart contract. Transactions are recorded into the blockchain.
Message: Data sent from a smart contract. Not delayed by mining because are part of the transaction execution
Transaction: Data sent from an EOA. It's always a transaction that gets things started, but multiple messages may be fired off to complete the action.
That indicates that messages are "not delayed by mining because they are part of the transaction execution".
This SO answer repeats that in different words: "The act of passing a message from one Account to another. If the destination account is associated with non-empty EVM Code, then the VM will be started with the state of said Object and the Message acted upon. If the message sender is an Autonomous Object, then the Call passes any data returned from the VM operation"
This SO answer indicates "message calls are not published on the blockchain" because they are part of an initial transaction that starts a domino process. (unquoted wording mine)
So lets assume transaction X transfers Y Ether from EOAccount1 to SmartContract1. That transaction gets confirmed on the blockchain in 20 minutes. The EVM code of SmartContract1 triggers, and following the code's instructions in 30 days SmartContract1 sends a message to SmartContract2 with Z Ether. How can the latter Ether transfer be part of the initial transaction? How can it not be confirmed in the blockchain? Thank you.