# SNSL 2.1 Builder & Contributor Guide

**Explanatory Reference Guide — Operative Legal Terms Reside in [SNSL 2.1](LICENSE) and Applicable Signed Instruments**
**License Version:** `SNSL-2.1` (`sha256: d1e78d64a54e95d41a200cde2e3057ecb6e5f9146ad99c3eb4d92ff0136ae6f7`)
**Effective Date:** November 17, 2026

The SagaHalla Network Source License (`SNSL 2.1`) is a **network-restricted source-available license** paired with a **staged contributor-governance and ownership framework**. It is not OSI-approved open source: active source access and runtime redistribution follow authenticated membership in an Authorized Network (`SagaHalla Network` or `Aregis Network`), while giving builders and contributors strong protections for independent applications, AI model-training opt-in, workspace privacy, durable attribution, and post-departure operational continuity.

---

## 1. Builder Permissions at a Glance

| What You Want to Do | Allowed? | Key Conditions & Sections |
| --- | --- | --- |
| **Read source, run locally, test, benchmark & deploy internally** | **Yes** | Requires active **Member in Good Standing** status for the designated repository/product (`§§4–5`). |
| **Build & sell independent apps, websites, or workflows generated with GAME or Saga Agent** | **Yes — Unrestricted** | Generated application code, configs, schemas, and work product are **yours**—not `Licensed Material` or `Derived Works`—and carry **zero** `§7.2` patch-back or `§23` distribution limits (`§§6.2(1), 23.1(1)`). |
| **Build & sell commercial plugins, MCP/A2A/ACP tools, or extensions** | **Yes — Unrestricted** | Independent extensions communicating over published APIs, wire protocols, or `Schedule G` permissive SDKs are excluded from contribution-back and redistribution limits (`§§6.2(2), 7.3, 22, 23.1`). |
| **Operate a managed SaaS, agency, or consulting service for non-Member clients** | **Yes** | Allowed under `§6` where you remain the operator, your membership tier permits commercial use, you do not offer an unauthorized `Competing Offering` (`§3.6`), and clients receive outputs rather than protected source/runtime. |
| **Ship an application that bundles an unmodified SNSL runtime / daemon** | **Yes — Via Profile** | Covered by standardized `Schedule H` **Embedded Runtime Distribution Profiles** (`§23.2`, e.g., end-user seat/token authentication) or a separate OEM agreement. |
| **Experiment privately with core SNSL modifications** | **Yes** | Private branches, local prompts, reasoning traces, and unpromoted Work Capsules stay private (`§§7.1, 14.2A`). |
| **Run modified core SNSL code in Production Use** | **Yes — 30-Day Patch-Back** | Modifications to protected Licensed Material used in Production Use must be contributed back within **30 days** (`§7.2`), with a confidential deposit option if client secrets are involved (`§§7.4–7.4A`). |
| **Build competing software independently** | **Yes** | Independent development and market competition are expressly protected (`§§3.6, 21.1`); only copying/deriving from protected implementation or `Non-Public Network Material` is barred (`§20.2`). |
| **Publish or redistribute core SNSL source/binaries to the general public** | **No** | External redistribution of protected Licensed Material requires a `Schedule G` component license or `Schedule H` profile (`§§22–23`). |

---

## 2. Four Standardized Commercial & Distribution Profiles (`§§6, 22, 23, Schedule G/H`)

To eliminate per-application legal friction when building at scale with **Saga Agent** and **Saga GAME**:

1. **Profile 1 — Independent Application / Generated Output (`§§6.2, 7.3, 23.1`):**
   * *Architecture:* Standalone software, web/mobile apps, smart contracts, schemas, or plugins generated, planned, or verified using GAME/Saga Agent, or linking solely against published protocol envelopes (`MCP`, `ACP`, `A2A`) and `Schedule G` permissive SDKs.
   * *Distribution:* **100% builder-controlled.** License under MIT, Apache-2.0, or proprietary terms; sell to anyone; no runtime royalties, no non-Member customer restrictions, and no contribution-back.
2. **Profile 2 — Builder-Operated SaaS & Client Services (`§§6, 6.1`):**
   * *Architecture:* You host and operate Saga Agent or GAME internally (or in your controlled cloud) under a commercial-eligible membership tier to deliver vertical SaaS outcomes, managed AI workflows, or consulting deliverables to non-Member clients.
   * *Distribution:* Clients use your application/outputs without needing Network membership, provided you do not expose raw protected source/binaries or rehost a generic `Competing Offering`.
3. **Profile 3 — Embedded Runtime / Seat-Authenticated App (`§23.2, Schedule H`):**
   * *Architecture:* Desktop, on-prem, or containerized applications that bundle an unmodified signed `saga-agent` or `GAME` runtime component.
   * *Distribution:* Redistributable under a published `Schedule H` Embedded Runtime Profile where Production Use activates upon the end customer binding an active Network seat, runtime token, or enterprise entitlement.
4. **Profile 4 — Enterprise Self-Hosted / Custom Modification (`§§4, 7.5, Schedule H`):**
   * *Architecture:* Enterprise customers hosting full SNSL source/runtimes internally, optionally with private modification carve-outs (`§7.5`).
   * *Distribution:* Direct Enterprise Network Membership or bilateral `Schedule H` commercial agreement.

---

## 3. Contributor Rights, AI Training Shield & Post-Departure Continuity

What happens when you contribute code, specifications, or verification artifacts to an SNSL 2.1 repository?

| Dimension | Voluntary / Reciprocity Contribution (`§§7, 8.2`) | Pre-Signed `S12` Equity-Eligible Work (`§8.6`) |
| --- | --- | --- |
| **Copyright Ownership** | **Retained by Contributor** (`§8.1`). | **Retained by Contributor** (`§8.1`). |
| **Inbound License Timing** | Perpetual, worldwide Network + commercial license starts on intentional submission (`§8.2`). | **Confidential assessment/testing only at intake**; commercial license triggers **only upon objective acceptance** (or neutral S12.5 ruling), which simultaneously binds equity admission (`§8.6`). |
| **AI Model Training & Distillation** | **Prohibited by default (`§20.1(b)`).** Zero training, fine-tuning, or synthetic data generation on your code, docs, prompts, or Work Capsules unless you explicitly opt in via `Schedule E` (revocable prospectively on 30 days' notice under `§20.1(b1)`). | **Prohibited at intake and after acceptance** unless you separately opt in under `§20.1(b)–(b1)` (`§20.1(f)`). |
| **Workspace & Agent Privacy** | Local `.saga-agent/` state, prompts, and unpromoted Work Records are protected as `Private Refinement` by construction (`eSRA`); warrantless daemon telemetry scraping is barred (`§§3.3A, 14.2A`, `Schedule J`). | Same full `eSRA` and Bound Saga-Agent constitutional-inspired contractual protections (`§§3.3A, 14.2A`). |
| **Provenance & Earned Standing** | Durable authorship attribution (`§9`) and earned `§11` Network Benefits **survive departure** (`§27.6`). | Durable attribution + binding `S12` conversion claim survive departure (`§27.6`, `S12.3`). |
| **Post-Departure Runtime Continuity** | Once your contribution becomes an **Accepted Contribution** in an official release, if you later leave without breach you keep **perpetual Pinned-Release Operational Continuity** (runtime + `§25.1` patents) to run that release for existing deployments (`§27.4A`). | Same **perpetual Pinned-Release Operational Continuity** (`§27.4A`) plus **180-day** general wind-down (`§27.4`). |
| **Retroactive License Changes** | **Blocked (`§28`).** Later SNSL versions never apply to already-licensed material without affirmative acceptance. | **Blocked (`§§28, 28.1`).** Protected Contributor Rights cannot be waived by third-party commercial side deals. |

---

## 4. Two-Layer Governance Status (`§1.1` & `§44.4` Truth-in-Licensing)

* **Layer 1 — Immediate Baseline Protections (Active Today):** All permissions and safeguards in Sections 1–3 above—including **180-day non-breach wind-down (`§27.4`)**, **perpetual Pinned-Release Operational Continuity for Accepted Contributors and 12+ month Members (`§27.4A`)**, **generated-app safe harbors (`§§6.2, 23.1`)**, **opt-in-only AI training (`§20.1`)**, **eSRA workspace privacy (`§14.2A`)**, and **fair-admission / independent competition rules (`§§4.3, 21.1`)**—are legally operative immediately upon repository adoption of `SNSL-2.1`.
* **Layer 2 — Companion Ownership & Decentralization Schedules (`S12`, `S13`, `S13A`, `Schedule I`):** The contractual pathway to individual contributor equity conversion (`State A`) and progressive contributor governance culminating in **$\ge 51\%$ independent contributor voting and fully diluted economic ownership (`State E`, `§11.2`)** requires entity-specific completion and independent verification of Adoption Register gates `A1`–`A8` (`Schedule I`, `§44.4`). Until `Schedule I` is executed and published for a specific entity, ownership conversion is not advertised as active for that entity.
