TUSD offboarding plan

The proposal follows the standard Aave governance pattern where the on-chain action is a single delegatecall-style execute() invocation on a deployed payload contract (as referenced by the linked Solidity implementation). The decoded calldata contains no arguments or sub-calls, so it is impossible to directly verify from the calldata alone whether the specific numeric changes described (LTV 75%->0%, LT 77.5%->75%, liquidation bonus 5%->10%, reserve factor 25%->95%, borrowing/stable borrowing disabled, and interest rate curve changes) are actually implemented inside the payload contract. This is typical and expected for Aave proposals reviewed via governance forums, where the actual parameter changes live in the linked contract code rather than in top-level calldata. Since there is no contradicting evidence and this pattern is standard/expected for this proposal type, I did not flag a discrepancy, but confidence is low because the calldata itself provides no verifiable detail to cross-check against the detailed prose specification table.