ethos-dissolution

Orchestrate consent-driven ETHOS dissolution with asset disposition and archival workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

When a NEOS ETHOS can no longer sustain operations, this skill provides a disciplined, consent-driven process to dissolve the ETHOS, settle obligations, transition members, and permanently archive governance history.

Core Features & Use Cases

  • Trigger verification and governance-structure integrity checks to ensure dissolution only proceeds under defined conditions (e.g., governance incapacity, 2/3 member consent, or ecosystem intervention).
  • Impact assessment and asset disposition planning that identify assets, obligations, partnerships, and cross-ETHOS relationships, with clear responsibilities and timelines.
  • Member transition orchestration, including issuing portable records, offering alternative ETHOS paths, and maintaining community continuity through asset and relationship migrations.
  • Use Case: A small ETHOS with dwindling membership uses this process to wind down responsibly, rehoming assets to the ecosystem pool and transferring remaining participants to a successor ETHOS.

Quick Start

Submit a formal dissolution proposal, appoint an independent dissolution coordinator, and begin the impact assessment.

Frequently Asked Questions about ethos-dissolution

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

FAQPage Schema
How do I dissolve an ETHOS and wind down its governance operations?

To dissolve an ETHOS, you orchestrate a consent-driven exit by verifying trigger conditions, settling obligations, dispositioning assets, transitioning members, and archiving governance records. The process requires a formal proposal and an independent dissolution coordinator to manage the workflow.

What conditions are required to trigger an ETHOS dissolution?

ETHOS dissolution requires verified evidence of a triggering condition, such as governance incapacity, two-thirds member consent, or ecosystem intervention. The process also requires a defined asset and obligation ledger, an agreed consent window, and established channels for amending agreements.

How does member transition work during a governance dissolution?

Member transition during dissolution involves issuing portable records, offering alternative ETHOS paths, and maintaining community continuity through asset and relationship migrations. This ensures remaining participants are successfully transferred to a successor ETHOS or rehomed within the ecosystem pool.

What is the best way to archive governance records when winding down an ETHOS?

The best way to archive governance records during dissolution is using a controlled archival workflow that permanently stores governance history. This skill handles records archival alongside asset disposition, ensuring all obligations are settled and historical data is preserved.

Can I use this dissolution process for a small ETHOS with dwindling membership?

Yes, this dissolution process suits a small ETHOS with dwindling membership by providing a disciplined method to wind down responsibly. It facilitates rehoming assets to the ecosystem pool and transferring remaining participants to a successor ETHOS.

What limitations exist when coordinating asset disposition across multiple ETHOS relationships?

Asset disposition requires a comprehensive impact assessment to identify cross-ETHOS relationships, partnerships, and obligations before proceeding. The dissolution coordinator must establish clear responsibilities and timelines to manage these dependencies without disrupting the broader ecosystem.