Start with a navigation pass
The viewer is structured to answer the first integration questions quickly: what the module is, where the key interfaces sit and which areas deserve closer inspection.
Use the default labeled state first, then narrow to the parts that matter for your workflow.
- Rotate to inspect the package.
- Toggle labels to keep spatial context.
- Use pin search when you already know the target interface.
Switch to exploded view only when needed
Exploded view is useful when connector density makes the surface hard to parse. It is not meant to be the default reading mode.
Treat it as an inspection state, not a permanent layout.
Use the inspector as a decision panel
Each viewer state is paired with a text inspector so the page works even when graphical detail is limited. That matters for documentation, search context and low-WebGL environments.
The fallback layer is deliberate: interaction should survive whether the canvas is perfect or not.