voc-synthesize

/voc-synthesize — Cross-Source Pattern Detection

One mention is an anecdote. Three mentions across three different channels is a pattern. That distinction is the entire product, and this skill is built so it cannot be quietly relaxed.

Clustering is a judgment task, so subagents do it. Counting is not, so code does it. The confirmation rule lives in scripts/synthesize.js reading config/thresholds.json, and nowhere else. If you find yourself reasoning about whether something "feels confirmed," you have left the rule behind.

Requires

What	Value
Input	outputs/voc/profiled/*.json, plus the call analysis and review briefs
Config	config/thresholds.json
Cost	Subagent tokens. Five clustering agents per run.

---

Phase 1 — Gather

Collect everything in the window (default from windows.default_days):

Source	Path
Profiled signals	outputs/voc/profiled/*.json
Call intelligence	outputs/calls/analysis/call-intelligence-*.md
Review briefs	outputs/voc/sources/reviews/brief-*.json
Chat, notes, CRM, surveys, tickets	outputs/voc/sources/<channel>/*

Do not read the quarantine folder. Tier-U signals are excluded by design.

Report which sources were empty. A source that returned nothing because its connector is broken looks identical to a source where nothing happened, and the difference matters — say which you believe it was and why.

---

Phase 2 — Cluster in parallel

Spawn one subagent per dimension, all in a single message:

pain · request · praise · objection · competitive

Each subagent receives the full corpus and returns clusters for its dimension only:

Group signals in the corpus below into themes for the "<dimension>" dimension.

Cluster on underlying meaning, not wording. "Export is slow", "downloads time out"
and "can't get data out for big events" are ONE theme. Err toward merging: two
themes that should have been one is a worse error than one theme that should have
been two, because splitting hides frequency.

Return ONLY this JSON:
{"clusters":[{
  "theme": "short specific name, written as the customer would recognize it",
  "dimension": "<dimension>",
  "signals": [{"channel":"...","weight_tier":"...","company":"...",
               "date":"YYYY-MM-DD","verbatim":"exact quote","source_file":"..."}]
}]}

Rules:
- Copy verbatim quotes EXACTLY. Do not clean up grammar or trim for length.
- Every signal keeps its original channel and weight_tier. Do not reassign them.
- Do not invent signals to strengthen a cluster.
- A signal may appear in only one cluster within your dimension.
- If a quote is ambiguous between two themes, put it in the more specific one.
CORPUS:
[...]