Menu

About

About Fragment

Fragment is a calm, AI-native notebook. You write in Markdown as usual, and only when it matters you add small YAML configs, Prism profiles, or Scene / Flow diagrams so that humans and AI can share the same structure on one page.

Fragment は「AI と一緒に考えるための静かなノート」です。 ふつうの Markdown ノートとして書き始めて、必要なときだけ 小さな YAML 設定・Prism(ふるまいのプロトコル)・Scene / Flow 図を足していきます。

AI-native, text-firstEthics as configurationPrism-friendly structure

Fragment: one small unit of living knowledge

Fragment is not just “another notes app”. It's a page model built for AI-heavy work: one note, one URL, one small unit of living knowledge that can travel with its assumptions and diagrams.

1 ページの Fragment は、ヘッダ・本文・小さな設定ブロック という シンプルな構造を持っています。ユーザーは「タイトル+本文+必要になったら少し設定を足す」 だけを意識すればよい設計です。

The three main pieces

  • Header — id, title, scope (private / unlisted / public), tags, timestamps, layout hints.
  • Markdown body — the main narrative you write: journals, specs, lecture notes, reviews, essays.
  • Small blocks — YAML config, Prism profiles, and Scene / Flow diagrams that sit next to the text instead of in separate files.

Internally, Fragment keeps these pieces in a way that is easy to version, export, and send to AI as one coherent context.

Design principles

Fragment is intentionally small in scope. Rather than chasing every feature, it focuses on a few principles that make thinking with AI feel steadier.

Calm first

The interface is quiet by design: a single page, gentle typography, no flashing side panels. AI appears after you've written something, so your own voice stays visible.

Ethics as configuration

Expectations for AI — tone, boundaries, “what to avoid” — live in Prism profiles and YAML, not only in one-off prompts. This makes behavior reviewable, shareable, and easier to adapt over time.

倫理や距離感を「設定ファイルとして書く」ことで、人と AI が同じ前提を見る ことを目指しています。

Shared text for humans & AI

Diagrams and configs are text-first. Scene / Flow, Prism, and config blocks are all readable as plain text, so you can diff them, copy them, and ask AI to “walk through” them with you.

How Fragment shows up in the product

Everything in Fragment is built around the page model: Fragment as a unit you can write, read, and share from different angles.

Studio

The editor where you write and grow a Fragment. Markdown, YAML blocks, Prism, and Scene / Flow diagrams live in one place.

Open Studio →

Reader & public Fragments

A calm reading view for public and unlisted Fragments. Good for sharing essays, templates, and teaching notes without the editing chrome.

Browse public Fragments →

AI & structure

When you call AI on a page, Fragment can send the body, Prism, YAML, and diagrams together. The model sees the same structure you do, not just an isolated paragraph.

Read Prism docs →

Fragment Practice (the studio)

Fragment Practice LLC is a very small studio designing thinking environments for humans and AI. It works across product, information architecture, and protocol design — from the Fragment app itself to Prism / Scene / Flow and related consulting work.

Fragment Practice は、新庄 泰大 による小さなスタジオです。 個人や小さなチームが AI と一緒に考えるときの「場」と「ルール」を、 プロダクトとプロトコルの両方から設計しています。

Work modes & contact

  • • Building Fragment as a calm, AI-native notebook
  • • Designing Prism / Scene / Flow and related specs
  • • Light consulting around AI usage rules, thinking rhythms, and information architecture

For collaborations, research, or press, feel free to reach out.

Current phase

Today, Fragment is in an early but steady phase: focusing on solid writing, simple structure, and reliable AI behavior rather than big growth.

  • • Stable Fragment page model (header, Markdown, blocks)
  • • Studio / Reader improvements for everyday notes
  • • First versions of YAML, Prism, Scene / Flow inside the editor

Where it's heading

Next steps focus on small teams, classes, and labs — places where people already keep notes but want clearer structure and safer AI collaboration.

  • • Collections and light “booklet” / zine-like grouping of Fragments
  • • Better cross-page links, relations, and timelines
  • • Stronger Prism / API surface for experiments and research

You can see the evolving snapshot on the Roadmap.

Start with one Fragment, then add structure only when it helps

If this resonates, you don't need a perfect system to begin. Write one real page — today's note, a small spec, or a weekly reflection — then add a tiny Prism block or YAML config only when it feels useful.

Fragment のコアはとてもシンプルです。まずは 1 件の Fragment を書いてみて、必要になったときにだけ 少しずつ構造を足していく──そのくらいのペースで使ってもらえたらうれしいです。

About Fragment — Fragment