Docs

Reading the structure

Shapes, colours, the toggles, isolating a field, and the banner the walk lights.

The structure is the graph as a molecule: every drawn field a sphere, every automation a diamond, and every bond a field an automation touches. It is the view for "what writes this field" and "what does this workflow reach".

Shapes and sizes

• Spheres are fields. Sized by how many automations contend for them: the busiest field in the portal is the biggest body on the screen.
• Diamonds are automations. Sized by how many fields they write.
• Hexagons are shells. Automations that touch only one drawn field fold into one shell per field, system and direction, labelled with their count, so a portal with hundreds of workflows stays legible. Forms fold apart from workflows.
• A hollow shape is a disabled automation.

Colours

Colour is an encoding, never decoration. Orange is HubSpot in every view; blue is Google Cloud; green is Apps Script; the other systems have their own. Each bond runs from the colour of the system that acts to the grey of the field it touches, so a field with bonds arriving in several colours bridges several systems. A gold ring marks a field another system reads; a red ring marks one with six or more deciding writers.

Bonds

A solid bond is a write; a thin one is a read; a dashed one is inferred from source and not yet confirmed. The Bonds group in the HUD turns each direction on and off, and Show hides inferred edges or input capture (forms), and switches between the shaded and flat renderers.

The toggles

The HUD on the left is the representation ladder. Systems hides a whole system. Fields hides an object, or one of the CRM's own property groups under it, and an automation whose every drawn field is hidden goes with them. Nothing here changes the graph; it changes what is drawn.

Isolating a field

Click a body and everything not bonded to it dims. Press esc to clear, f to refit the camera. Drag to rotate, scroll to zoom.

What is drawn

The footer says: how many of the graph's fields are drawn, and why. At the default level a field is drawn when two or more deciding writers contend for it, when more than one system touches it, or when it is declared a funnel. The rest are in the graph and not drawn, which is why the walk's banner can say n not drawn at this level.

The lit banner

When the trajectory's walk is linked to the structure, each step lights that stage's automations and the fields they write here, dims everything else, and frames the camera on what is lit. The banner at the top says what is lit and how many of the asked-for items this level does not draw. esc clears it.