Write Directly to Containers from Transformations

Hi,

Currently, transformations must target a view to populate a container. But if we update the view (e.g. remove an attribute that we no longer want to expose), the transformation will no longer populate that field — even though the container still supports it.

As a result, existing users relying on older views that still expose this attribute will see empty data, creating unintentional breaking changes.

Suggestion:
 Enable transformations to write directly to containers

This would:

• Ensure stable ingestion regardless of view changes,
• Prevent breaking downstream users,
• Simplify the data pipeline.