shared-resource-stewardship

Establish formal governance agreements for shared resources across multiple AZPOs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of governing jointly-held resources across multiple AZPOs, preventing control vacuums or dominance by single entities, and ensuring equitable access and rotating stewardship.

Core Features & Use Cases

  • Formalized Governance: Establishes explicit governance agreements for shared resources like funding pools, infrastructure, repositories, and services.
  • Rotating Stewardship: Prevents entrenchment of control by implementing a system of rotating stewards from participating AZPOs.
  • Equitable Access Rules: Defines clear rules for accessing and utilizing shared resources.
  • Use Case: Multiple research labs within a university (AZPOs) need to share a high-performance computing cluster. This Skill can be used to create a governance agreement that outlines contribution levels, access priorities, and a rotating stewardship role to manage the cluster's operations.

Quick Start

Use the shared-resource-stewardship skill to propose a new shared knowledge repository between the Bali and Costa Rica SHURs.

Frequently Asked Questions about shared-resource-stewardship

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

FAQPage Schema
How do I establish governance for shared resources across multiple units?

Governance for shared resources is established through formal multi-party consent and rotating stewardship agreements. This prevents single-entity control over jointly-held assets like funding pools, infrastructure, and repositories by defining explicit access rules, contribution commitments, and exit terms.

What is the best way to manage shared funding pools and infrastructure equitably?

The best way to manage shared funding pools and infrastructure equitably is by ratifying a formal governance agreement. This approach mandates rotating stewardship and multi-party consent, ensuring equitable access across participating units and preventing dominance by a single entity.

How does rotating stewardship prevent single-entity control of shared repositories?

Rotating stewardship prevents single-entity control of shared repositories by regularly changing the managing unit among participating parties. This system requires explicit negotiation and ratification of governance agreements, defining access rules and contribution commitments to avoid control entrenchment.

Can I use this approach to manage a shared computing cluster for research labs?

Yes, you can manage a shared computing cluster for research labs by creating a formal governance agreement. This defines contribution levels, access priorities, and a rotating stewardship role to manage operations, ensuring equitable access and preventing any single lab from dominating the resource.

What terms need to be negotiated when setting up inter-unit resource coordination?

Setting up inter-unit resource coordination requires explicit negotiation of stewardship rotation, access rules, contribution commitments, and exit terms. Ratifying these governance agreements ensures that jointly-held resources like services and repositories have clearly defined operational boundaries.

When do I need a formal governance agreement for jointly-held resources?

You need a formal governance agreement for jointly-held resources when multiple units require equitable access and shared control over assets like funding pools or infrastructure. This prevents control vacuums and ensures rotating stewardship through multi-party consent and explicit rule ratification.