`MAZENG-FT-18` · Compose a cloud-resource topology

Feature intent

Users need to build a cloud-resource topology visually while receiving clear feedback when a placement or connection is invalid.

Why it matters

Users need to build a cloud-resource topology visually while receiving clear feedback when a placement or connection is invalid.

Users can create and maintain a persisted topology of supported resources, containers, and relationships without executing infrastructure.

Add supported resources to a project at valid canvas locations.
Place resources in valid containers and connect only compatible resources through a selected relationship.
Remove resources with explicit visibility of affected descendants and persist the updated topology.
Infrastructure execution is excluded.

Acceptance

01
Dropping a supported resource at a valid location creates it and persists both resource and canvas data; invalid placement explains why it was rejected.
02
A user can connect only compatible resources, select the relationship represented by the connection, and reopen the project with that relationship intact.
03
Removing a resource explicitly identifies affected descendants and updates the saved topology.

None recorded.

Container and connection compatibility rules may diverge between the visual model and persisted representation.
Descendant removal can cause unintended topology loss unless impacts are confirmed before persistence.

No authoritative Architecture tasks are linked.