emergency-criteria-design

Define objective emergency criteria and exit conditions for ETHOS and SHUR locations.

2|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Community-Chests/neos-operating-system --skill emergency-criteria-design-community-chests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emergency-criteria-design
Source: https://github.com/Community-Chests/neos-operating-system/tree/main/neos-core/layer-08-emergency/emergency-criteria-design
Command: npx skills add https://github.com/Community-Chests/neos-operating-system --skill emergency-criteria-design-community-chests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Defines objective emergency criteria and exit conditions to prevent subjective crisis declarations during crises.

Core Features & Use Cases

  • Risk assessment and domain scoping for multiple ETHOS contexts.
  • ACT Advice and Consent workflows to install, monitor, and review criteria.
  • Publication of a centralized Emergency Criteria Registry for ecosystem transparency and governance integrity.

Quick Start

Install starter criteria into the ACT workflow and publish them to the registry.

Frequently Asked Questions about emergency-criteria-design

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

FAQPage Schema
How do I define objective emergency criteria to prevent subjective crisis declarations?

Defining objective emergency criteria requires establishing formal risk assessments and exit conditions across governance, funding, safety, and infrastructure domains before a crisis occurs. This approach prevents subjective declarations by using unique criterion IDs and a published registry.

What is the ACT Advice and Consent workflow for policy design?

The ACT Advice and Consent workflow is a formal process used to install, monitor, and review emergency criteria. It ensures governance integrity by requiring formal installation and review dates before criteria are published to the centralized registry.

How do I set up an emergency criteria registry for governance transparency?

Setting up an emergency criteria registry involves publishing installed criteria with unique IDs, activation history, and review dates. This centralized registry provides ecosystem transparency and tracks criteria across multiple ETHOS and SHUR locations.

When do I need to perform a risk assessment for emergency criteria design?

Risk assessment for emergency criteria design is needed before installing policies through the ACT workflow. It scopes multiple ETHOS contexts across governance, funding, safety, and infrastructure domains to ensure criteria cover relevant crisis scenarios.

Can I use emergency criteria design for multiple ETHOS and SHUR locations?

Yes, emergency criteria design explicitly covers risk assessment and criteria installation across multiple ETHOS and SHUR locations. It requires annual reviews and a published registry to maintain governance integrity throughout the ecosystem.

What are the limitations of using subjective crisis declarations without formal exit conditions?

Without formal exit conditions and objective emergency criteria, crisis declarations risk being subjective and lacking governance oversight. Implementing a criteria registry with activation history and annual reviews prevents unchecked subjective declarations.