> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/kizen-basics/kizen-in-action.md).

# Kizen Basics in Action

See how Kizen works in practice through guided walkthroughs that show how data, Activities, and Agentic Workflows come together.

## **Welcome to Flywheel Adventure Park**

<code class="expression">space.vars.Theme\_park\_name</code> is the example business we use to demonstrate how the <code class="expression">space.vars.Kizen\_company\_name</code> platform works in a real-world setting. Instead of learning features in isolation, you’ll follow how a single business uses <code class="expression">space.vars.Kizen\_company\_name</code> to connect data, manage interactions, automate operations, and support every part of its workflow.

To make the concepts concrete, you’ll track the experience of the Reyes family, a typical family visiting the park:

* **Marcus**, who plans the trip and books the tickets
* **Elena**, who manages family schedules and communicates with the park
* **Sofia (age 12)**, who needs a waiver for rides
* **Caleb (age 8)**, who also needs a waiver

As they move through the park’s online booking, entry, activities, purchases, and follow-up surveys, you’ll see exactly how <code class="expression">space.vars.Theme\_park\_name</code> uses <code class="expression">space.vars.Kizen\_company\_name</code> to support its day-to-day operations.

Behind the scenes, the park handles ticketing, guest requests, operations, lost items, food sales, and ongoing guest communication, all set against the roller coasters, spinning rides, carnival games, and concession stands of a classic amusement park. This use case gives you a practical, end-to-end view of how <code class="expression">space.vars.Kizen\_company\_name</code> ties everything together so you can begin building your own <code class="expression">space.vars.workflows</code>, data structures, and <code class="expression">space.vars.automations</code>.

Use this walkthrough as your starting point for learning the <code class="expression">space.vars.Kizen\_company\_name</code> Basics: how it works, how data connects, and how you can bring all your operations into one intelligent, adaptable platform.

***

## What's Next?

Start by reviewing the [prerequisites](https://developer.kizen.com/docs/kizen-basics/kizen-in-action/prerequisites-or-kizen-in-action.md) required to complete the <code class="expression">space.vars.Kizen\_company\_name</code> Basics in Action walkthroughs.


---

# 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://developer.kizen.com/docs/kizen-basics/kizen-in-action.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.
