#

The Connector.

The Hash Operator creates structure out of chaos. It is the taxonomy engine that turns linear text into a queryable network.

The Semantic Glue

Definition

=Operator: # (Hash/Tag) .Function: Categorization, Filtering, Cross-referencing. .Scope: Applies to the specific line it resides on. →Result: Enables "Query > Retrieve" workflows.

The Taxonomy Effect

Without tags, a note is an island. With tags, it is part of an archipelago.

#project-alpha #q3-planning #backend #api #urgent #design-debt #hiring #marketing

Unstructured vs. Tagged

Prose requires you to read to understand the category. Tags allow you to filter *before* reading.

Without Tags

"We need to fix the login bug that is preventing users from accessing their dashboard. Also, the API response time is slow."

⚠ Issue: Is this a UI bug? Backend issue? Performance issue? You have to parse the English to find out.
With CLN Tags .Fix login bug for dashboard access#auth#bug .Optimize API response time #backend#perf
✓ Instantly categorizable. Searchable. Filterable.

Syntax Conventions

To ensure the parser and your future self can read the tags, follow these rules.

// Rule 01: Kebab-Case +#user-onboarding +#api-v2 -#UserOnboarding -#user onboarding // Rule 02: Singular vs Plural +#bug +#feature *Tip: Prefer singular for easier filtering (matches 'bug' and 'bugs'). // Rule 03: Scope Context =Global tags: #project-name, #team, #priority =Local tags: #css, #db-query, #specific-component

Artifact: The Filtered View

Imagine you query your entire knowledge base for #urgent. This is what you see.

Query Results

Filter: #urgent
3 items found
.Roll back API deployment #urgent#backend !Breaking change in payment gateway .Renew SSL certificate for prod #urgent#devops @expires in 12 hours .Reply to security audit request #urgent#legal @due: EOD