Bring supported assets
into Maple.

A bridge with
defined boundaries.

Morph is the asset-conversion application in the planned Maple family. It is intended to turn supported external assets into Maple-native assets, providing a preparation role distinct from creating the original asset.

Conversion depends on what an input contains and what the destination can represent. That is why Morph is described as supporting particular assets, rather than promising a universal conversion of every file or every feature.

No public source-format or destination-format list is announced here. Specific compatibility, preservation rules, and conversion limits will need verified documentation.

Conversion is
one possible route.

An asset created externally may need a supported conversion route before it can be used in Maple. Morph defines that role. An asset created within another Maple application may have a different route as the suite develops.

Not every asset must pass through every tool. Foundry is modeling, Soar is animation, Design is sprite creation, Morph is conversion, and Engine is runtime. Keeping those jobs separate makes the intended workflow more honest and easier to follow.

This is a conceptual division of responsibilities. It does not announce a released end-to-end pipeline or imply that all external asset details will survive a conversion.

Compatibility needs
a specific answer.

A useful support statement eventually needs to identify the input type, the information carried through, any limits or losses, and the destination requirements. Simply naming a familiar external tool would not establish that every asset from it is supported.

Until the actual supported scope is announced, this site avoids promising exact file formats, automatic fidelity, arbitrary batch conversion, or complete interoperability.

No public Morph download, price, release date, licensing program, or conversion service is announced here.

Ask with
the asset context.

For a question about Morph, email contact@casilian.com. Mention the application and describe the type of workflow you want to discuss.

Public reference links can help explain the question. Do not send account credentials or confidential files simply to ask whether a workflow is in scope.