inter-unit-liaison

Establish formal liaison roles with explicit mandate boundaries for cross-ETHOS coordination.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Defines formal liaison roles with explicit mandate boundaries to enable accountable, distributed cross-ETHOS coordination and to prevent information capture.

Core Features & Use Cases

  • Formal liaison roles with explicit mandate boundaries across ETHOS for ongoing cross-unit coordination.
  • Four-layer mandate structure (can communicate, can explore, can recommend, requires consent) with rotation and regular reporting.
  • Role assignment and registration in all participating ETHOS registries to ensure traceability and accountability.

Quick Start

Draft a four-layer liaison mandate, appoint the liaison via role-assignment, and register it in all participating registries.

Frequently Asked Questions about inter-unit-liaison

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

FAQPage Schema
How do I establish formal cross-unit coordination roles with explicit mandate boundaries?

Cross-unit coordination roles are established by defining a formal liaison with a four-layer mandate structure—can communicate, can explore, can recommend, and requires consent—then assigning the role and registering it in all participating ETHOS registries to ensure accountability and prevent information capture.

What is a four-layer mandate structure for liaison roles and how does it work?

A four-layer mandate structure defines liaison authority boundaries using four tiers: can communicate, can explore, can recommend, and requires consent. This layered approach prevents information capture by explicitly limiting how much autonomy a liaison has when coordinating across multiple ETHOS units.

How do I set up role assignment and registry registration for ongoing bilateral coordination?

Role assignment and registry registration for bilateral coordination require drafting a liaison mandate, appointing the liaison via role-assignment, and registering the appointment in all participating ETHOS registries to maintain traceability across ongoing cross-unit collaborations.

Can I use rotation and reporting cadence to prevent information capture in multilateral coordination?

Rotation and reporting cadence prevent information capture in multilateral coordination by enforcing regular reporting procedures and term dates for liaison roles. These rotation controls ensure no single liaison retains exclusive control over cross-ETHOS communication channels indefinitely.

When do I need formal escalation procedures for cross-ETHOS liaison roles?

Formal escalation procedures for cross-ETHOS liaison roles are needed when ongoing cross-unit collaborations encounter issues exceeding the liaison's mandate scope. Escalation procedures ensure structured resolution paths exist beyond the four-layer mandate boundaries defined during initial role assignment.