---
name: pattern-weaver
description: >
  Cross-product, cross-domain pattern recognition. What's working across multiple surfaces?
  What principle connects the successful products? What meta-capability is the system developing?
  Use when you need to zoom out from individual products and see the portfolio-level patterns.
metadata:
  author: nirav
  version: "1.0"
compatibility: Designed for Claude Code
allowed-tools: Read Write bash Glob Grep Agent
---

# Pattern Weaver — Seeing the Meta

Individual products are threads. The pattern-weaver sees the fabric.

When multiple products are in flight — some emerging, some surfaced, some evolving — the pattern-weaver looks for what connects them. Not just common features or shared capabilities, but **structural patterns** that reveal what the intelligence system is becoming.

## What to Look For

### Success Patterns

What do the successful products have in common?

- **Capability combinations** — Which domain pairings produce the best results repeatedly?
- **Constraint ratios** — Do successful seeds share similar constraint structures?
- **Feedback architectures** — What loop designs correlate with healthy evolution?
- **Interface choices** — Which paradigms work best for which types of intelligence?

### Failure Patterns

What do composted initiatives have in common?

- **Recurring kill criteria triggers** — Are we repeatedly failing for the same reason?
- **Capability gaps** — Do failures cluster around the same missing capability?
- **Timing patterns** — Are we consistently too early or too late?

### Meta-Capabilities

What can the SYSTEM do that no individual PRODUCT can?

- **Cross-product synthesis** — Insights from product A that illuminate product B
- **Compounding knowledge** — Each product making every other product smarter
- **Emergent portfolio effects** — The collection being worth more than the sum

### Synergies and Cannibalization

- **Synergies** — Products that make each other better (shared capabilities, complementary surfaces)
- **Cannibalization** — Products competing for the same user attention or capability
- **Gaps** — Spaces between products where a new surface should exist

## Process

1. **Read the portfolio** — initiative-tracker provides the current state of all initiatives
2. **Read evolution signals** — adaptation-observer outputs from each surfaced product
3. **Read the emergence log** — `loom-briefings/emergence-log.md` for cross-product emergence
4. **Cross-reference** — Look for patterns across all three data sources
5. **Synthesize** — Produce a pattern report

## Output

```markdown
# Pattern Report — {date}

## Success Patterns
{What connects the working products}

## Failure Patterns
{What connects the composted ones}

## Meta-Capability Developing
{What the system-as-a-whole is getting better at}

## Portfolio Synergies
{Products that enhance each other — and how to strengthen the connection}

## Portfolio Tensions
{Products competing or conflicting — and how to resolve}

## Recommended Actions
1. {Pattern-informed recommendation}
2. {Pattern-informed recommendation}
3. {Pattern-informed recommendation}
```

## Connection to The Loom Cycle

Pattern reports feed:
- **Sense** — Patterns reveal where to look next
- **Envision** — Meta-capabilities suggest new product visions
- **Synthesize/narrative-keeper** — Patterns ARE the evolving story
- **Weekly Product Synthesis** — Pattern reports are a core input to the briefing