Squawk statuses

What it is

A squawk moves through a short lifecycle from first report to a terminal state. At any moment every squawk is in exactly one of five statuses.

dismissed ◀─ dismiss ── pending ── confirm ──▶ open ── resolve ──▶ resolved
                                                │ ▲                   ▲
                                          defer │ │ deferral          │ resolve
                                                ▼ │ expires           │
                                              deferred ───────────────┘

Terminal statuses: resolved and dismissed. A squawk cannot move out of these. A deferred squawk is not terminal: if its date passes before anyone resolves it, it returns to open and the asset is grounded again.

Who can use it

Members report squawks (creating a pending or open squawk depending on the syndicate policy).
Admins confirm, dismiss, defer, and resolve squawks.

Where to find it

Per-asset squawk list: /syndicates/:syndicateId/assets/:assetId/squawks.
Pending-approvals queue: /syndicates/:syndicateId/squawk-approvals.
Individual squawk detail: /squawks/:squawkId.

Fields / options

Status	Serialised	Terminal	Counts toward “active”
Pending	`pending`	No	Yes
Open	`open`	No	Yes
Deferred	`deferred`	No	Yes
Resolved	`resolved`	Yes	No
Dismissed	`dismissed`	Yes	No

What each status means

Pending: reported by a member, awaiting admin review. Used when the syndicate setting “Require admin confirmation for squawks” is on and the reporter is not themselves an admin.
Open: active and in force. Grounding squawks in this state ground the asset.
Deferred: the admin has acknowledged the issue and allowed the asset to continue operating until a stated date, with a recorded reason. When the date passes the squawk returns to open and the asset is grounded again, unless it has been resolved first.
Resolved: fixed. No further action needed.
Dismissed: reviewed and judged not a real defect; dropped without a fix.

Behaviour rules

Starting status depends on syndicate policy and reporter role:
- Confirmation required and reporter is not an admin → pending.
- Otherwise → open.
Only pending squawks can be confirmed. Confirming transitions to open and stamps the confirming admin and time.
Only pending squawks can be dismissed through the approval flow. Dismissal requires a dismissal reason from the admin.
Only open grounding squawks can be deferred. Caution and info squawks have no ground effect and do not need deferral. Deferral requires a deferral date and a reason.
A deferral expires on its own. When the deferral date passes, the squawk returns to open, the asset is grounded again, and the bookings spanning it suspend, unless an admin resolved it first. The syndicate’s admins get a reminder on the day it expires.
Only open or deferred squawks can be resolved. A pending squawk must be confirmed first; a dismissed squawk is terminal.
Resolved and dismissed are terminal. Reopening is not supported. The correct response is a fresh squawk referencing the original.
“Active” squawks (pending, open, deferred) appear in the asset’s squawk list; terminal squawks are filtered out of the default view.
The pending badge on the approvals queue counts only pending squawks.