agreement-registry

Manage and query ecosystem agreements with status, version history, and relationships.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/JadeZaher/neos-operating-system --skill agreement-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agreement-registry
Source: https://github.com/JadeZaher/neos-operating-system/tree/main/neos-core/layer-01-agreement/agreement-registry
Command: npx skills add https://github.com/JadeZaher/neos-operating-system --skill agreement-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill provides a transparent and navigable single source of truth for all agreements within the ecosystem, preventing governance from becoming an archaeological endeavor.

Core Features & Use Cases

  • Centralized Agreement Management: Maintains and queries all active agreements, their versions, and relationships.
  • Query Access: Allows any participant to query agreements based on various criteria.
  • Write Access Control: Restricts writes to authorized processes (agreement-creation, amendment, review).
  • Use Case: A new participant can query the registry to understand all agreements applicable to their role and domain, ensuring compliance and clarity from day one.

Quick Start

Query the agreement registry for all active space agreements in the SHUR Bali domain created in the last year.

Frequently Asked Questions about agreement-registry

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

FAQPage Schema
How do I manage agreement version history and status across an entire ecosystem?

Manage agreement version history and status by using a central registry that tracks all active agreements, their versions, and relationships across all hierarchical levels. This ensures governance transparency and serves as the single source of truth.

What is a central registry for agreements and how does it ensure compliance?

A central registry for agreements is a single source of truth that maintains all active ecosystem agreements, their versions, and relationships. It ensures compliance by restricting write access to authorized creation, amendment, and review processes while allowing open queries.

How do I query active agreements applicable to a specific domain or role?

Query active agreements applicable to a specific domain or role by accessing the central registry's open query access. Any participant can search based on various criteria to understand all agreements applicable to their role, ensuring clarity and compliance.

Can any participant write to the agreement registry, or is access restricted?

No, participants cannot freely write to the agreement registry. Write access is restricted to authorized processes like agreement creation, amendment, and review, while open query access is provided to all participants for transparency.

When do I need a single source of truth for ecosystem governance?

You need a single source of truth for ecosystem governance when managing complex relationships and version histories across hierarchical levels. This prevents governance from becoming an archaeological endeavor and ensures navigability for all participants.