Restart Condition
The set of preconditions — cause identified or its absence expressly recorded, an accountable individual's written authorization, and, where a capability is owed to a counterparty, advance notice — that must be satisfied before a halted system may resume operation.
Why it matters
Kill functionality is required by name in RTS 6 and referenced throughout model-risk guidance; no reviewed standard specifies what must be true before a halted system resumes. That silence is where a halt gets waived rather than honored: the pressure to resume arrives within hours, on whoever is least equipped to resist it, and a restart condition that cannot be satisfied under pressure is one that gets skipped.
This term is a QIS Canonical Extension. It does not currently appear in the Model Context Protocol specification, the A2A specification, the AIEOG Shared AI Lexicon, or any instrument in our standards register. We are proposing it because we have documented the gap it fills, and we label it as ours everywhere it appears. Adopt it, argue with it, or ignore it — but do not cite it as industry consensus, because it is not.
What it is not
These are routinely confused with Restart Condition. The distinctions are not pedantic — each one has consequences for how a system is governed.
Kill functionality is the capacity to stop. A restart condition is the precondition for starting again; a form can satisfy one and be silent on the other.
Relationships
Typed edges into the rest of the ontology. These are what make the canon traversable rather than merely readable.
| Verb | Target | Meaning |
|---|---|---|
requires | Kill Functionality | The subject imposes the object as a precondition. |
addresses | marque:drift | The subject speaks to the object as a question or concern. |
Record
| Canonical identifier | QIS-TERM-00058 |
| Status | QIS Canonical Extension |
| Adoption | Experimental |
| Domain · Layer | Oversight · Governance |
| Origin | QIS Canonical Extension. Names a gap the standards register leaves open — every cited kill-functionality requirement addresses stopping, none addresses resuming. |
| Semantic aliases | None recorded. |
| First published | 2026-08-02 |
| Last reviewed | 2026-08-02 · 180-day cycle |
Cite the identifier, not the URL. Identifiers are stable; URLs may change. This entry is free to read, quote and index under the dual license. Corrections to [email protected] are published.