TUSD offboarding plan

The decoded calldata contains only a single generic execute() call to a proposal payload contract, which is the standard Aave governance pattern: the actual risk-parameter changes (LTV, LT, liquidation bonus, reserve factor, interest rate curve, borrowing flags) are implemented inside the payload contract's bytecode rather than passed as visible calldata arguments. Because the decoded action does not expose the individual parameter values, it is not possible to directly verify each numeric claim in the description (LTV 75%->0%, LT 77.5%->75%, liquidation bonus 5%->10%, reserve factor 25%->95%, borrowing disabled, rate curve changes) against on-chain data. The description links to the corresponding implementation and test source files, which is consistent with this architecture and gives reasonable assurance the payload matches the stated intent, but this cannot be confirmed from the decoded action alone. No contradiction is evident, and the single execute() call is fully consistent with what the description implies (a payload executing the offboarding plan), so there is no basis to flag a discrepancy. Confidence is set to low because the calldata's opacity prevents a rigorous line-by-line verification of the specific parameter values claimed in the prose.