> For the complete documentation index, see [llms.txt](https://docs.acecentre.org.uk/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecentre.org.uk/products/pasco/advanced/tree-file-details.md).

# Tree / Language file details

There are three formats that pasco reads langauge trees in.

1. **Mindnode - Markdown format. - ATX Style**

Files look a little like this:

```
# Chat


## How are you?

- Ace!

- Whats that?

- 

## Whats happening?

- Yeah for sure

## I’m fed up


# I need something


## Its in my bag

## Its somewhere else

## Its upstairs
```

It's not the easiest to read - note that with markdown line breaks are key. It's easiest to generate this with something like MindNode - an iOS and Mac app to generate MindMaps. It really is a breeze

1. **Tab OR Space Indented text file**

Here a file looks like this:

```
Chat
	How are you?
	Ace!
	Whats that?
	Whats happening?
		Yeah for sure
	I’m fed up

I need something
	Its in my bag
	Its somewhere else
	Its upstairs
```

It looks a little easier to read - but be **warned** - spaces and tabs at the beginning cannot be mixed. Don't put a space and then a tab. Its not the easiest.

1. **Open Board format**

Pasco natively supports the [open board format](https://www.openboardformat.org). To use this simply upload your board(s) as a 'obz' file in the **Configuration** screen - and hopefully it should work! Note that we of course strip images - and right now there is no built in 'cue' for items. We use the label for this.

To export - select **Export** in the **Configuration** screen and select 'obz' format. You will need a way of sharing this file - either via email or your files app (and then dropbox etc) to make use of this outside of your iPad. Note it exports all your sound files too.

![Setup screen](https://1729435929-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlkGpHI3undR5vI9VWWTz%2Fuploads%2Fgit-blob-a30fb04f0051f82bc5fe79447c249d2f95576c8a%2Fexport-obz.png?alt=media)

[![Image from Gyazo](https://i.gyazo.com/e21b312aa955ef896c71faf724015948.gif)](https://gyazo.com/e21b312aa955ef896c71faf724015948)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.acecentre.org.uk/products/pasco/advanced/tree-file-details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.