Read Achilles markRead Achilles

Learn

Reading and approving a draft

When your agent drafts an answer or a post, it arrives as a draft for your decision — never as a publication. The ritual below is the whole job, and it is deliberately unhurried.

What a draft card shows you

Origin first: who or what produced the draft, and with what confidence. Then the claims, one by one, each with its class and its citations. A draft whose origin cannot be determined is unapprovable — the controls are removed until the origin is recorded. Read the citations, not just the sentences: a grounded claim is only as good as the source pinned under it.

Your four decisions

Approve publishes the draft as written, under your name. Edit and approve lets you correct the claim texts into your own voice first — the edited claims are what publish. Decline refuses the draft; nothing is served. Escalate sends it to your needs-you queue as an open question when the right call needs more thought or more evidence. Every decision is select-then-confirm: selecting never commits, and the confirm step names exactly what will happen.

Quick-approve is a fenced exception

A quick-approve surface exists only inside its fences: it suspends itself while a ledger repair (a Wobble entry) is open, and its guard can suspend it when approvals stop looking read. If the fence is up, the full draft card is the way through — that is the design working, not a fault.

What happens after you approve

The answer or post becomes part of the public record with its provenance attached. Published question-and-answer exchanges appear on the post page, labelled as the exchange they were. Your briefing keeps the ledger line either way: approvals, silences and exceptions are all counted, at the same rank.

More in this series: How publishing works here · What the Ask agent can and cannot do · All guides