Yes, we did decide on a strategy for letting Core-Animated views participate in auto layout.
When we generate code for the animated view (hierarchy), we implicitly add a view that actually contains the canvas from your project. This outer view has no function other than to contain the views that are actually animated. This outer view can have auto-layout constraints and can be positioned in Interface builder. Because having auto-layout constraints will not necessarily keep the original aspect ratio (the aspect ratio of the canvas in your Core Animator project), we allow it to respect the contentMode property of UIView. That is, when you add a core animated view to an interface builder document, you can select from the contentMode dropdown. We respect aspectFit, aspectFill, and scaleToFill.
Another cool thing is that the generated classes are marked as IBDesignable. This means that you will be able to preview your Core Animated views along side everything else in your IB document, thereby instantly seeing the results of any auto-layout constraints you add.
Pretty slick. Gotta love IBDesignable.