# 本編

- [まえがき](https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents/0-foreword.md)
- [なぜインナーソースなのか](https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents/1-why-innersource.md)
- [インナーソースとは何なのか？何ではないのか？](https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents/2-what-innersource-is-and-isnt.md)
- [最も重要な役割、そして最初の一歩: トラステッドコミッター](https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents/3-the-most-important-role-and-the-first-step-trusted-committer.md)
- [検索可能性の必要性とパッシブドキュメンテーション](https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents/4-passive-documentation-and-the-need-for-findability.md)
- [来客に良いハウスルールを作る: コントリビューション協定を書く](https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents/5-creating-good-house-rules-for-guests-writing-contributing-agreements.md)
- [組織内にあてはめる: 計画の理解](https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents/6-working-within-the-enterprise-understanding-planning.md)
- [組織内サイロから組織内透明性へ](https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents/7-from-internal-silos-to-internal-transparency.md)
- [今後の展望](https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents/8-looking-forward.md)
- [実際のチェックリスト](https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents/9-appendix.md)


---

# Agent Instructions: 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:

```
GET https://jp-contents.innersourcecommons.org/understanding-the-innersource-checklist/contents.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.