CLN Wiki · Practice
CLN Wiki TERM
= personal knowledge base built in CLN format @ 2026 · CLN lexicon
Double-click any line to anchor. Select + Right-click to tagmarry or record a decision. Traces persist in the sidebar.
01// Definition Term
// ##def · What is a CLN Wiki =CLN Wiki — a personal knowledge base where every entry is a CLN document: structured, scannable, reusable =not a filing system — a thinking system =entries link to each other via »[text]##id cross-references // ##def-core · The core distinction *prose wiki — captures what you read →CLN wiki — captures what you decided, noticed, questioned →operator column = cognitive fingerprint of how you processed information
02// Why CLN for a personal wiki Why
// ##why-compare · vs prose-based wikis +scan a 3-month-old entry in 10 seconds — operator column tells you the shape +copy any block into a doc, prompt, or email — no reformatting +AI can parse and extend CLN entries directly — no translation layer +writing forces decomposition — choosing ! vs . vs ? is an act of thinking -no narrative flow — wrong format for stories, reflections, essays !CLN wiki ≠ diary — use prose separately for emotional processing // ##why-memory · Memory mechanics .writing a block = episodic event — you remember the act of structuring .block title = semantic anchor — activates schema on re-read .block number = spatial anchor — place cell fires for position in document *→ see Block Annotations Memory for full mechanism
03// Wiki page anatomy Structure
// ##anatomy-layers · Four layers of every entry =Layer 1 — header: = TOPIC: Title — names the entry, sets schema =Layer 2 — block annotations: // NN · Name — segment into cognitive chunks =Layer 3 — operator lines — one fact per line, semantic type explicit =Layer 4 — cross-links: »[text]##id — connects to other entries
Layer
L1Header
L2Blocks
L3Lines
L4Links
Example
= TOPIC: AWS Migration
// 01 · Risk Register
! data residency — GDPR blocker
»[GDPR Guide]##gdpr-entry
// ##anatomy-rules · Naming rules .entry title: unique, schema-activating — not Notes, not Stuff .block titles: 4–8 per page max — beyond that, spatial map saturates .block numbers: stable — don't renumber without reason !generic titles destroy recall — // 03 · Notes leaves no memory trace
04// Entry types Practice
📚
Book / Article Summary

Core thesis, main points, pros/cons, risks, metadata. Reusable as AI context.

= . + - ! @
⚡
Decision Log

What was decided, why, risks, open questions. The reasoning, not just the outcome.

= + - ! → ?
🔬
Concept Entry

Definition, mechanism, examples, where it applies. Like this page — a wiki term.

= . * ! →
🗺
Project Map

Context, phases, risks, open questions, stakeholders. One block = one phase.

= . ! ? @
05// Live builder — write your first entry Interactive
.type your entry below — preview updates in real time .click operator buttons to insert at cursor .Copy button — paste into any text field, Notion, VS Code, Telegram
CLN Entry Builder
Preview appears here…
06// Cross-linking entries Practice
// ##link-syntax · Link syntax =format: »[display text]##entry-id =entry-id = page filename without .html *example: »[GDPR Compliance]##gdpr-entry *example: »[see risk matrix]##aws-migration#risks — deep link to block // ##link-when · When to link .link when you reference a concept that has its own entry .link when a decision depends on another decision .link when a risk is already analyzed elsewhere !don't link for the sake of linking — every link = cognitive load →rule: link when the target entry adds non-obvious context
07// Maintenance patterns Practice
// ##maint-rhythm · Weekly rhythm .weekly: scan all ? lines — resolved questions → convert to = .weekly: scan all . lines — completed actions → mark ✔ or delete .monthly: scan ! lines — risks changed? update or remove .quarterly: prune entries not accessed — dead pages add noise // ##maint-tagmarry · Tagmarry as maintenance tool →re-read old entry → tagmarry lines that still matter →your tag list = snapshot of what currently matters to you *tags shift over time — compare tags from 3 months ago vs now →entries nobody tagmarries → candidates for deletion *→ see Tagmarry for full mechanism
08// Anti-patterns Watch out
// ##antipatterns · The five traps !Dump trap — copy-paste without structuring → no episodic trace, no recall →fix: write each line yourself, even if source is copy-pasted !Decoration trap — operators chosen for style, not semantics →fix: always ask "what cognitive role is this line?" before choosing operator !Graveyard trap — entries created, never revisited →fix: link every new entry to at least one existing entry on creation !Over-structuring trap — 15+ blocks per page, micro-entries for every thought →fix: 4–8 blocks per page, merge micro-entries into parent topics !Diary trap — CLN for emotional processing, reflection, venting →fix: use prose for emotional content — CLN is for structured knowledge
⚓Anchor line
#Tagmarry…
~Record decision…
Tagmarry — name this line
key-insight action risk revisit quote
Record a decision