Each of the resulting files contains data for one object type consisting of one line of JSON for each object of that type.

The entire outputted chunk of text, taken as is, as a whole, is indeed not valid JSON. But each individual line is a valid JSON object. And the entire export can easily be made into valid JSON by inserting a comma after each line and wrapping the entire thing in square brackets. This was done this way intentionally, so that it can easily be processed progressively without the need to load the entire file at once. If you would like to turn the entire text into a valid JSON string, add commas at the end of each line except the last, then add a starting `[` and an ending `]` around the entire contents.

While we do not offer support for working with the JSON files, the following list details the meaning of the less obvious but still important properties.

### Thoughts.json
ACType
   Public = 0,
   Private = 1,

Kind
   Normal = 1,
   Type = 2,
   Tag = 4,

### Links.json
Relation
   NoValue = 0,
   Child = 1,
   Parent = 2,
   Jump = 3,
   Sibling = 4,

Direction - Binary flags
   OneWay = 4, // x1xx, 1 means One-Way Link;
   DirectionBA = 2, // xx1x, 0 means A -> B, 1 means B\->A, isBackward
   IsDirected = 1, // xxx1, 1 means Is-Directed; xxx0 means Not-Directed

Meaning
   Normal = 1,
   InstanceOf = 2, // Type (A) to Normal Thought (B)
   TypeOf = 3, // Super Type (A) to Type (B)
   HasEvent = 4,
   HasTag = 5, // Tag (A) to Normal or Type Thought (B)
   System = 6,
   SubTagOf = 7, // Super Tag (A) to Tag (B)

Kind
   Normal = 1,
   Type = 2,

### Attachments.json
Type
   InternalFile = 1,
   ExternalFile = 2,
   ExternalUrl = 3,
   NotesV9 = 4, // HTML-based notes from TheBrain 9 and 10
   Icon = 5,
   NotesAsset = 6,
   InternalDirectory = 7,
   ExternalDirectory = 8,
   SubFile = 9,
   SubDirectory = 10,
   SavedReport = 11,
   MarkdownImage = 12,