# Decision items

<!-- squads:managed — regenerated by `sq sync`; do not edit by hand. -->
<!-- squads:version:0.5.0 -->

An architecture decision record: context, decision, consequences.

**Lifecycle:** Proposed → Accepted → Superseded (+ Rejected, Deprecated)

## Commands

```bash
sq create decision "…" --author architect
sq decision <n> status Accepted
```

## For Robert Architect (`architect`)

**Enter** — before you act:
- Read the full item dossier: `sq decision <n> show --full --comments` (decisions and
  refinements often live in discussion comments, not the body — skipping this is how context
  gets missed).
- gather the context + the options you're weighing

**Do:**
- author the ADR (`sq create decision "…" --author architect`)
- in the body capture context, the decision, and consequences
- link what it affects (`sq decision <n> ref add … --kind related`)

**Hand off:**
- once the decision is agreed, `sq decision <n> status Accepted` and `@tech-lead` to apply it in the affected tasks

**Watch for:**
- supersede an old ADR rather than editing its decision after acceptance

## For Olivia Lead (`tech-lead`)

**Enter** — before you act:
- Read the full item dossier: `sq decision <n> show --full --comments` (decisions and
  refinements often live in discussion comments, not the body — skipping this is how context
  gets missed).
- read the proposed decision + its context

**Do:**
- co-author/review it; ensure tasks follow it once Accepted

**Hand off:**
- supersede it (new ADR) when reality changes

---
The `.md` files are sq-managed — never edit them by hand. Items are addressed as
`sq decision <n> <verb>`. Set this item's body with `sq decision <n> body
-m "…"` (or `--file`); `--desc` sets only the short summary. Its user stories / subtasks / findings
get their bodies from `sq decision <n> <kind> <k> body -m "…"`. Read anything back with
`sq decision <n> show --full --comments` (full dossier, including discussion) /
`sq decision <n> <kind> <k> show`.
