# Decisions

> Propose a decision, vote, decide, and write it back to GitHub.

A decision is a shape for something the team is settling: proposed, voted on, decided, and eventually superseded. Once decided, it can be written back to GitHub as an architecture decision record (ADR) or a Discussion post.

![Decisions on a board: one proposed with votes, two decided, one superseded by another, and one written back as ADR 0003 with its pull request open.](https://tack.social/_astro/decisions-light.Cq2CPbqg_Zm4eN1.webp)

## Proposing

Press `D` and click to place one. Type the title (“What did you decide?”), press `Enter` for the body (“The decision, and why”), and `Esc` or `⌘` `Enter` to finish.

Or let [AI](https://tack.social/boards/ai.md) draft one from a discussion: select its stickies and cards (or its section) and choose **Decide** in the bar (`⌥` `⇧` `D`).

Connect it to the issues it settles: every card at the other end of a connector touching the decision is one of its **linked items**, listed on it.

## Voting

While a decision is **Proposed**, anyone who can edit the board can vote **Agree** or **Disagree**. Each person has one vote: click the other option to change it, or the same one again to take it back. Voters’ initials show beside the counts.

## Deciding and superseding

Choose **Decide** to mark it decided, with who decided it and when. While anyone has voted against it, Decide asks once more (“Decide anyway”, over how the vote stands, such as “3 agree, 1 disagree”), so nobody decides mid-vote by accident. The **Decision options** menu has the rest:

- **Mark decided**, or **Reopen as proposed**
- **Supersede with a new decision**, which adds a new decision beside it, connected by a “supersedes” connector
- **Mark as superseded by…**, to point it at another decision already on the board, picked from a list

A superseded decision says what superseded it, and links to it.

## Writing it back

Once a decision is decided, choose **Write back**. It can become:

- **An ADR pull request**: a new record in `docs/decisions/` on its own branch, for review. When the pull request merges, the decision shows **Merged**, with no one touching the board.
- **A Discussion post**, announcing it for comment.

Either way it’s staged with the board’s other changes, and nothing is written until someone pushes. See [Decision records](https://tack.social/writing-back/decision-records.md).