Skip to content

Add lightweight final verification after draft generation #47

@terisuke

Description

@terisuke

Context

The current workflow generates the final draft with the heavy draft model and runs mechanical style evaluation. We should add a lightweight model review before returning the final output.

Scope

  • Add a final verification step after draft generation and style evaluation.
  • Default model split:
    • style/source summarization: gemma4:e2b
    • follow-up questions: qwen3.6:27b
    • final Japanese draft: gemma4:31b
    • final verification: gemma4:latest
  • Verify draft consistency against the article brief, writing style guide, output format rules, and unsupported factual claims.
  • Surface PASS/NEEDS_REVIEW and concrete findings in API/UI/scenario output.
  • Keep automatic rewrite from verification feedback out of scope until draft versioning and section regeneration are in place.

Acceptance

  • /api/drafts returns verification metadata.
  • SSE draft generation emits a verification status before result.
  • UI displays final verification separately from mechanical style score.
  • Scenario output writes verification.json and prints verification status.
  • ADR/docs/env examples describe the new verification step.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions