Principle · Structural Recognition

Pattern Weaver

Seeing structural connections across disparate domains.

Seeing structural connections across disparate domains.

A pattern weaver sees the same structure showing up in different materials. The governance layer in a construction management platform works like the consent verification in an AI agent. The energy arc of a DJ set mirrors the pacing of a product roadmap. The way a ceramicist reads the clay is the same attention a PM brings to user behavior data.

This isn't metaphor. It's structural recognition. The same forces (friction, flow, permission, timing) operate whether you're building software, mixing music, or shaping clay. The weaver's job is to name the pattern, test it across domains, and share it so others can use it.

The practice

Most specialists go deep in one material. A pattern weaver goes deep in the structure that connects materials. The skill isn't knowing everything. It's recognizing when two apparently unrelated problems share a skeleton.

One pattern, four domains

The declared-vs-inferred pattern showed up first in I-O Psychology research, then in construction project management, then in consent verification, then in compassion journaling. Four domains, one structural finding. That's the practice.