# Ecosystem Ownership Matrix

> **Status:** Hardened temporary model
> **Owner Model:** temporary four-party operating model
> **Parties:** Saravana, Codex, Windsurf, Cursor
> **Purpose:** Clarify who owns what for ecosystem planning, implementation, review, and tracking.

---

## 1. Current Operating Reality

For now, the ecosystem is effectively operated by four parties:

1. **Saravana**
   Product owner, final technical decider, integration sponsor, and release authority.
2. **Codex**
   High-power architecture and implementation driver for complex cross-repo work.
3. **Windsurf**
   Medium-power execution partner for bounded implementation, iterative follow-through, and repo-local work.
4. **Cursor**
   Lower-power execution and assistance layer for narrower or more guided tasks.

This document assumes no larger team structure exists yet.

---

## 2. Role Definitions

### Saravana

Own:

- final priorities
- architectural direction approval
- repo strategy decisions
- acceptance of cross-product behavior changes
- release/push/go-live calls

### Codex

Own:

- ecosystem architecture
- shared-contract definition
- cross-repo sequencing
- difficult implementation plans
- higher-risk refactors and integration strategy
- documentation system-of-record quality

### Windsurf

Own:

- bounded implementation chunks
- repo-local follow-through
- structured doc updates
- medium-complexity verification and completion loops

### Cursor

Own:

- smaller scoped implementation assistance
- local productivity tasks
- narrow edits under strong guidance
- low-risk follow-up changes

---

## 3. Responsibility Matrix

| Work Type                          | Saravana | Codex | Windsurf | Cursor |
| ---------------------------------- | -------- | ----- | -------- | ------ |
| ecosystem strategy                 | A        | R     | C        | C      |
| shared contracts                   | A        | R     | C        | C      |
| cross-repo implementation planning | A        | R     | C        | C      |
| high-complexity integration work   | A        | R     | C        | I      |
| medium repo-local implementation   | C        | C     | R        | I      |
| low-risk guided edits              | C        | C     | C        | R      |
| tracker and commit-link hygiene    | A        | R     | C        | C      |
| final push/go-live decision        | A        | C     | I        | I      |

Legend:

- `A` = accountable
- `R` = responsible
- `C` = consulted
- `I` = informed

---

## 4. Repo Ownership Bias

This is not exclusive ownership. It is the default lead bias.

| Repo Area                                 | Default Lead                      |
| ----------------------------------------- | --------------------------------- |
| `learning_ai_common_plat/docs/ecosystem/` | Codex                             |
| shared contract docs                      | Codex                             |
| implementation tracker updates            | Codex                             |
| product-local adoption docs               | Windsurf or Cursor under guidance |
| final prioritization and acceptance       | Saravana                          |

---

## 5. Practical Rules

1. If a change affects more than one repo or defines a shared contract, Codex should lead.
2. If a change is bounded to one repo and the contract is already clear, Windsurf can lead.
3. Cursor should be used only for narrower, strongly-scoped work until the ecosystem contracts harden further.
4. Saravana remains the final authority on tradeoffs and sequencing.
5. Every major ecosystem task should be visible in the tracker with one clear owner.

## 6. Revision Trigger

This ownership model must be revised when any of these become true:

1. the working team grows beyond Saravana, Codex, Windsurf, and Cursor
2. one product repo gains a stable long-term owner outside the current four-party group
3. release authority becomes shared across multiple humans
4. approval, security, or infra ownership becomes operational rather than ad hoc

If one of those happens, update this document in the same change series that updates:

- `ECOSYSTEM_AGENT_OPERATING_MODEL.md`
- `ECOSYSTEM_IMPLEMENTATION_TRACKER.md`
- the relevant adoption docs

## 7. Next-State Ownership Shape

If the team expands, the preferred next structure is:

- `Saravana`
  - product direction
  - release authority
  - final acceptance
- `Codex`
  - shared architecture
  - ecosystem contracts
  - cross-repo integration review
- `Repo leads`
  - one accountable human or agent owner per active product repo
- `Execution agents`
  - bounded implementation, verification, and documentation updates under the shared operating model

See also:

- [`ECOSYSTEM_AGENT_OPERATING_MODEL.md`](/Users/saravana/BytelystAI/learning_ai/learning_ai_common_plat/docs/ecosystem/ECOSYSTEM_AGENT_OPERATING_MODEL.md) for the detailed delegation, review, merge, and parallelization process.

---

## 8. Implementation Checklist

- [x] confirm this temporary four-party ownership model
- [x] add handoff conventions between Codex, Windsurf, and Cursor
- [x] define revision triggers if the team structure changes
- [ ] add repo adoption owners when active ownership expands beyond the current four-party model
- [ ] revise this doc if the team structure changes

Commits:

- `41fa2cd` drafted the initial version
- `7a86a76` updated the ownership language to Saravana
- `765568f` linked ownership to the detailed operating model
- `065c025` tracked ownership revision as remaining work