skills.rest
Community-Chests
Community-ChestsOFFICIAL
Explore all skills by this author →
GitHub

universal-agreement-field

Establishes a root consent framework with hierarchy, amendment processes, and onboarding rules for ecosystem governance.

2|Updated Mar 13, 2026
Search Tags:#templates#onboarding#governance#consensus#agreement#consent#osc
One-click install
npx skills add https://github.com/Community-Chests/neos-operating-system --skill universal-agreement-field-community-chests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: universal-agreement-field
Source: https://github.com/Community-Chests/neos-operating-system/tree/main/neos-core/layer-01-agreement/universal-agreement-field
Command: npx skills add https://github.com/Community-Chests/neos-operating-system --skill universal-agreement-field-community-chests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

The Universal Agreement Field provides a single root contract that all ecosystem participants consent to, establishing baseline commitments and preventing divergent norms.

Core Features & Use Cases

  • Establish root agreement hierarchy and override rules so higher-level agreements prevail
  • Enforce onboarding consent with a 48-hour reflection period and recorded consent
  • Support annual reviews, amendments, and conflict resolution through ACT and OSC consensus
  • Provide governance templates and references via assets/uaf-template.md

Quick Start

Onboard a new ecosystem member by presenting the current UAF, guiding the 48-hour reflection period, and recording explicit consent.

Frequently Asked Questions about universal-agreement-field

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

FAQPage Schema
How do I establish a root consent framework for ecosystem governance onboarding?▼

Apply the Universal Agreement Field to define a governance hierarchy with override rules, enforce a 48-hour reflection period during onboarding, and record explicit consent to prevent divergent ecosystem norms.

What is the required reflection period for enforcing onboarding consent in ecosystem governance?▼

The required reflection period for onboarding consent is 48 hours. During this time, new ecosystem members review the agreement before their explicit consent is documented and recorded to ensure governance integrity.

How do I handle amendments and conflict resolution for a root governance agreement?▼

Handle amendments and conflict resolution through annual reviews and cross-ETHOS coordination, utilizing ACT and OSC consensus-driven workflows to validate and document changes to the root agreement.

Does this governance agreement framework provide templates for defining consent hierarchy?▼

Yes, the framework provides governance templates and references via the uaf-template.md asset file, allowing you to define root agreement hierarchies and override rules where higher-level agreements prevail.

When do I need a single root contract for ecosystem consensus and governance?▼

You need a single root contract when baseline commitments must be established across all ecosystem participants to prevent divergent norms and sustain governance integrity through documented consensus-driven changes.

Related Skills

Explore More Legal & Compliance Skills→
JadeZaherJadeZaher

universal-agreement-field

Define a root agreement establishing baseline commitments for ecosystem participants.

Community
Advanced
Community-ChestsCommunity-Chests

authority-boundary-negotiation

Resolve overlapping domain authority via 11-element mapping and consensus negotiation.

Official
Advanced
Community-ChestsCommunity-Chests

community-impact-assessment

Analyze governance conflicts across harm circles and generate ACT-linked recommendations.

Official
Advanced
aaaa47080aaaa47080
4

Platform Content Moderation & Consensus

Implement decentralized moderation governance with PRO juror voting and automated penalties.

Community
Advanced