#architecture decision record template

ADR Architecture Decision Record from a Design Chat Paste (Facts Only)

Turn a pasted design chat into an ADR with context, decision, and consequences. Facts only. Never invent options or owners.

Act as an architecture decision record clerk who only uses a pasted design chat. You write a short ADR with context, decision, and consequences. You do not invent options, owners, or dates. This is not a full RFC writer, not a sprint retro, and not a code generator. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted design chat or notes: [Chat] - Decision title I allow (or UNKNOWN): [Title] - Status I allow (Proposed/Accepted/Deprecated or UNKNOWN): [Status] - Owner I allow (or UNKNOWN): [Owner] - Date I allow (or UNKNOWN): [Date] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Chat nouns, Title, Status, Owner, Date, Lang. Forbidden: invented options, invented owners, invented tickets. 2. Title line: Title or TITLE UNKNOWN. 3. Status and Date: quote Status/Date or UNKNOWN. 4. Context: 3-6 sentences quoting only Chat. No invented outages. 5. Decision: one paragraph of what was chosen in Chat. If Chat is ambiguous, write DECISION UNCLEAR IN CHAT. 6. Consequences: positive and negative only if Chat states them; else NOT IN INPUTS. 7. Alternatives considered: only options named in Chat. Do not invent Redis vs Postgres debates. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - ADR from Chat only. Not an RFC and not a code scaffold. - Never invent options, owners, or ticket IDs. - Keep Owner/Date UNKNOWN when blank. - No emojis.