Skip to main content
Yuzu generates buyer-facing material: recap scripts, emails, LinkedIn posts, business-case copy, titles, and summaries. Content quality is the system that keeps that output specific, useful, and less generic.

​
Model routing

Different tasks use different model tiers:
  • Opus for deeper agent work, long-context reasoning, email quality, and high-stakes judgment.
  • Sonnet for high-volume generation, summaries, emails, and business-copy drafting.
  • Haiku for fast classification, routing, dedupe, and other lightweight decisions.
The model registry gives Yuzu one place to route work and audit which model generated a result. Recent deal-agent and email-review work uses Opus 4.8 where the task needs stronger account reasoning. Recurring workspace memory and high-volume strategy drafting can still use lower-cost models when the task is narrower.

​
Judge passes

Some generated content can run through an LLM judge panel. Judges score the draft against a rubric and return concrete feedback. If the first draft is weak, Yuzu can revise once using the judge feedback, then compare the revision against the original. The system keeps the better version and avoids exposing judge language to buyers. Judge results are also useful for generated-asset review gates. A TLDR, business-case page, email, or LinkedIn post should not be treated as ready just because a background job produced bytes. The review state should reflect whether the asset passed generation, has review metadata, and is safe to expose to the seller for approval.

​
What judges look for

Rubrics vary by surface, but generally check:
  • Specificity to the buyer and deal
  • Clear next step
  • Factual grounding in available evidence
  • Avoidance of generic AI phrasing
  • Appropriate tone for a seller-authored artifact
  • No invented claims beyond the source context

​
What still needs human review

Judges are a quality gate, not legal or commercial approval. Review anything that mentions pricing, commitments, timelines, discounts, security, or customer claims before sending. For buyer-package assets, review is explicit. Sellers should open the TLDR, business-case page, email, or LinkedIn post and confirm the final artifact before sending or scheduling it, even when autopilot created the draft automatically.