abcd decide writes an ADR as proposed, and its help says the status stays proposed until the author sets accepted, but no verb sets it: accepting a decision means hand-editing status:, and nothing records who accepted it or when. A downstream project accepting its first decisions did exactly that.

Frontmatter

.abcd/work/issues/open/iss-2610040758569116-abcd-decide-writes-an-adr-as-proposed.md
open on GitHub ↗ · commit history ↗

mentions1

• dcn-26100900000000012026-10-09 — Rulings of the product thinker on the three hand-backs of the 2026-10-07/08 autonomous drain (asked by abcd-0b, one question at a time, answers verbatim): (1) iss-2609251618079479, whether the build-sequence chapter's build-milestone sense retires with the phase: "Rewrite in today's terms" — 06-delivery/01-build-sequence.md stays a current chapter, its build order restated as dependencies with no milestones (neither retired as history nor kept as a second sense of the word). (2) iss-2610040758569116, whether an agent may run 'abcd decide accept', which stamps the person's git name as accepted_by: "Agents too, disclosed" — no guard block as for 'source ledger --flip'; the commit's Assisted-by trailer is the disclosure. (3) iss-2610030956156354's open design point, whether a step still falls back to the agent harness when the size count already sent the brief to the person's own model server and the chat call then fails: "Move to the harness" — no answer received is the trigger, not nothing sent; recorded as iss-2610090701491123, since the resolved fix stops instead.