TOPIC: Example indentation levels = Level 1 — this is the context @ Level 2 — subordinate metadata . Level 1 — action step | Level 2 — tool for this step ! Level 2 — risk belonging to this step → Level 3 — consequence of the risk

. Write API integration tests #backend ##api-tests ☐ ↑ ↑ ↑ ↑ ↑ Slot 1 Slot 2 Slot 3 Slot 4 Slot 5

? Self-Test: what kills a good note? || Ambiguity. No operator = no meaning. || = Rule: one fact per line || violating this creates cognitive debt ||

// ##arch 01 · Architecture = client-server, React + Go ##arch-decision // ##risks 02 · Risks ! latency spike — see »[architecture decision]##arch-decision !! . blocked by »[auth task]##auth-task ☐

TOPIC: Architecture choice ( = Option A — Monolith + fast start - hard to scale ) ( = Option B — Microservices + flexible - high overhead )

((( Algorithm | Best | Average | Worst | Stable ))) (( Quick Sort | O(n log n) | O(n log n) | O(n²) | No )) (( Merge Sort | O(n log n) | O(n log n) | O(n log n) | Yes )) (( Heap Sort | O(n log n) | O(n log n) | O(n log n) | No )) (( Bubble Sort | O(n) | O(n²) | O(n²) | Yes )) * Tim Sort (hybrid) is default in Python and Java ! Quick Sort worst case triggered by sorted input without randomised pivot ? Which is the only stable O(n log n) sort? || Merge Sort — guarantees stability without extra cost ||

Step 1 Line matches /^\s*\(\(\((.+)\)\)\)\s*$/ → header row strip outer ((( ))) · split on unescaped | each segment → <th>, trimmed Step 2 Line matches /^\s*\(\((.+)\)\)\s*$/ → data row strip outer (( )) · split on unescaped | each segment → <td>, trimmed empty segment (whitespace only) → <td class="cln-td-empty"> Step 3 Consecutive rows at same indent → one <table> first ((())), found → opens <thead>, then <tbody> if no ((())) before first (()) → open <tbody> immediately Step 4 First non-table line at same/lower indent → close </table> Step 5 Column count = len(header) if header present, else max(row widths) short row → append <td class="cln-td-empty"> to fill long row → truncate + emit [TABLE:OVERFLOW row N] Step 6 Inside cells: || text || → <span class="cln-spoiler"> »[t]##id → <a href="#id" class="cln-ref"> \| → literal pipe character

. validate config | format: json ─── { "source": "database", "flags": ["debug", "!important"] } ─── ! check for missing required keys

TOPIC: Title goes here = definition or essence #domain @ status: active . action step one #tag ##step-one ☐ | tool: something . depends on »[step one]##step-one ☐ + advantage ✔ confirmed - disadvantage ! risk !! ~ unresolved tension * Self-Test: main risk? || see ! line above || ( = option A + fast ) ( = option B + reliable ) ((( Metric | Option A | Option B ))) (( Speed | fast | slow )) (( Memory | O(1) | O(n) )) (( Stable | No | Yes ))

SUMMARY: [Title] = core definition / thesis (1–2 lines max) = key insight or takeaway . main point 1 * supporting detail . main point 2 | tools / methods / resources involved + strengths / advantages - weaknesses / limitations ! risks / warnings / common mistakes @ domain: field of application @ source: origin / author / year

MDA: [Topic] — depth [N] ⟶ ##first First-Order . Dimension: [AREA 1] = description + strength - weakness ⟶ ##second Second-Order . Effect: consequence of »[First Order]##first * explanation ⟶ ##third Third-Order Cascade . Cascade: emergent system effect = description * implication ⟶ ##foresight Foresight . Strategic direction ~ tension that drives the cascade

You are a CLN engine. CLN = Cognitive Ladder Notation v2.8. OUTPUT RULES: 1. Wrap every response in ```cln ... ``` (fenced code block, tag "cln"). 2. No text outside the code block. 3. Use operators: = . | @ ! ? * → ~ + - 4. 4-space indentation per level. 5. One fact per line. Max ~80 chars per line (not strict for URLs/code fences). 6. No fabricated URLs. No citation markers ([1], :contentReference). Internal links: »[text]##id only. 7. Use ─── for raw code/data embedding. 8. Use ⟶ for sequential phases and MDA depth levels. 9. Use tables ((( ))) / (( )) for fixed-column data. 10. Use ( ) blocks for parallel alternatives. 11. Use || text || for inline spoilers. 12. Inline formatting mid-line only: **bold** *italic* `code` ~~strike~~ $math$ ==mark== 13. Read %directives before generating. %alias expands first. %reality:off = fiction mode. 14. >> sections are visual containers. %presentation:true = slide mode. Spec: https://cognitiveladder.com/CLN-Spec-v2_8.md

Always respond in CLN (Cognitive Ladder Notation) v2.8 format. Wrap every response in ```cln ... ```. No prose outside the block. Operators: = . | @ ! ? * → ~ + - | 4-space indent | one fact per line. Lines ≤ 80 chars. Split long lines via indentation, not paraphrase. No fabricated URLs. No [cite] or :contentReference markers. Internal links: »[text]##id only. Real URLs only when explicitly asked. Use ─── for code fences. Use ⟶ for phases/MDA. Use ((( ))) for tables. Inline fmt mid-line only: **bold** *italic* `code` ~~strike~~ ==mark== Read %directives first. >> sections = visual containers. Spec: https://cognitiveladder.com/CLN-Spec-v2_8.md

[CLN MODE] Respond in Cognitive Ladder Notation v2.8. Wrap in ```cln```. One fact per line. 4-space indent. Max ~80 chars. Operators: = . | @ ! ? * → ~ + - No fake URLs. No citation markers. Internal refs: »##id. Use ─── for code. Use ⟶ for phases. Use ((( ))) for tables. Inline fmt mid-line: **bold** *italic* `code` ~~strike~~ ==mark==

A1sLadder → CLN → Chainalyst Code formatting → Universal notation → Analytical engine

>> ##anchor Section Title | bg:color border:color accent:color width:N collapse:true = content inside the visual section ! risks inside . actions inside

>> ##risks Project Risks | bg:#1a0a0a accent:#d4654a collapse:true ! no fallback if API goes down !! ! deadline: 2026-03-15 is fixed !! >> ##kpis Q1 Metrics | viz:bar = revenue: 120 000 = users: 8 400 = NPS: 72

TOPIC: Project Status = **CLN** is a plain-text notation — *semantic*, not just visual = install with: `npm install cln-parser` = deprecated: ~~use prose notes~~ · replaced by CLN operators = energy: $E = mc^2$ (Einstein · 1905) = see:  = ==critical deadline== — review before merge !! ! **never** push to main directly !! * see OWASP: `A03:2021 — Injection` . run `npm test` before committing ☐