Organize Source Material for AI — Raw Notes, Honest Reading
Raw notes are fragments, not conclusions. Package them so the AI organizes without inflating — a four-word note stays an observation, not a firm claim.
Overview
Working notes are the most misread source type: fragmentary, unordered, full of half-thoughts — and models love completing them into conclusions the writer never reached. The notes type packages fragments with the honest-reading rules: fragments are observations, not conclusions; a four-word note must not inflate into a firm claim; and where notes conflict, the conflict gets reported, because notes have no authoritative order. This setup loads a raw working-notes dump with the organizing task framed correctly: themes without invented conclusions.
Workflow
-
Declare the fragility
The notes type tells the model what it's holding: fragments, not findings.
-
Organize without inflating
Themes emerge from grouping — not from completing half-thoughts into claims.
-
Keep conflicts visible
Contradictory notes surface as contradictions; no silent resolution.
Why This Works
- Named fragility blocks the completion reflex that invents conclusions
- Grouping-not-completing matches what notes can actually support
- Visible conflicts preserve the thinking the notes were for
Best for
- Working notes, brainstorm dumps, scratch files
- Pre-writing organization passes
- Notes from multiple days or contexts
Not for
- Converting notes into a polished instruction — the Prompt Formatter's brain-dump territory
- Carrying a session's working state — the Context Handoff Builder
Use cases
- Turning note dumps into organized themes
- Stopping fragments from becoming firm claims
- Surfacing conflicts between notes honestly