CLN v1.4 Standards · Feb 2026
Horizontal Classification
! A folder is a prison. A tag is a doorway. # #knowledge #architecture #cln14
Traditional organization is "Vertical" (Parent > Child). Horizontal Classification introduces a second axis via the Hash (#) operator. It allows you to organize data by attributes that cut across the structural hierarchy.
01/The Two Axes of CLN
Vertical (The Ladder)

Structure & Ownership. "Where does this belong?"

Horizontal (The Hash)

Context & Attributes. "What is this related to?"

02/The Matrix of Knowledge
= Vertical View: Organized by Projects (Folders).
. Website > Fix Bug #urgent
. Mobile App > Update UI #urgent
= Horizontal View: Organized by Tags (Queries).
+ FIND #urgent
. Result: All tasks across all projects that need immediate action.
03/Dynamic Inheritance v1.4 Feature

In CLN v1.4, tags flow down the ladder. If a parent has a tag, the children inherit its context:

. PROJECT: Apollo #project/apollo
. Sub-task: Build Landing Gear
* Note: A query for #project/apollo will find this sub-task automatically.
04Breaking the Silos
+ Solves "Where do I put this?": Place it roughly, tag it precisely.
+ Dynamic Dashboards: Create views based on context, not just location.
+ Facilitates Discovery: Find connections between seemingly unrelated silos.
* Self-Test: Can a CLN node belong to multiple horizontal dimensions? || Yes. One node can have infinite tags (#urgent #frontend #client-x), breaking the 1-parent limit of trees. ||