CONF iture,
It would appear the protections came on for good reason, because of the ADIRU generated high angle of attack. It would also appear the protections responded the way they should have in response to the angle of attack generated by the ADIRU.
The output from one ADR was not correct, "the recorded parameters of the ADR part of ADIRU 1 include erroneous and temporary wrong values in a random manner" from the time the AP was disconnected.
The procedures for dealing with "unreliable speed" and "unjustified stall & overspeed warnings" is listed in the QRH, they may not come up on ECAM as the ADIRU cannot detect unreliable speed. The procedure calls for the faulty ADR to be turned off after the speeds have been cross checked.
FCOM 3 also says in case of simultaneous failure of ADR and IR (same ADIRU), the ADR FAULT procedure should be applied BEFORE the IR FAULT procedure (where you would turn off the failed ADR as part of the procedure). That is listed at the start of the NAV IR FAULT, and NAV ADR FAULT FCOM 3 procedures.
Did you know the QRH and FCOM 3 references to turning off the failed ADR before making your posts ?
I will be keen to see the ATSB report when it is issued.