> For the complete documentation index, see [llms.txt](https://www.oulan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.oulan.com/2023/11/06.md).
# 06
不舍昼夜
该怎么识别清晨还是夜？\
该怎么探索青春还是苍老的边界？\
该怎么确认阳光还是阴雨的田野？\
我们在阴影下落座\
阳光洒了\
思绪成河
该怎么听取一些噪声或者颂歌\
该怎么从一朵花开始发散抵达一个村落进行总结\
该怎么切分层次或整体建模\
我们在草地上快活\
小狗土豆在沉默\
有话想说
该怎么听出一些禅意或者临在一些福音\
该怎么运用风的能力或者任由时间改变世界\
该怎么运转一种思维或者构造外置大脑\
我们将视野聊得更开阔\
一些崭新的\
角色
该怎么收集远山的雪或者心灵亲吻过的落叶\
该怎么抵达一处期许或是从一处热望路过\
该怎么解析一根稻草抓住另一根稻草的热烈\
我们是物质也是波\
一些思想烧着了\
在干涉
---
# 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://www.oulan.com/2023/11/06.md?ask=&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.
