Validation¶
Audience: Beginners | Status: V1 Core | Verified against: v0.43.0
Validation is part of the learning experience. As you place resources and create connections, CloudBlocks checks the architecture and teaches you when a pattern breaks common cloud rules.
Use validation as feedback
Treat each validation result as an explanation of the pattern, not just a blocker to clear.
Real-Time Validation¶
As you place resources and create connections, CloudBlocks automatically checks:
- Placement rules — Resources must be placed in valid containers (e.g., VMs go inside subnets, subnets go inside networks).
- Connection rules — Only valid connection flows are allowed (e.g., Compute → Data, Delivery → Compute).
- Structural rules — Architectures must have at least one network, and resources cannot exist outside containers.
Errors appear instantly as visual indicators on the canvas.
Manual Validation¶
Run a full architecture audit at any time:
- Go to Build → Validate Architecture in the menu bar.
- View detailed results in the Validation tab in the Bottom Dock.
- Each error includes the affected block and a description of the issue.
Connection Rules¶
Connections follow real-world traffic patterns. See Core Concepts — Connections for the full connection flow table.
Key constraints:
- Receiver-only categories: Data, Security, Operations, Identity, and Network can only receive connections — they cannot initiate them.
- Allowed semantics:
http,event, anddata— each connection flow allows specific semantic types.
What's Next?¶
| Goal | Guide |
|---|---|
| Understand connection rules | Core Concepts |
| Browse architecture patterns | Templates |
| Learn the editor interface | Editor Basics |