Governance

Decision, waiver, incident, and review

These four objects have different statuses; merging them erases who decided, what deviated, and what still needs correction.

Objectives

Prerequisites

Concepts

Documented decision
A dated, attributed, and bounded outcome of an authorised process, retaining its evidence, open questions, and limitations.
Waiver and emergency stop
A waiver is explicitly approved, bounded, and tracked; an emergency stop suspends the action without retroactively creating a waiver.
Incident, reconciliation, and review
Reconciliation compares expected and observed states; the post-incident review separates facts, unknowns, decisions, actions, and follow-up.
DAGR candidate concept
In the Learning Hub, DAGR is only an advanced-research candidate concept. No public specification or public implementation is referenced here, and no operational capability is claimed.

Visual guide

Retaining statuses

Synthetic example

An action deviates from policy without approval. It must be treated as an incident or deviation, not retrospectively renamed an exception.

A status must not be rewritten to hide a deviation.

This lesson proposes a record structure for keeping decisions, exceptions, incidents, and reviews distinct.

What this lesson does not demonstrate

It classifies no real event and replaces no legal, regulatory, or contractual obligation.

Check question

It is named after the event to avoid calling it an incident.

It remains permanent and implicit.

It is approved, bounded, dated, and tracked.

Choose an answer to read its feedback.

Local checklist

Classify a fictional event without erasing unknowns.

This activity is neither an incident report nor an official decision.

Sources and limitations