CLN Wiki · CLN Practice
The Markdown Trap
Markdown needs a renderer. CLN needs your eyes.
01
/
Definition
Analysis
=
Markdown — visual markup for rendered documents
=
CLN — cognitive notation for raw-text environments
Markdown renders beautifully in GitHub, Notion, Obsidian. But open a Markdown file in
an email, Slack, or terminal? ## **Important**: See [this](https://...) is
machine-readable, not human-readable. CLN is designed to be read raw. No renderer.
No preview pane. Just text.
02
/
Rendering Dependency
Comparison
-
Markdown raw: `## **Title**` — visual noise
+
CLN raw:
= Title — immediately readable
-
Markdown in Slack: renders inconsistently
+
CLN in Slack: works perfectly (it's just text)
-
Markdown in email: doesn't render at all
+
CLN in email: reads exactly as intended
03
/
Semantic Typing
Core Difference
-
Markdown:
- item — WHAT is this item? task? fact? risk?
+
CLN: operator tells you WHAT before you read the text
04
/
Use Both
Resolution
=
USE BOTH — they solve different problems
*
Markdown for: docs, READMEs, rendered content
*
CLN for: thinking, analysis, notes, prompts, communication
!
they solve different problems — don't mix roles
05
/
The Portability Test
Test
Copy your notes. Paste into each environment below. If they still make sense — they're portable.
CLN — passes all
✓ Slack
✓ Email
✓ Terminal
✓ Text file
✓ AI chat
✓ Printed page
Markdown — fails raw environments
Slack
Email
Terminal
✓ GitHub
✓ Obsidian
✓ Notion
Markdown is for documents. CLN is for thinking.