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

# Notes

#### Author Note

해당 문서는 IBTC재단에서 공식적으로 발행한 프로젝트 백서입니다.

#### 다른 언어

[English](https://ibtc-whitepaper.gitbook.io/eng/)

#### 릴리즈 노트

v1.1 / 6 March 2024 / 백서  업데이트

v1.0 / 22 May 2023 / 법적고지, fig-3 및 오타 업데이트\
v0.1 / 11 May 2023 / 초판 발행

#### IBTC 커뮤니티에 접속해 보세요&#x20;

IBTC 평가 시스템(Alpha ver.) : <https://ibtc.it>\
공식 텔레그램 : <https://t.me/ibtc_official>\
공식 트위터 : <https://twitter.com/IBTC_Global>\
깃허브 : <https://github.com/ibtc-official/Sourcecode.git>


---

# 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://ibtc-whitepaper.gitbook.io/kor/notes.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.
