Docs— Structure behind a calm, AI-native notebook
Fragment is an AI-native notebook for structured thinking. You write as small pages called Fragments, and add just enough structure with YAML config blocks, Scene / Flow diagrams, and Prism Protocol when you need it. These docs explain how those pieces fit together.
このドキュメントは、Fragment の「ページ構造とふるまい」の地図です。 ノート 1 枚（Fragment）の中に、Markdown と YAML、Scene / Flow 図、Prism プロファイルがどう並び、どこまで AI に開くかを説明します。
A gentle path: Getting started → Fragment basics. You can come back here later for YAML, diagrams, or Prism only when you actually need them.
The docs follow four layers. You don't have to learn them all at once — it's enough to know that they stack on top of a single page (a Fragment).
Each layer is written so that humans and AI can read the same text — no separate prompt documents, no one-off diagram screenshots that go out of sync.
まずは「Fragment = 1 枚のノート」として使い、必要になったときだけ YAML や Scene / Flow、Prism を足していく前提の構成になっています。
Start from the part that matches your current question: “What is a Fragment?”, “How do I write YAML safely?”, “How do diagrams work?”, or “How do I shape AI's tone?”.
What a Fragment is as a page: identity, scope, content, metadata, and how it appears in Studio, Reader, and Deck.
How Fragment uses front-matter and inline YAML blocks to add small, human-readable structure next to Markdown.
A lightweight text-first DSL for diagrams inside a Fragment. Scene for layouts; Flow for processes and logic.
A small YAML profile that describes how AI should behave on a page: persona, tone, boundaries, and explanation style.
What is available today, what we are actively building next, and the long-term direction of Fragment.
Where Fragment comes from and the principles behind a calm, low-noise, AI-native notebook.
Depending on how you meet Fragment, different entries make more sense:
Fragment のドキュメントは、「最初から全部読む」前提では書いていません。 いま必要な概念を 1 つだけ調べて、あとはノートを書くほうに時間を使ってください。
If you'd rather feel the notebook before reading specs, start with Getting started, templates, or public Fragments. Skim a few concrete pages, then come back here only when you want to understand the underlying structure.
まずは「使ってみる」→「気になった部分だけ調べる」という順番で大丈夫です。ドキュメントは、 実際のノートやテンプレートの「裏側」をあとから確認するための場所として設計しています。
