The account data to write, in the order to write it.
Five events: the key description, one per private signing key, and the pointer that makes the new key this account's default.
The pointer is last, and the order is load-bearing. Everything before it adds to the account without changing what any client currently resolves, so a product interrupted partway through has written a key description and some ciphertexts that nothing points at, and whatever recovery the account had before still works. Writing the pointer earlier would repoint the account at a key whose secrets do not exist yet, which is a window in which neither the old recovery nor the new one opens anything.
The recovery key, in the base58 form the Matrix specification defines, grouped in fours.
This value is never stored and can never be produced again. It is the passphrase's equal rather than a backup of it: either one opens the recovery, and losing both loses the account's identity for good. See createRecovery for what that costs.
What createRecovery produced: the one secret to show your user, and the account data to write.