> For the complete documentation index, see [llms.txt](https://whitepaper.oyabun.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.oyabun.io/japanese/storytelling.md).

# STORYTELLING

- [起源](https://whitepaper.oyabun.io/japanese/storytelling/qi-yuan.md): 根を掘り下げる：サイバーヤクザの起源
- [キャラクターたち](https://whitepaper.oyabun.io/japanese/storytelling/kyarakuttachi.md): サイバー・ヤクザのキャラクター：ネオ東京の人々へのガイド
- [三つの勢力](https://whitepaper.oyabun.io/japanese/storytelling/tsuno.md): 三つの勢力：ネオ東京の三本柱
- [地平線の先](https://whitepaper.oyabun.io/japanese/storytelling/no.md): 未来の一瞥：ネオ東京の航路を描く
- [大須: ラーメン物語](https://whitepaper.oyabun.io/japanese/storytelling/rmen.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, and the optional `goal` query parameter:

```
GET https://whitepaper.oyabun.io/japanese/storytelling.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.