> For the complete documentation index, see [llms.txt](https://flow-core.gitbook.io/flow-core-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flow-core.gitbook.io/flow-core-docs/documentation/getting-started/start-here.md).

# Start Here

Level: Beginner

## Goal

Choose the right first reading path, build a first visual graph, and know what result should appear in Unity before moving into deeper concepts.

Flow Core is easiest to learn by making one observable graph first. The first result should not be a code call or a large gameplay system. It should be a scene object, a Local Blackboard value, a Start Trigger, an Action, and a Console line that proves the graph is running.

## Prerequisites

* You can create assets in the project.
* You can select and edit GameObjects in a scene.
* Flow Core menus are visible in Unity.
* You can open the Unity Console.

## Start Path

| If you want to...                                      | Read this first                                                                                       | What you should get                                                                        |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| Build the first visual result                          | [First 15 Minutes](/flow-core-docs/documentation/tutorials/first-15-minutes.md)                       | `Hello Flow Core` printed from a graph in Play Mode.                                       |
| Understand how the graph is bound to a scene object    | [Run a Flow Graph in a Scene](/flow-core-docs/documentation/tutorials/run-a-flow-graph-in-a-scene.md) | A clear model of graph asset, `FlowCoreProcess`, Local Blackboard, and Unity `Start`.      |
| Fix a graph that does not run or reads the wrong value | [Debug a Running Graph](/flow-core-docs/documentation/how-to-guides/debug-a-running-graph.md)         | A repeatable checklist for graph assignment, Debug Context, Trigger, and Blackboard scope. |
| Understand the main vocabulary                         | [Beginner Glossary](/flow-core-docs/documentation/reference/glossary.md)                              | Short definitions for Graph, Node, Trigger, Chain, Blackboard, Scope, and Debug Context.   |
| Decide what Flow Core is for                           | [What Is Flow Core](/flow-core-docs/documentation/core-concepts/what-is-flow-core.md)                 | The mental model for visual workflow, data, graph ownership, and runtime execution.        |

## Recommended Order

1. Build the Hello Flow Core graph.

   Follow [First 15 Minutes](/flow-core-docs/documentation/tutorials/first-15-minutes.md) exactly. Do not skip the Local Blackboard step; it is the first data-flow moment.
2. Bind the graph to a scene object.

   Use [Run a Flow Graph in a Scene](/flow-core-docs/documentation/tutorials/run-a-flow-graph-in-a-scene.md) to understand which part lives in the graph asset and which part lives on the GameObject.
3. Set Debug Context when reading values.

   Debug Context tells the editor which scene object should be used for preview and summaries. Without it, the graph may be valid but hard to inspect.
4. Read concepts after the first result.

   Once the Console prints `Hello Flow Core`, move into concepts, Blackboard scope, editor workflow, and node reference pages.

## Expected Result

* You can create a Flow Graph asset.
* You can bind it to a scene GameObject through `FlowCoreProcess`.
* You can attach a Local Blackboard and read a `String` key named `Say`.
* You can run a visual graph from Unity `Start`.
* You can see `Hello Flow Core` in the Unity Console without writing C#.

## Common Mistakes

* Reading reference pages before building the first graph.
* Treating the first tutorial as a code exercise instead of a visual data-flow exercise.
* Creating the Blackboard but not adding it to `Local Blackboards`.
* Setting Debug Context to a different GameObject than the one running the graph.
* Changing the key name in one place but not the other.

## Next Steps

* [First 15 Minutes](/flow-core-docs/documentation/tutorials/first-15-minutes.md)
* [Run a Flow Graph in a Scene](/flow-core-docs/documentation/tutorials/run-a-flow-graph-in-a-scene.md)
* [Blackboard UI](/flow-core-docs/documentation/editor-guide/blackboard-ui.md)
* [Graph Editor](/flow-core-docs/documentation/editor-guide/graph-editor.md)
* [Beginner Glossary](/flow-core-docs/documentation/reference/glossary.md)


---

# 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:

```
GET https://flow-core.gitbook.io/flow-core-docs/documentation/getting-started/start-here.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.