I compared the four tables/claims in the description against the four decoded actions. The tETH supply cap reduction (10,000 → 5,000) on two mainnet comets is faithfully implemented: two updateAssetSupplyCap calls set newSupplyCap to 5000e18 (5,000 tokens with 18 decimals, matching the claimed value), each paired with a deployAndUpgradeTo call to finalize the change on the respective comet proxy — this is routine and consistent. However, the description also claims two additional changes: raising the cbBTC supply cap on Base USDS from 0 to 450, and reducing Base USDS daily COMP incentives from 24 to 20. Neither of these appears in the calldata at all — there is no Base-chain action, no cbBTC-related call, and no reward configuration call. This means half of the proposal's stated changes (2 of 4 claimed parameter updates) would not actually execute if this proposal passes, despite being presented as part of the same package. This is a significant gap between what delegates are told will happen and what the calldata will actually do, warranting a material discrepancy flag so voters are aware the cbBTC and incentive changes are not included in this particular on-chain execution.