progit-plugin-sdk 0.2.1

# Plugin Licensing Guide

This document explains the licensing model for the ProGit plugin ecosystem.

---

## TL;DR for Plugin Developers

**You can use ANY license for your plugin**, including fully proprietary.

This is possible because:

1.  Your plugin links against the **Plugin SDK**, which is **LSL-1.0 (Sovereign)**.
2.  The SDK's "Commercial Bridge" clause allows proprietary Larger Works.
3.  Your plugin is loaded at **runtime** (LuaJIT/WASM), not statically linked to the Core.

The copyleft nature of the ProGit Core (**LCL-1.0**) does **not** extend to plugins.

---

## The License Suite

| Component | License | What It Means for You |
|-----------|---------|----------------------|
| **ProGit Core** (`prog` binary) | **LCL-1.0** (Commonwealth) | Strong copyleft. You cannot use Core code directly. |
| **This SDK** (`progit-plugin-sdk`) | **LSL-1.0** (Sovereign) | File-level copyleft. Your app code stays yours. |
| **Plugin Marketplace** (future) | **LUL-1.0** (Unbound) | Permissive. Infrastructure is open. |
| **Your Plugin** | **Your Choice** | ANY of the 4 Libertaria licenses, or proprietary. |

---

## Recommended Licenses for Plugins

| Your Goal | Recommended License |
|-----------|---------------------|
| Maximum community adoption | **LUL-1.0** (Unbound) |
| Shared engine improvements | **LSL-1.0** (Sovereign) |
| Full open-source commitment | **LCL-1.0** (Commonwealth) |
| Commercial / Closed-source | **LVL-1.0** (Venture) or **Proprietary** |

---

## How to Apply Your License

1.  Create a `LICENSE` file in the root of your plugin repository.
2.  Copy the full text of your chosen license (see `/legal/` directory for templates).
3.  Update your `Cargo.toml` (if Rust) or manifest file with the license identifier.

---

*"Communal Core. Individual Profit."*