Which perceptual channel best encodes asymmetric directionality (source→target) while remaining invariant to view orientation and scale? (a sub-question that arises while solving: What is the best way to display concept mapping and diagram trees in this app (a software application) for the concepts being shown?)

# Analysis of Perceptual Channels for Asymmetric Directionality

## Direct Answer

Motion is the best channel for showing direction without losing orientation or scale. Hue progression is the next best static option.

---

## Ranked Perceptual Channels

| Channel | Directionality Encoding | Orientation Invariant? | Scale Invariant? | Notes | |---------|-----|------------------------|-----|-----| | **Motion/Flow** | Direction of motion (source→target) | ✓ Yes | ✓ Yes | Strongest; works at all zoom levels; no geometric dependency | | **Hue Gradient** | Color shift warm→cool (or custom) | ✓ Yes | ✓ Yes | Static alternative; works perceptually across zoom; unambiguous | | **Arrowheads** | Triangle/chevron point direction | ✗ **TENSION** | ✗ **TENSION** | Fine details disappear at extreme zoom-out; breaks scale invariance | | **Line Weight** | Thickness increase source→target | ⚠ Partial | ⚠ Partial | Orientation-invariant but requires consistent scaling logic | | **Dash Pattern** | Dashes progress directionally | ⚠ Partial | ✗ No | Scale-dependent; dashes compress illegibly |

---

## ⚠️ FLAGGED CONTRADICTION

Arrowheads break your invariance rule. At extreme zoom-out, like concept maps with 50+ nodes, the geometry becomes sub-pixel. Perceptual salience degrades before the scale transformation even matters.

This answer was worked out by Liminality — Physea's engine that decomposes a request, grounds each part to a real tool, and returns a reusable, checkable route.

Connect it over MCP: https://mcp.physea.ai/mcp · physea.ai