> For the complete documentation index, see [llms.txt](https://docs.internetobject.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.internetobject.org/structure-and-syntax/structural-elements.md).

# Structural Elements

The characters and tokens that structure and delimit an Internet Object document.

The Internet Object format uses a small set of structural characters, literals, and other special characters to structure and delimit data. Working together with objects, strings, arrays, numbers, and whitespace, these elements compose the format's grammar and let documents express complex, flexible data structures.

## Categories

* [Structural Characters & Separators](/structure-and-syntax/structural-elements/structural-characters-n-keywords.md) — core syntax characters that organize data
* [Literals](/structure-and-syntax/structural-elements/literals.md) — predefined constant values (booleans, null, special numbers)
* [Other Special Characters](/structure-and-syntax/structural-elements/other-special-characters.md) — functional modifiers for variables, schemas, and values
* [Whitespace & Indentation](/structure-and-syntax/structural-elements/whitespaces.md) — recognized Unicode whitespace and its handling

## See Also

* [Value Representations](/structure-and-syntax/values.md) — data types and how values are written
* [Comments](/structure-and-syntax/comments.md) — comment syntax and usage
* [Encoding](/structure-and-syntax/encoding.md) — character encoding and Unicode support


---

# 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.internetobject.org/structure-and-syntax/structural-elements.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.