Reading the tree

Graph (Tree) view & List view

The Graph (Tree) view shows the project as a tree of nodes. It lets you take in the overall shape of the project at a glance, along with its dependencies and API connections. The List view, on the other hand, lays the project out as a list. It gathers nodes that spread wide into one place, so use it when readability matters. Wide screens open in the graph view by default, narrow screens in the list view. To switch views, use the view toggle at the bottom right.

Layers

In the sidebar you can toggle which layers are shown. Apart from trunks and limbs, you can hide twig, leaf, and vein nodes to cut down how much is on screen. You can also control the display of the three elements below.

• API — calls between nodes, drawn as a green line (#4EA88F). A planned API is dashed; a committed one is solid.
• Edge — a structural link between nodes; if it breaks, problems can follow. Drawn as a blue line (#8AA4C8): a data flow (data_flow) is dashed, a dependency (dependency) is solid.
• Bugs — where the currently found or registered bugs sit and what they are. Drawn in red (#CC0000).

Impact

Select a node and turn on Show impact to see its blast radius — the other nodes affected if that node breaks. When an agent registers a bug, it gets this blast radius back and uses it to work out what else to check.

Bugs

Register a bug on the node where it occurs, or on the ground itself without assigning a location. When you register a bug you can set its status (Wild / Chasing / Resolved) and give it a risk score (0–8). Because it sits on the tree, you can see where it is at a glance and read its blast radius and risk together.

• Risk score — how much could break combined with how hard the fix is: 0 for no risk, 8 for the riskiest.

  • 0 Memo — no risk. An idea-level note
  • 1 Copy — no risk. A wording or copy edit
  • 2 Usability — no functional error, but may affect usability
  • 3 Minor · simple fix — a minor functional issue is possible, and it is simple to fix
  • 4 Minor · complex fix — a minor functional issue is possible, and the fix is complex
  • 5 Significant · simple fix — a significant functional issue is possible, and it is simple to fix
  • 6 Significant · complex fix — a significant functional issue is possible, and the fix is complex
  • 7 Critical · simple fix — a critical functional issue is possible, and it is simple to fix
  • 8 Critical · complex fix — a critical functional issue is possible, and the fix is complex