---
title: DARO-01 — AI Technical Writer
slug: daro
role: AI Technical Writer
function: Operations
seniority: Mid
verticals:
  - "SaaS"
  - "B2B"
tier: professional
monthlyPrice: $500/month
publishedAt: "2026-05-04T00:00:00Z"
canonical: "https://fidelic.ai/agents/daro"
---

# DARO-01 — AI Technical Writer

*Docs that ship with the release*

Drafts API docs, internal runbooks, onboarding guides, and the changelog for product teams that ship faster than they document.

## Capabilities

- Drafts API reference docs from the actual code, the spec, and the changelog — not from invented behavior
- Maintains internal runbooks: deployment steps, on-call procedures, incident playbooks, posted in the team’s wiki and updated when the underlying process changes
- Writes onboarding guides for new hires that mirror how the team actually works — sourced from real Slack threads, real PRs, real recent decisions
- Drafts the changelog and release notes for every shipped release; flags items the human writer should turn into a longer post
- Routes any user-facing copy decision (marketing register, brand voice, public framing) to a human reviewer before publication

## The edge

DARO distinguishes between docs that describe what the code does and docs that describe what the team meant the code to do. Most doc agents do the first. The second is where docs earn their keep. DARO drafts both — and flags every divergence between the two for the human reviewer.

## The hook

Your engineering team ships releases on Friday. The doc page updates Friday afternoon, drafted from the merged PRs and the spec, ready for a human pass before Monday. The hour the senior engineer used to spend translating their own work into prose goes back into the work itself.

## Evidence

- Built on the Fidelic AI EvalOps test suite — doc-fidelity tests gate every release (claims-vs-source agreement, citation accuracy)
- Sandboxed deployment in Anthropic-managed infrastructure; no data leaves the bounded environment without explicit egress config
- Pre-launch. Public beta planned for Q3 2026.

## Worst-case behavior

Defers to the human reviewer when the spec or code is ambiguous. Failure mode is producing a doc that says “this function does X according to the spec; the implementation may differ — the human author should verify line 47 of the file” rather than guessing.

## Day 1 / Week 1 / Month 1

- **Day 1:** Reads the existing docs, the API reference, the changelog, the spec repo, the team’s recent PRs, and the support-ticket history. First clarifying questions on doc voice, scope, and review thresholds land in DMs.
- **Week 1:** First doc page ships under review on a real release. Human writer signs off; DARO calibrates the threshold for “flagged for human attention” vs autonomous.
- **Month 1:** Doc cadence is stable across the release calendar. Internal runbook coverage measurable. The 30-day success metric — no release without an updated doc page — has its first reading.

## 90-day success criterion

By day 30, no release ships without an updated doc page — drafted, reviewed, and posted before the release notes go public.

## Resume

**Background.** DARO-01 is a Fidelic AI Professional-tier template configured for technical writing in product teams. Claude-native, isolated Anthropic project per customer. Configuration agent steward is itself trained on doc-fidelity patterns and the four-tier authority model.

**Methodology.**
- Trigger taxonomy: PR merge events, spec changes, changelog entries, support tickets that recur, runbook drift signals
- Four-tier constitution gating every action; review-required state on all public-facing docs
- EvalOps test suite (doc-fidelity tests, claim-vs-source agreement, citation accuracy) gating every release
- Doc-voice calibration cycle: human writer edits early drafts; DARO learns the team’s voice from the edits

**Evals.** Pre-deployment red-team only. Doc-fidelity benchmarks pending public-beta close.

**Operating record.** Pre-launch. Public beta planned for Q3 2026.

**Lineage.** Fidelic AI template informed by senior technical-writing practice; no single practitioners. Future Expert-tier variants may be formed from practitioners (see Marketplace).

## Compatible agents

- [ZADO-01 — AI Knowledge Curator](https://fidelic.ai/agents/zado) — Cited Slack answers
- [DRYN-01 — AI Data Analyst](https://fidelic.ai/agents/dryn) — Recurring analyses, dashboard maintenance, anomaly watch
- [SYRA-01 — AI SEO Strategist](https://fidelic.ai/agents/syra) — Search intent first, volume second

## Related honest questions

- [What do I actually own if I cancel my AI agent tomorrow?](https://fidelic.ai/hard-questions/what-do-i-own-if-i-cancel)
- [Is Fidelic just a wrapper around GPT?](https://fidelic.ai/hard-questions/wrapper-around-gpt)
- [What if the AI hallucinates and says something wrong?](https://fidelic.ai/hard-questions/ai-hallucination-explained)

---
Canonical: https://fidelic.ai/agents/daro