Ask — one decision, one record

An ask is a decision request with a deadline-shaped default. It exists so that a question the human must answer is one record they can find, not a TODO line, a chat message, or a hope.

Shape of an ask

An ask always carries, verbatim:

The question — one sentence, as its title.
Options — the realistic choices, each one line.
Default if silent — what proceeds, and after how long. The default must be sane enough to actually run.
Blocks — what work is held until it is answered, named by ticket or scope.

Where an ask lives

An ask is a ticket in the tenant's own Linear, labelled catalyst-ask, written through the same Linear write access the linearis skill uses (the customer's own Linear tooling and credential — never a credential you improvised). The tenant's mirror recognises that label and holds the ticket out of the dispatchable pool, so a question is never mistaken for work. Cite the ask's identifier only after the create call returned it.