# Dispositions

An ask is an artefact here, not a bolded line in a document nobody answers.
**ADR-29 clause 2.**

`<date>-<kind>.json` — the queue. Written by Hobbs in the same act as the brief
or the review it comes from, never afterwards from a re-reading: the report's ask
and the queue entry must not be able to disagree.

`<date>-<kind>.answers.jsonl` — append-only, one line per click, written by the
review surface. Last line for an ask wins.

## An ask

```json
{
  "id": "w3-07-bg9",
  "section": "7 — Next-actions scan",
  "short": "the Ophelia yard invoice",
  "ask": "one sentence, answerable yes or no",
  "context": "what he needs in front of him to answer it",
  "tasks": ["hobbs-bg9"],
  "yes_label": "Paid — close it",
  "no_label": "Still unsent",
  "effects": {
    "yes": [{ "verb": "close", "id": "hobbs-bg9" }],
    "no":  [{ "verb": "note", "id": "hobbs-bg9" },
            { "verb": "hobbs", "what": "what Hobbs does with this answer" }]
  }
}
```

**The effects are the judgment, and they are written when the ask is written.**
The five verbs — `close`, `priority`, `label`, `note`, `hobbs` — are the whole
vocabulary the surface will execute. `defer` never carries a mechanical effect,
because a defer carries his words by definition and words are intentions.

Anything the surface does not recognise is refused and the answer is still
recorded. Losing the answer is the only unrecoverable failure.