> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/overview/concepts.md).

# Concepts

The Intangible-specific abstractions that the rest of the docs assume you know. Read these once and the feature pages get a lot shorter.

## Start here

* [Projects and scenes](/overview/concepts/projects-and-scenes.md): how a project is structured – scenes as locations, shots as time.
* [The three modes](/overview/concepts/the-three-modes.md): Build, Compose, Visualize – what each owns and why they're separated.
* [How the visualizer thinks](/overview/concepts/how-the-visualizer-thinks.md): semantic 3D, the multi-agent system, why prompts get built from the scene.

## Building blocks

* [Populators](/overview/concepts/populators.md): the procedural environment generators – Houdini for normal people.
* [Image reference](/overview/concepts/image-reference.md): how a reference image attached to an object reaches the model.
* [Animation and shot time](/overview/concepts/animation-and-shot-time.md): why animated movement belongs to a shot, not to a scene.

## Cost

* [Credits and tokens](/overview/concepts/credits-and-tokens.md): what every action costs and how to read the counter.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.intangible.ai/overview/concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.