member-lifecycle

Manage auditable participant lifecycles from onboarding through exit with append-only records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

The lifecycle system provides a canonical, auditable record of each participant's status and transitions to ensure governance processes like quorum calculations are trustworthy and traceable.

Core Features & Use Cases

  • End-to-end lifecycle tracking: record onboarding, active participation, inactivity, reactivation, exit, and archival of records.
  • Quorum and governance integrity: drive accurate quorum checks and cross-ETHOS interoperability.
  • Auditability and history: append-only transitions with timestamps, facilitator, UAF references, and activity logs.

Quick Start

Create a new lifecycle record for a prospective member and guide them through onboarding to become active.

Frequently Asked Questions about member-lifecycle

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

FAQPage Schema
How do I track participant lifecycle status from onboarding to exit for governance audits?

Participant lifecycle tracking records onboarding, active status, inactivity, reactivation, and exit transitions. It uses an append-only model with timestamps and facilitator references to ensure governance accountability and accurate quorum calculations.

What is the best way to maintain auditable records for member onboarding and mass exits?

Auditable member records are maintained using an append-only lifecycle model that stores transition dates, onboarding metadata, profiles, and activity logs. This approach handles both voluntary and mass exits while preserving provenance for governance reviews.

How does append-only record-keeping work for governance quorum calculations?

Append-only record-keeping for quorum calculations works by logging immutable participant status transitions with timestamps and references. This canonical history ensures only currently active members are counted, making quorum checks trustworthy and traceable.

Can I detect member inactivity and manage reactivation within an ETHOS governance context?

Yes, lifecycle management applies across ETHOS contexts to detect member inactivity and process reactivation. It tracks activity dates and transitions per member, ensuring accurate status updates without altering the historical audit trail.

Does member lifecycle management require specific dependencies to track role transfers and agreements?

Member lifecycle management requires no external dependencies to track role transfers and agreements. It stores references to these elements internally within each member's lifecycle record, maintaining a self-contained and auditable provenance chain.

What are the limitations of using an append-only lifecycle record model for participant exits?

The append-only lifecycle record model cannot delete or overwrite past status transitions during participant exits. Records are archived rather than removed, meaning historical data persists permanently to preserve auditability and governance compliance.