pre-authorization-protocol

Register pre-authorized emergency roles with authority scopes, hard ceilings, and auto-expiration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Define emergency roles with pre-consented authority scopes, hard ceilings, and auto-expiration to prevent improvised power during crises.

Core Features & Use Cases

  • Maps emergency criteria to pre-authorized roles and assigns bounded authority.
  • Establishes hard ceilings, auto-expiration, and irreducible constraints to safeguard governance.
  • Maintains a transparent ACT-driven registry and supports post-emergency reviews and ongoing calibration.

Quick Start

Review emergency criteria, map roles, set authority scopes and ceilings, and install pre-authorizations via the ACT process

Frequently Asked Questions about pre-authorization-protocol

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

FAQPage Schema
How do I define emergency governance roles with pre-consented authority scopes?

To define emergency governance roles, you map specific emergency criteria to pre-authorized roles and establish bounded authority scopes, hard ceilings, and auto-expiration to prevent improvised power during crises.

What is pre-authorization for emergency governance and when is it needed?

Pre-authorization for emergency governance is the process of establishing consent for rapid response roles before crises occur. It is needed when ETHOS governance contexts require rapid responses that must stay within defined boundaries.

How do I set hard ceilings and irreducible constraints for emergency roles?

You set hard ceilings and irreducible constraints for emergency roles by acknowledging them during the role design phase, ensuring they are tracked in the Pre-Authorization Registry and aligned with the irreducible-constraints.yaml file.

Does the pre-authorization protocol support auto-expiration and post-emergency reviews?

Yes, the pre-authorization protocol supports auto-expiration by setting expiration parameters for emergency roles and facilitates post-emergency reviews and ongoing calibration through a transparent ACT-driven registry.

What data is included in a Pre-Authorization Registry entry for role design?

A Pre-Authorization Registry entry includes role_id, role_name, associated_criteria, authority_scope, hard_ceilings, auto_expiration, primary_holder, alternate_holders, status, and activation_history for comprehensive role tracking.