role-sunset

Dissolve governance domains by inventorying responsibilities, archiving contracts, and applying a reactivation window.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill prevents the accumulation of "zombie" governance domains by providing a structured process for their formal dissolution, ensuring no lingering authority or orphaned responsibilities.

Core Features & Use Cases

  • Formal Dissolution: Executes a complete sunset process for domains that have served their purpose.
  • Accountability: Ensures all responsibilities and agreements are inventoried and dispositioned before dissolution.
  • Grace Period: Includes a 90-day window for discovering and resolving any missed items post-sunset.
  • Use Case: When a project-specific governance domain is no longer needed after project completion, this Skill can be used to formally archive it, preventing it from becoming a source of confusion or potential misuse.

Quick Start

Use the role-sunset skill to initiate the sunset process for the 'legacy-project-domain'.

Frequently Asked Questions about role-sunset

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

FAQPage Schema
How do I formally dissolve an obsolete governance domain?

A governance domain sunset requires strict procedural steps and consent mechanisms to formally dissolve obsolete domains. It inventories responsibilities, executes a disposition plan, archives the domain contract, and provides a 90-day reactivation window for resolving missed items.

What is a domain sunset process for governance accountability?

Governance domain dissolution inventories responsibilities and agreements, executes a disposition plan, archives the domain contract, and provides a 90-day reactivation window. This prevents zombie governance domains from accumulating with lingering authority or orphaned responsibilities.

When should I initiate a governance domain dissolution?

Initiate domain sunset when a governance domain has achieved its purpose, become vacant, or is otherwise deemed obsolete. This prevents project-specific governance domains from becoming sources of confusion or potential misuse after project completion.

How does the 90-day reactivation window work during a domain sunset?

The 90-day reactivation window is a grace period after archiving the domain contract. It allows you to discover and resolve any missed items or orphaned responsibilities post-sunset before the governance domain is fully dissolved.

Can I sunset a domain without inventorying all agreements first?

No, inventorying responsibilities and agreements is a required step before dissolution. The sunset process mandates strict procedural steps and consent mechanisms to ensure accountability and prevent orphaned responsibilities during the disposition phase.

What happens to the domain contract after a governance domain is dissolved?

The domain contract is formally archived during the sunset process. After archiving, a 90-day reactivation window opens to resolve any missed items, ensuring the governance domain does not retain lingering authority once fully dissolved.