Sky proposes Osero Morpho-vault onboarding and removal of a penalty-setting timelock

What happened

Sky Core GovOps submitted the Atlas weekly-cycle proposal for the week of September 28. It proposes adding the Gauntlet USDC Prime Morpho Vault V2 to the Osero Liquidity Layer and changing Atlas rules so the force-deallocate penalty is not subject to a minimum timelock.

What changed

Nothing is operative yet. If adopted and implemented, Osero would gain a new ERC-4626 vault allocation surface and governance could introduce a force-deallocate penalty without the prior seven-day minimum delay.

What did not change

The proposal does not document an executed spell or on-chain implementation. It does not establish that assets have been allocated to the vault or that the proposed timelock exemption is already operative.

Confirmed

• The proposal was submitted by Sky Core GovOps.
• The proposed Osero onboarding enables ERC-4626 and PSM facets for the named vault configuration.
• The proposal would remove the seven-day minimum timelock requirement for setting the force-deallocate penalty.

Still open

• Whether the proposal will be adopted and implemented on-chain.
• The final deployed vault parameters, role holders, signer thresholds, and operative timelocks.
• Whether the proposal's identified documentation warning concerning the max-exchange-rate setter will be resolved before implementation.

What it means for an advisor

• Monitor the governance outcome and any implementing spell before treating the vault or control change as operative.
• Review the Sky memo if execution introduces the new allocation dependency or removes advance notice for penalty changes.
• Confirm deployed roles, limits, timelocks, and emergency-exit mechanics after execution.

Previous interpretation

Sky's reviewed control perimeter did not include this proposed Osero vault configuration or a no-minimum-delay rule for the force-deallocate penalty.