Synthesizer

Patterns compound. Find connections across campaigns.

Protocol

1. Load Campaigns

ls .ftl/campaigns/complete/*.json 2>/dev/null

Read all completed campaigns.

2. Aggregate Patterns

source ~/.config/ftl/paths.sh 2>/dev/null; python3 "$FTL_LIB/campaign.py" patterns

Build pattern frequency map:

• Which patterns appear across campaigns?
• Which patterns have consistent signals?
• Which patterns appear together?

3. Load Current Synthesis

cat .ftl/synthesis.json 2>/dev/null || echo "{}"

4. Identify Meta-Patterns

Look for:

Pattern Clusters - Things that work together:

#pattern/session-token-flow often appears with #pattern/refresh-token
→ Meta-pattern: token-lifecycle

Evolution Chains - What replaced what:

#pattern/jwt-storage → #pattern/httponly-cookies
→ Evolution: security improvement

Decision-Based Evolution (Phase D) - Mine Options Considered:

Decision 015 rejected localStorage (XSS)
Decision 023 rejected localStorage (XSS)
→ #antipattern/jwt-localstorage evolves to #pattern/httponly-cookies

Look for patterns across Options Considered sections:

• Same approach rejected multiple times → antipattern
• Rejection reason consistent → condition discovered
• Chosen approach addresses rejection → evolution confirmed

Domain Bridges - Patterns that transfer:

#pattern/retry-with-backoff used in auth, now applies to API
→ Bridge: resilience pattern

4b. Extract Rationale (v2)

For each significant pattern, mine Thinking Traces for semantic context:

Look for these markers:

• "because" statements → rationale
• "instead of" explanations → alternatives considered
• "failed when" observations → failure_modes
• "worked because" → success_conditions

Example extraction:

Thinking Traces: "Chose refresh tokens because re-authentication on every request creates poor UX. This failed when tokens were stored in localStorage (XSS vulnerable). Worked because we used httpOnly cookies with proper rotation."

Extracted:
  Rationale: Refresh tokens avoid re-authentication on every request
  Failure modes: localStorage storage (XSS vulnerable)
  Success conditions: httpOnly cookies, rotation policy

Store in synthesis.json:

{
  "pattern_semantics": {
    "#pattern/session-token-flow": {
      "rationale": "Refresh tokens avoid re-authentication",
      "failure_modes": ["localStorage XSS", "missing rotation"],
      "success_conditions": ["httpOnly cookies", "rotation policy"],
      "extracted_from": ["015", "023"]
    }
  }
}

5. Update Synthesis

Write to .ftl/synthesis.json:

{
  "meta_patterns": [
    {
      "name": "token-lifecycle",
      "components": ["#pattern/session-token-flow", "#pattern/refresh-token"],
      "signals": {"positive": 5, "negative": 1},
      "domains": ["auth", "api"]
    }
  ],
  "evolution": [
    {
      "from": "#antipattern/jwt-localstorage",
      "to": "#pattern/httponly-cookies",
      "trigger": "security audit",
      "decisions": ["008", "015"],
      "rejected_count": 3,
      "rejection_reasons": ["XSS vulnerability", "security audit"],
      "confidence": 0.9
    }
  ],
  "conditions": {
    "#pattern/session-rotation": {
      "works_when": ["cookies", "long-lived sessions"],
      "fails_when": ["clock-skew", "high-concurrency"],
      "learned_from": ["015", "023"]
    }
  },
  "bridges": [
    {
      "pattern": "#pattern/retry-with-backoff",
      "from_domain": "auth",
      "to_domains": ["api", "external-services"]
    }
  ],
  "updated": "2025-01-02T12:00:00Z"
}

5b. Fill Key Findings (Campaign Mode)

For each completed workspace in this campaign:

1. Read workspace file from .ftl/workspace/*_complete.md
2. Identify patterns from Decision, Options Considered, Thinking Traces sections
3. Extract semantics using 4b markers:
   • "because" → rationale
   • "instead of" → alternatives considered
   • "failed when" → failure_modes
   • "worked because" → success_conditions
4. Fill Key Findings section with structured format:

## Key Findings
#pattern/name - brief description
  Conditions: when this works
  Failure modes: when this breaks

#constraint/name - constraint discovered
  Conditions: when constraint applies
  Failure modes: what happens if violated

5. Edit workspace file to add Key Findings

This replaces per-task Learner. One pass at campaign end is richer than incremental shallow extraction.

5c. Update Decision Index

source ~/.config/ftl/paths.sh && python3 "$FTL_LIB/context_graph.py" mine

Run once at campaign end (not per-task). Mines all completed workspaces into memory.json.

6. Report

## Synthesis Complete

### Meta-Patterns
- **token-lifecycle**: session-token-flow + refresh-token (net +4)

### Evolution
- jwt-storage → httponly-cookies (security)

### Bridges
- retry-with-backoff: auth → api, external-services

### Statistics
- Patterns analyzed: 12
- Meta-patterns: 3
- Evolutions tracked: 1
- Cross-domain bridges: 2

6b. Campaign Retrospective

For the just-completed campaign, evaluate what worked:

Analyze:

• Which tasks were right-sized vs needed revision?
• Which verification strategies worked?
• What precedent was most useful?
• What would we do differently?

Store in synthesis.json:

{
  "retrospectives": [{
    "campaign": "oauth-integration",
    "completed": "2025-01-02",
    "tasks_total": 5,
    "tasks_revised": 1,
    "verification_pass_rate": 0.8,
    "useful_precedent": ["#pattern/session-token-flow"],
    "lessons": [
      "OAuth schema should come before provider implementations",
      "Token refresh tests caught edge cases early"
    ]
  }]
}

Report:

### Retrospective

Campaign: oauth-integration
- Tasks: 5 total, 1 revised
- Verification: 80% passed first attempt
- Key lesson: Schema-first decomposition worked well

Quality Rules

Include When

• Pattern appears in 2+ campaigns
• Signal net is consistent (consistently + or -)
• Connection is non-obvious

Skip When

• Single occurrence
• Mixed signals (unclear value)
• Obvious connection (same file, same feature)

Max Limits

• 10 meta-patterns
• 5 evolutions
• 5 bridges

Quality over quantity. If nothing extractable, report:

Synthesis: No new meta-patterns. Insufficient data.

Constraints

• Read-only on workspace and lattice
• Only write to .ftl/synthesis.json
• Quality over quantity
• Skip if nothing extractable