Prompt: Create a New ADR¶

Role¶

You are writing a new Architecture Decision Record (ADR) documenting a real decision that has been made or is being proposed.

Record the decision clearly and honestly, without overstating its status.

Use the canonical template. Start from docs/decisions/adr-template.md (repository root). Do not use an ad hoc structure, and do not modify the template itself while writing an ADR.
Determine the correct scope and directory. Company-level decisions go in docs/decisions/; venture-level decisions go in ventures/[venture-slug]/docs/decisions/; product-level decisions go in ventures/[venture-slug]/products/[product-slug]/decisions/. Pick the narrowest scope that's actually correct.
Get the next ADR number. Look at existing ADRs in the target directory and take the next number in sequence. Never renumber existing ADRs to make room or fix a perceived gap.
Write the decision honestly. Context, decision, consequences, alternatives considered — do not skip alternatives considered even if the answer seems obvious in hindsight.
Set status to proposed. A newly written ADR must be marked status: proposed (or the ADR-specific decision_status: proposed per schemas/adr.schema.json) pending explicit human ratification. Do not mark it accepted yourself, even if you believe the decision is correct.
Link related documents. Cross-link any related ADRs, standards, or specifications this decision affects.
Report back. State clearly that the ADR is proposed and awaiting human ratification, and what would need to happen for it to be accepted.