emergency-criteria-design

Design objective emergency criteria with matching exit conditions for governance systems.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/JadeZaher/neos-operating-system --skill emergency-criteria-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emergency-criteria-design
Source: https://github.com/JadeZaher/neos-operating-system/tree/main/neos-core/layer-08-emergency/emergency-criteria-design
Command: npx skills add https://github.com/JadeZaher/neos-operating-system --skill emergency-criteria-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill prevents subjective and potentially manipulative declarations of emergency by establishing clear, objective, and pre-consented criteria for when an emergency begins and ends.

Core Features & Use Cases

  • Objective Thresholds: Defines measurable entry and exit conditions for emergencies.
  • Pre-Consented Rules: Ensures criteria are agreed upon during calm periods, not in moments of crisis.
  • Use Case: Before any crisis, an organization defines that a "resource crisis" is triggered if funding drops by 30% with less than 60 days notice, and ends when 75% of the shortfall is covered or costs are reduced. This prevents a funder from creating an "emergency" for leverage.

Quick Start

Design emergency criteria for a new ecosystem by following the step-by-step process outlined in the skill documentation.

Frequently Asked Questions about emergency-criteria-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design objective emergency criteria for governance systems?

Design objective emergency criteria by establishing measurable entry and exit conditions for governance systems. This prevents subjective emergency declarations by ensuring all thresholds are pre-consented during calm periods rather than moments of crisis.

What is the best way to prevent subjective emergency declarations in risk management?

Preventing subjective emergency declarations requires pre-defining objective, measurable triggers and exit conditions. By establishing clear thresholds agreed upon before any crisis, organizations stop individuals from declaring emergencies for leverage.

How do I define measurable entry and exit conditions for an organizational crisis?

Define measurable entry and exit conditions by setting specific thresholds, such as a funding drop of 30% with under 60 days notice. Exit conditions trigger when 75% of the shortfall is covered or costs are reduced.

What prerequisites do I need to install emergency triggers and safeguard registries?

Installing emergency triggers requires risk assessment, an existing criteria registry, a safeguard trigger registry, ACT process access, domain boundary definition, and stakeholder input to ensure proper governance process compression.

When should I not use pre-consented emergency thresholds in governance?

Pre-consented emergency thresholds should not be used without prior risk assessment and stakeholder input. If domain boundaries are undefined or existing registries are missing, objective emergency criteria cannot be reliably established.