# Ecosystem Marketplace Unification

> **Status:** Draft
> **Owner:** `learning_ai_common_plat`
> **Purpose:** Define one marketplace model for reusable ecosystem assets across products.

---

## 1. Problem

Marketplace-like concepts already exist or are implied across the ecosystem:

- JarvisJr agent marketplace ideas
- Cowork plugin marketplace
- Note templates
- FlowMonk workflows
- ChronoMind routines
- EffoRise programs
- prompt packs, skill packs, department agents

Without one shared marketplace model:

- assets are siloed by product
- monetization is fragmented
- entitlement logic is duplicated
- creators cannot publish once and reach multiple products

---

## 2. Goal

Create one inventory and entitlement model that can support multiple asset types while allowing product-specific presentation.

---

## 3. Canonical Inventory Types

The marketplace should support at least:

- `agent`
- `plugin`
- `connector`
- `skill-pack`
- `prompt-pack`
- `workflow-template`
- `note-template`
- `routine-pack`
- `habit-program`
- `review-template`

Each listing should declare:

- `listingId`
- `inventoryType`
- `title`
- `summary`
- `publisher`
- `supportedProducts`
- `deliveryMode`
- `version`
- `entitlementModel`

---

## 4. Delivery Modes

Supported delivery modes should include:

- config-only
- document/template bundle
- runtime plugin
- connector integration
- agent behavior pack
- prompt or skill bundle

---

## 5. Phase-1 Scope

Start with these inventory types:

- [ ] `plugin`
- [ ] `workflow-template`
- [ ] `note-template`
- [ ] `routine-pack`
- [ ] `skill-pack`

These map directly to existing ecosystem capabilities.

---

## 6. First Adopters

1. `oss/learning_ai_claw-cowork`
2. `learning_ai_flowmonk`
3. `learning_ai_notes`
4. `learning_ai_clock`
5. `learning_ai_jarvis_jr`

---

## 7. Open Decisions

1. Should one listing support multiple delivery modes?
2. Should entitlement be product-scoped or ecosystem-scoped by default?
3. How should version compatibility be represented across products?
4. Which assets require review/signing before distribution?

---

## 8. Acceptance Criteria

1. One creator asset can target more than one product.
2. Platform entitlements can gate access without per-product duplication.
3. Cowork marketplace assets can map into the shared listing model.
4. Product-specific presentation does not require product-specific listing storage.

---

## 9. Implementation Checklist

- [ ] define canonical listing schema
- [ ] define inventory type taxonomy
- [ ] define entitlement model
- [ ] define compatibility/version model
- [ ] define phase-1 publishing workflow
- [ ] define review/signing requirements

Commits:

- `7a86a76` drafted the initial version
