CC2.0 COLLABORATE Function Skill
Function: COLLABORATE - Team Coordination & Parallel Composition
Category Theory: Applicative + Parallel (independent coordination)
Purpose: Coordinate multiple agents/teams working on shared goals
Status: ✅ Production-Ready (380 lines, all parallel composition laws verified)
Local Installation: /Users/manu/cc2.0
Environment Variable: export CC2_HOME=/Users/manu/cc2.0
The Eternal Function
Universal Question: How do we coordinate?
This function captures the timeless human activity of coordinating independent efforts toward shared goals. Across all domains and eras, humans work in parallel on different aspects of a problem, then merge results. COLLABORATE is the bridge from "individual work" to "collective achievement."
Universality Across Domains
| Domain |
COLLABORATE Applies To |
Core Operation |
| Medicine |
Surgical teams, care coordination, specialist consultation |
Coordinate surgeon, anesthesiologist, nurses toward patient outcome |
| Business |
Department coordination, cross-functional teams, partnerships |
Coordinate sales, marketing, product toward revenue goals |
| Science |
Research collaboration, multi-institution studies, peer review |
Coordinate multiple labs toward research publication |
| Education |
Team teaching, curriculum development, assessment design |
Coordinate teachers across subjects toward learning goals |
| Manufacturing |
Assembly line coordination, supply chain, quality teams |
Coordinate production, logistics, QA toward delivery |
| Software |
Pair programming, code review, microservices orchestration |
Coordinate developers, services toward feature delivery |
| Law |
Legal team coordination, co-counsel, expert witnesses |
Coordinate attorneys, paralegals, experts toward case strategy |
| Architecture |
Design team, engineering coordination, contractor management |
Coordinate architects, engineers, contractors toward building |
The Universal Pattern
Independent Work → Parallel Composition → Merged Result
(Agents) → (Applicative) → (Outcome)
Historical Precedent:
- Ancient Building: Pyramid construction (coordinated labor - 2560 BCE)
- Military: Roman legion coordination (centurions + legates - 100 BCE)
- Industrial: Assembly line coordination (1913)
- Software: Microservices orchestration (2010s)
The function is eternal; the coordination mechanisms change.
Why This Works Universally
- Applicative Structure: Independent agents compose via
<*> operator
- Parallel: Agents work independently, results merge deterministically
- Compositional: Coordination of coordination (meta-collaboration)
- Role-based: Clear agent roles, interfaces, handoffs
Surgical team coordination = Software team coordination. Same structure, different agents.
When to Use This Skill
- 👥 Coordinate teams - Multiple agents working toward shared goal
- ⚡ Parallel execution - Independent work that merges
- 🔄 Role management - Define agent responsibilities, interfaces
- 📊 Merge results - Combine outputs from parallel agents
- 🎯 Shared context - All agents work from same base state
Building Foundations for Your Domain
Universal Function = Eternal Structure + Domain Foundations
COLLABORATE is an eternal categorical structure (Applicative + Parallel). To use it in YOUR domain, construct domain foundations - agent roles, communication protocols, and merge strategies.
The Pattern
COLLABORATE (Universal Applicative)
⊗
Domain Foundations (Roles + Protocols)
=
Domain Implementation
Foundations by Domain
| Domain |
Foundations to Construct |
Examples |
| Medicine |
Team roles, handoff protocols, communication standards |
Surgeon/anesthesiologist roles, SBAR protocol |
| Business |
Department roles, meeting cadence, reporting |
Sales/marketing roles, weekly syncs, dashboards |
| Software |
Service boundaries, API contracts, event schemas |
CC2.0 provides: Agent protocols, message schemas |
| Manufacturing |
Station roles, quality gates, inventory handoffs |
Assembly stations, inspection points, JIT delivery |
| Education |
Teacher roles, curriculum alignment, assessment sharing |
Subject specialists, standards mapping, grade sync |
| Science |
Lab roles, data protocols, authorship guidelines |
PI/postdoc roles, data formats, co-authorship |
| Law |
Attorney roles, document sharing, privilege protocols |
Lead/co-counsel, discovery sharing, privilege logs |
| Architecture |
Discipline roles, drawing coordination, change orders |
Architect/engineer, BIM coordination, RFIs |
Related Skills
- cc2-observe: Provides shared context for all agents
- cc2-reason: Generates collaborative strategies
- cc2-create: Agents create different artifacts in parallel
- cc2-verify: Validates merged results from collaboration
- cc2-orchestrator: Orchestrates complex multi-agent workflows
File References
Implementation: ${CC2_HOME}/src/functions/collaborate/CollaborateFunction.ts (380 lines)
Tests: ${CC2_HOME}/tests/laws/collaborate-parallel.test.ts
Documentation: ${CC2_HOME}/functions/collaborate/FUNCTION.md
Status: ✅ Production-Ready
Categorical Rigor: L5 (Pragmatic with parallel composition)
Test Coverage: 100% (all parallel composition laws verified)
"To collaborate is to transform individual effort into collective achievement, to bridge isolation and coordination. COLLABORATE is the applicative that makes parallel work convergent."
— CC2.0 Categorical Foundations
1---2name: cc2-collaborate3description: CC2.0 COLLABORATE Function Skill4---5# CC2.0 COLLABORATE Function Skill67**Function**: COLLABORATE - Team Coordination & Parallel Composition8**Category Theory**: Applicative + Parallel (independent coordination)9**Purpose**: Coordinate multiple agents/teams working on shared goals10**Status**: ✅ Production-Ready (380 lines, all parallel composition laws verified)1112**Local Installation**: `/Users/manu/cc2.0`13**Environment Variable**: `export CC2_HOME=/Users/manu/cc2.0`1415---1617## The Eternal Function1819**Universal Question**: *How do we coordinate?*2021This function captures the timeless human activity of coordinating independent efforts toward shared goals. Across all domains and eras, humans work in parallel on different aspects of a problem, then merge results. COLLABORATE is the bridge from "individual work" to "collective achievement."2223### Universality Across Domains2425| Domain | COLLABORATE Applies To | Core Operation |26|--------|----------------------|----------------|27| **Medicine** | Surgical teams, care coordination, specialist consultation | Coordinate surgeon, anesthesiologist, nurses toward patient outcome |28| **Business** | Department coordination, cross-functional teams, partnerships | Coordinate sales, marketing, product toward revenue goals |29| **Science** | Research collaboration, multi-institution studies, peer review | Coordinate multiple labs toward research publication |30| **Education** | Team teaching, curriculum development, assessment design | Coordinate teachers across subjects toward learning goals |31| **Manufacturing** | Assembly line coordination, supply chain, quality teams | Coordinate production, logistics, QA toward delivery |32| **Software** | Pair programming, code review, microservices orchestration | Coordinate developers, services toward feature delivery |33| **Law** | Legal team coordination, co-counsel, expert witnesses | Coordinate attorneys, paralegals, experts toward case strategy |34| **Architecture** | Design team, engineering coordination, contractor management | Coordinate architects, engineers, contractors toward building |3536### The Universal Pattern3738```39Independent Work → Parallel Composition → Merged Result40 (Agents) → (Applicative) → (Outcome)41```4243**Historical Precedent**:44- **Ancient Building**: Pyramid construction (coordinated labor - 2560 BCE)45- **Military**: Roman legion coordination (centurions + legates - 100 BCE)46- **Industrial**: Assembly line coordination (1913)47- **Software**: Microservices orchestration (2010s)4849The function is eternal; the coordination mechanisms change.5051### Why This Works Universally52531. **Applicative Structure**: Independent agents compose via `<*>` operator542. **Parallel**: Agents work independently, results merge deterministically553. **Compositional**: Coordination of coordination (meta-collaboration)564. **Role-based**: Clear agent roles, interfaces, handoffs5758Surgical team coordination = Software team coordination. Same structure, different agents.5960---6162## When to Use This Skill6364- 👥 **Coordinate teams** - Multiple agents working toward shared goal65- ⚡ **Parallel execution** - Independent work that merges66- 🔄 **Role management** - Define agent responsibilities, interfaces67- 📊 **Merge results** - Combine outputs from parallel agents68- 🎯 **Shared context** - All agents work from same base state6970---7172## Building Foundations for Your Domain7374**Universal Function = Eternal Structure + Domain Foundations**7576COLLABORATE is an eternal categorical structure (Applicative + Parallel). To use it in YOUR domain, construct **domain foundations** - agent roles, communication protocols, and merge strategies.7778### The Pattern7980```81COLLABORATE (Universal Applicative)82 ⊗83Domain Foundations (Roles + Protocols)84 =85Domain Implementation86```8788### Foundations by Domain8990| Domain | Foundations to Construct | Examples |91|--------|-------------------------|----------|92| **Medicine** | Team roles, handoff protocols, communication standards | Surgeon/anesthesiologist roles, SBAR protocol |93| **Business** | Department roles, meeting cadence, reporting | Sales/marketing roles, weekly syncs, dashboards |94| **Software** | Service boundaries, API contracts, event schemas | **CC2.0 provides**: Agent protocols, message schemas |95| **Manufacturing** | Station roles, quality gates, inventory handoffs | Assembly stations, inspection points, JIT delivery |96| **Education** | Teacher roles, curriculum alignment, assessment sharing | Subject specialists, standards mapping, grade sync |97| **Science** | Lab roles, data protocols, authorship guidelines | PI/postdoc roles, data formats, co-authorship |98| **Law** | Attorney roles, document sharing, privilege protocols | Lead/co-counsel, discovery sharing, privilege logs |99| **Architecture** | Discipline roles, drawing coordination, change orders | Architect/engineer, BIM coordination, RFIs |100101---102103## Related Skills104105- **cc2-observe**: Provides shared context for all agents106- **cc2-reason**: Generates collaborative strategies107- **cc2-create**: Agents create different artifacts in parallel108- **cc2-verify**: Validates merged results from collaboration109- **cc2-orchestrator**: Orchestrates complex multi-agent workflows110111---112113## File References114115**Implementation**: `${CC2_HOME}/src/functions/collaborate/CollaborateFunction.ts` (380 lines)116**Tests**: `${CC2_HOME}/tests/laws/collaborate-parallel.test.ts`117**Documentation**: `${CC2_HOME}/functions/collaborate/FUNCTION.md`118119---120121**Status**: ✅ Production-Ready122**Categorical Rigor**: L5 (Pragmatic with parallel composition)123**Test Coverage**: 100% (all parallel composition laws verified)124125---126127*"To collaborate is to transform individual effort into collective achievement, to bridge isolation and coordination. COLLABORATE is the applicative that makes parallel work convergent."*128129— **CC2.0 Categorical Foundations**
manutej