agreement-registry

Maintain and query active governance agreements across universal and ETHOS domains.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

The agreement registry consolidates governance contracts into a single, authoritative source of truth, enabling transparent tracking of existence, status, and history.

Core Features & Use Cases

  • Centralized storage of all active agreements across universal, ecosystem, and domain-specific hierarchies.
  • Read and query capabilities for participants to verify current status, version history, and relationships between agreements.
  • Consistency checks and cross-reference validation to surface stale or conflicting references for remediation.

Quick Start

Query the registry for the current version and status of all active agreements.

Frequently Asked Questions about agreement-registry

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

FAQPage Schema
What is a governance agreement registry and how does it work?

A governance agreement registry maintains a single source of truth for all active governance agreements. It consolidates contracts across universal and ETHOS domains, enabling transparent tracking of agreement existence, current status, and version history.

How do I query the current version and status of active governance agreements?

To query active governance agreements, access the registry to retrieve current_version and status fields. The registry supports open queries by any participant to verify agreement details, dates, parties, and hierarchical relationships across domains.

Can I track version history and parent relationships for amended governance agreements?

Yes, the agreement registry tracks version_history and parent_agreement_id fields for amended governance agreements. It handles writes from agreement creation, amendment, and review while maintaining hierarchy_level for each agreement.

Does the agreement registry support cross-reference validation for stale or conflicting agreements?

The agreement registry performs consistency checks and cross-reference validation to surface stale or conflicting references. This enables remediation of outdated agreements and ensures the single source of truth remains accurate across universal and domain-specific hierarchies.

What schema fields are maintained for governance agreements in a centralized registry?

The registry schema maintains fields including agreement_id, type, title, current_version, status, domain, dates, parties, parent_agreement_id, hierarchy_level, and version_history for each governance agreement stored in the system.

How do I consolidate governance contracts across multiple domains into a single source of truth?

To consolidate governance contracts, the registry provides centralized storage across universal, ecosystem, and domain-specific hierarchies. It accepts write artifacts from agreement creation and amendment processes while enabling open queries for verification.