description:Create a GEWU comparison, brief or synthesis from accepted revision-bound inputs, preserving conditions, disagreement and dependencies before any requested MCP submission.
---
# Synthesize evidence
Read the pack's [evidence](../../protocols/EVIDENCE.md), [scope](../../protocols/SCOPE.md) and [contribution](../../protocols/CONTRIBUTIONS.md) protocols, then use the [synthesis pipeline](../../pipelines/synthesize.md).
Identify audience, purpose, scope and requested output. Retrieve accepted input revisions and build a dependency inventory. Compare conditions, methods, observations and limitations before composing. Label new interpretation and cite the accepted records it depends on. Preserve contradictory evidence and unknown values.
For comparison requests, use a compact matrix when it makes differences easier to inspect. Choose columns that fit the evidence, such as method, population or sample, conditions, findings and limitations. Cite each cell to the accepted record and source revision that supports it. Mark unavailable values as unknown; do not infer or fill them from memory. Follow the matrix with a short account of agreement, disagreement and evidence gaps when useful.
Audit factual statements and dates against the dependency inventory before delivery. For each material factual statement, classify its support as supported, partially supported, unsupported or conflicting, and keep its citation beside it. Check that citations support the statement as written and retain the required source locations and warnings; do not treat a citation's presence as proof. Keep interpretations distinct from retrieved claims and cite the records they depend on. Unsupported or conflicting statements must be qualified, removed, or reported as open questions rather than presented as established findings. If an input revision changes, recheck affected statements. A draft may be written locally when requested; do not report it as saved GEWU knowledge. Submit a synthesis proposal only when the user requested a knowledge contribution and the service exposes a compatible synthesis contract.
Return the artifact, dependency inventory, limitations and receipt if accepted. If synthesis submission is unavailable, keep the draft and identify that exact missing capability. The skill does not add a server-side reasoning agent or website authoring path.
