> For the complete documentation index, see [llms.txt](https://docs.studio.uzu-app.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.studio.uzu-app.com/en/basic-features/phase/basic/discussion.md).
# Basic phases
In the Basic Phase, you can display **text, images, decks, and actions**. This phase is suitable for loading character texts, discussing, investigating, presenting explanations, and verifying additional information.
\\
## Fields to Input and Their Content
| Field | Content | Example |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| Management Title (Optional) |
A title used by the author on Uzu Studio for memo-like purposes during scenario implementation. It does not reflect on the app.
| Phase next for ○○・If ○○ then |
| Title (Required) | Sets the title displayed at the top. | Character Text Loading・First Discussion |
| Subtitle (Optional) |
Set the text displayed in black under the title. If left blank, it will not be displayed.
| Please open the text tab・Start the discussion |
| Caption (Optional) |
Set the text displayed in gray under the title. If left blank, it will not be displayed.
| Discussion time is 10 minutes・Clues can be revealed |
| Required Time | If the phase completion condition is set to "Next Button," it's the estimated time required; if set to "Time Limit (Timer)," it's the timer setting time. The former does not display on the app. | Enter numeric values |
| Phase Completion Condition (Required) | Decide whether to proceed by pressing the "Next" button or by setting a "Timer." | - |
| Characters Who Can Press Next Button (Required) | If the phase completion condition is set to "Next Button," you can set which characters can press it. It's good to allow all if there's no particular preference. | - |
| Phase Content (Required) | Set the text, images, decks, and actions to be displayed on the common screen. | Instruction text・Common information・Decks・Actions |
\\
## About the Phase Content
Adding text, images, decks, and actions is done through the "Add +" button.
A popup like the following will appear, so select what you want to add.
For text, you can use the following types of text decorations.
\\
For images, you can set **where to align the image** (left-aligned, centered, right-aligned) and **how big** to display it.
\\
## Distributing Phase Content as Text
If you want to distribute the information displayed on the common screen during this phase to the **text tab** as well (to make it reviewable later), set it up from the menu on the right.
If you want to add synchronized text (cannot be edited from the text side; editing on the phase side automatically reflects on the text) with the phase content\
→ Just turn ON "Distribute as Text" for phase content recording.
If you want to add copied text (can be edited from the text side) from the currently inputted phase content:
1. Press "Add +" for distribution.
2. Select text.
3. Open the distribution text field.
4. Select "Copy of this phase".
Synchronized text is useful for adding rule explanations and common information, while copied text is convenient for content that requires individual editing.
---
# 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://docs.studio.uzu-app.com/en/basic-features/phase/basic/discussion.md?ask=&goal=
```
`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.