re-entry-integration

Process former member re-entry with consent and a 30-day orientation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Returning members often rejoin with outdated terms or missing context. This skill provides a structured, auditable re-entry process that ensures consent to current agreements, preserves historical context, and prevents preferential treatment.

Core Features & Use Cases

  • Structured flow from request to Re-Entry Record filing, including verification of departure context, portable record, and change summaries.
  • Coordinate integration by planning ETHOS and circle assignment, and enforcing a 30-day orientation.
  • Audit-ready records and notices to maintain governance transparency.

Quick Start

Initiate a re-entry for a former member and begin the 30-day orientation while collecting consent to current agreements.

Frequently Asked Questions about re-entry-integration

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

FAQPage Schema
How do I manage re-entry for former members returning to a governance ecosystem?

Manage re-entry for returning members by initiating a structured flow that verifies departure context, checks portable records, and enforces a 30-day orientation period. This ensures former members consent to current foundational agreements before rejoining the ecosystem.

What is a formal re-entry process for membership governance and why is it needed?

A formal re-entry process is an auditable workflow that captures explicit consent to current agreements and preserves historical context. It is needed because returning members often rejoin with outdated terms, missing context, or require standardized orientation to prevent preferential treatment.

How do I verify portable records and capture consent for returning circle members?

Verify portable records and capture consent by processing the re-entry request through a structured flow that validates departure context, summarizes changes, and requires explicit agreement to current foundational terms before filing a Re-Entry Record artifact.

Does the re-entry integration process require a mandatory orientation period before publishing a notice?

Yes, the re-entry integration process requires a mandatory 30-day orientation period. During this time, ETHOS and circle assignments are coordinated, consent is collected, and a factual re-entry notice is published only after the orientation requirements are met.

Can I use this structured re-entry workflow across different ETHOSs and circles in the NEOS ecosystem?

Yes, you can use this structured re-entry workflow across receiving ETHOSs and circles within the NEOS ecosystem. It coordinates integration by planning assignments and maintaining audit-ready records to ensure governance transparency across all groups.

What limitations exist when handling re-entry requests without complete departure context or portable records?

Without complete departure context or portable records, the structured re-entry flow cannot fully verify the former member's historical standing or ensure audit-ready compliance. The process depends on verifying these records to prevent preferential treatment and accurately file the Re-Entry Record artifact.