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.
- StatusProposed by QIS (not yet industry usage)
- AdoptionExperimental
- LayerGovernance
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 (Agent2Agent) 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.
Where it comes from
QIS Canonical Extension. Names a gap the standards register leaves open — every cited kill-functionality requirement addresses stopping, none addresses resuming.
No published instrument defines this term yet; the note above is its origin.
What it is not
These are routinely confused with Restart Condition. The distinctions have consequences for how a system is governed.
- Kill Functionality
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.
How it connects
What it needs
- Restart Condition requires Kill Functionality Canon term
MARQUE questions it addresses
- DriftHow is behavioral change detected before it becomes loss?
Related framework objectives
Connected through the MARQUE (a reference framework organized around eight questions) crosswalk, an editorial mapping. These objectives from the Financial Services AI Risk Management Framework are assigned to the same questions that this term addresses. The ones sharing most of this term's vocabulary are shown first, as a reading aid. The assignment is to the question, not to the term: the source does not map this term to any objective directly.
Question: Drift · 11 control objectives assigned
- MS-2.5.2Validation Results and ImprovementMeasure
Cite and reuse
Cite the identifier QIS-TERM-00058, not the URL: identifiers are stable, URLs may change. This entry is free to read, quote and index under the dual license. Corrections sent to editor@qisfund.com are published.
Technical details: identifier, graph relationships and record
| Predicate | Target identifier | Target | Predicate meaning |
|---|---|---|---|
requires | term:kill-functionality | Kill Functionality | The subject imposes the object as a precondition. |
addresses | marque:drift | Drift | The subject speaks to the object as a question or concern. |
- Canonical identifier
QIS-TERM-00058- Tier
- QIS Canonical Extension
- Domain · layer
- Oversight · Governance
- Semantic aliases
- None recorded
- First published
- 2026-08-02
- Last reviewed
- 2026-08-02 · 180-day cycle