Quote: for jump thoughts it's still relevant, where you start to draw the link, see thoughts "X" and "jump" in second image above. Links to parent and child thoughts are handled like you said. Yes. I suppose it could behave either as Source -> Target, or Left|Right. I could go either way, but I think my preference is with the current behavior. Maybe.
Quote: Currently, the links point from a parent to a child thought. If you have a link type like "is a" above, I suppose, you must have either two different link types, or you ever create a "is a"-link in the form "parent 'is a'(reversed direction) child". Not necessarily. The directionality of the link is still hierarchically before link type, so if you changed the link direction it will override link type arrow direction. In my database, directionality is generally very consistent for link type relationships. For example, Performed in always points from Child -> Parent, Reports To Always points Child -> Parent, Requested by always points from Parent -> Child, Author of always points from Parent -> Child. In TheBrain 8 and lower I'd always have to stop to think about which way I'm dragging the link to make sure the arrow pointed in the same direction before I assigned the link type. In actual use this generally followed the following pattern: Drag the link Apply the link type Roll my eyes because I'd forgotten and dragged the link from the wrong thought's gate Fix the arrow direction. In the case you brought up there are several options I'd look at:
Create two link types - Very quick to assign, will show differently on report Use one link type, change on the link - takes longer, will show under one on report Look at what I'm trying to achieve with the data presentation and see if the relationship should always be the same.