Briefly: a newsroom without a human editor
Briefly publishes digests on AI, software and security in English, Spanish, Russian and Portuguese. No person approves a post. A Writer agent drafts, a Reviewer agent checks every item against its sources, and Dagu runs each step as an idempotent job.
- Sources
- Writer
- Reviewer
- 4 languages
- Publish
Retries live outside the service
The service never retries on its own. Dagu re-runs a failed step, which is safe because every step is idempotent.
Decisions are in git
Every architectural decision is an ADR in the repository. People and agents read the same reasons.
How a mistake became a rule
- Symptom. One Portuguese edition took 15 Writer/Reviewer cycles across four runs.
- Data, not a guess. The review log showed the Reviewer rejecting ordinary loanwords like “offline” and “hub”, next to one real error — a professor turned into a researcher.
- Cause. Any style remark blocked publication, and a full rewrite fixed one complaint while breaking another item.
- Rule in the harness. Findings are now typed blocking or advisory. Only factual and fidelity errors block, and code, not the model, decides approval.
- Every next edition. The rule is an ADR and a response schema, so every later edition runs under it.
The fix went into the harness, not into one article.