Structural Patterns · Feb 2026 · v2.2
Semantic Patterns
Semantic patterns are reusable operator combinations that express specific
cognitive structures. Master these patterns, and you can construct
any complex idea as a readable, navigable structure.
01/Introduction
Foundation
=
A semantic pattern = a reusable operator
combination that expresses a cognitive structure.
Pattern Anatomy
=
Operator A
+
.
Operator B
=
→
Pattern
→
✓
Meaning
.
Why patterns matter:
+
Reduce cognitive load — readers recognize
patterns pre-attentively
+
Enable reuse — same pattern solves similar
problems
+
Create consistency — team shares a visual
language
02/Operator Matrix
Interactive Operator Grid
=
Equals
.
Dot
|
Pipe
@
At
!
Bang
?
Question
*
Star
→
Arrow
~
Tilde
+
Plus
-
Minus
✔
Check
03/Core Patterns
Interactive
=
Definition Chain: Claim → Refinement →
Nuance
Visual Flow
=
Main claim
↓
=
Refinement
↓
=
Nuance
Example
=
API
Design is about
predictability
=
Predictability means
consistent patterns
=
Consistent patterns
reduce cognitive load
*
Use when: Refining a concept from
abstract to concrete
=
Causal Chain: Cause → Effect →
Consequence
Visual Flow
!
Cause
→
→
Effect
→
→
Consequence
Example
!
Cache
invalidation bug
→
Users see stale data
→
Support tickets spike
→
Team diverted from
roadmap
*
Use when: Tracing causality through a
system
=
Trade-off Pattern: Pros (+) vs Cons (-)
→ Tension (~)
Visual Balance
+ Fast iteration
Ship features quickly
VS
- Technical debt
Pay later with interest
~
Tension: Speed vs Sustainability
CLN Syntax
+ Fast iteration — ship features quickly - Technical debt — pay later with interest ~ Tension: Speed vs Sustainability
*
Use when: Evaluating options, making
decisions
=
Evidence Tree: Claim (*) supported by
multiple evidence points
Tree Structure
=
Main
Claim
*
Evidence A
*
Evidence B
.
Detail for B
*
Evidence C
*
Use when: Building an argument,
supporting a thesis
=
Decision Flow: Question → Options →
Selection
Interactive Decision Tree
?
What
deployment strategy?
+
Blue-Green
+
Canary
+
Rolling
Update
SELECTED
*
Use when: Documenting decisions with
alternatives
04/Pattern Composition
=
Patterns compose: combine simple patterns to
build complex structures.
Composition Example: Definition + Evidence +
Trade-off
=
Microservices decompose systems
into services
*
Each service owns its data
*
Services communicate via APIs
+
Independent deployability
-
Operational complexity
~
Flexibility vs Complexity
.
Composition rules:
.
Each line participates in exactly one pattern
at its level
.
Nested lines form sub-patterns
.
Readers parse top-down, recognizing patterns as
they go
05/Anti-Patterns
Warnings
!
Anti-Pattern 1: Orphan Claims
— evidence without a claim
-
Problem: Reader asks "why does this
matter?"
!
Anti-Pattern 2: Mixed
Operators — inconsistent operators for
same semantic role
-
Problem: Reader can't build pattern
recognition
!
Anti-Pattern 3: Deep Nesting —
more than 4 levels
-
Problem: Cognitive overload, reader loses
context
+
Solution: Extract into new block or
document
06/Quick Reference
=
Definition
.
Action
*
Evidence
→
Result
!
Risk
+
Pro
-
Con
~
Tension
?
Unknown
Pattern Cheat Sheet
= → =
→ = Definition Chain
! →
→ → → Causal Chain
= *
* Evidence Tree
+ /
- ~ Trade-off
. . .
→ Action Sequence
?
. → Hypothesis Test
! .
→ Risk Mitigation
? +
+ → Decision Flow