Record an architecture decision

Capture what was decided while the evidence is still in this conversation, then write it only after the developer approves the exact bytes.

$ARGUMENTS is an optional hint, e.g. /adr we chose Riverpod over Bloc. Treat it as evidence only for what it literally says. It never supplies a reason that was not stated.

The one rule

Never invent rationale. Code shows what was built; only the developer can say why. If a material claim cannot be traced to something the developer said or confirmed, drop the claim — or cancel the record. A missing ADR costs a conversation. A confidently wrong ADR becomes architectural law.

"No ADR needed" is a normal, successful outcome. Say it plainly and stop.