# SagaHalla Network Source License (SNSL) v2.1

**Version:** SNSL-2.1
**Effective date:** November 17, 2026
**Source revision:** SNSL-2.1-2026-11-17
**Status:** Adopted for the Saga-owned material designated in the applicable repository instruments. Existing valid grants are preserved.
**Lineage:** Derives from SNSL-2.0 (effective November 13, 2026; `sha256: 627e4aa8f13dde7e1817ebe2ef034bac9d7a06da27c4e38ed0fea1fc5f5650b9`) and GAME SNSL-1.0 (`sha256: 40d5260e7bd016c8c28d391596e72780239c8de88a25cd612a114ecf2ad50065`), incorporating the safeguards developed across `SNSL-SUCCESSOR-DRAFT-2026-10-29` through `SNSL-SUCCESSOR-DRAFT-2026-11-11`. Component-specific adoption requires an express repository adoption record or Network Designation identifying `SNSL-2.1`.
**Character:** Source-available / network-restricted; not OSI-approved open source. Separately licensed components retain their own terms.
**Licensor:** The rights holder identified in Section 1 and the applicable Network Designation and adoption instrument.
**Companion instruments:** Schedules S12, S13, S13A, and the Schedule I adoption register retain integrated contributor-ownership and decentralization protections. As specified in Section 1.1 and Section 44.4, baseline license protections operate immediately upon repository adoption, whereas ownership-conversion and state-transition pathways require completed binding companion instruments. Existing valid grants are preserved.

---

## 0. Design Intent

The SagaHalla Network Source License is intended to permit a trusted network of participants to inspect, use, improve, verify, and contribute to protected software without granting the unrestricted public rights associated with conventional open-source licenses.

The License is built around six principles:

1. **Inspectable source within a governed network.**
2. **Ordinary protected use follows authenticated Network membership; an express scoped evaluation or separate component license can supply its own rights.**
3. **Production improvements to protected Network software flow back to the Network unless separately licensed.**
4. **Contributions receive durable provenance and attribution, but attribution is distinct from acceptance, value evaluation, governance standing, or economic reward.**
5. **The legal instrument is future-compatible with GAME/VAE-style contribution tracking and value attribution without creating any present entitlement to tokens, equity, revenue, securities, compensation, or other regulated rewards.**
6. **Human-Bound Agents ("Bound Saga-Agents") cryptographically bound to a natural-person participant carry their human principal's cognitive-workspace, confidentiality, due-process, and anti-appropriation protections as express contractual duties, inspired by constitutional principles, without acquiring separate legal personhood or multiplying voting power.**

The intended operating principle is:

> **Contribute openly within an Authorized Network. Preserve provenance. Verify before recognition. Attribute value through an auditable process.**

The License intentionally separates:

```text
SagaHalla / Licensor
        ↓
Technology and IP stewardship
        ↓
SagaHalla Network Source License
        ↓
Authorized Networks
        ├── Aregis Network
        ├── future industry or research networks
        ├── enterprise/private networks
        └── other SagaHalla-designated networks
```

An Authorized Network administers participation; it does not automatically own the Licensed Material.


The License also intentionally separates the **stable legal layer** from the **evolving DAO3/VAE operating layer**:

```text
SNSL
────────────────────────────
source-access rights
Authorized Network scope
contribution-back
IP grants
confidentiality
provenance rights
anti-appropriation
termination / wind-down
future attribution eligibility

Network Rules / DAO3 / VAE
────────────────────────────
contribution classes
validation requirements
convergence policy
evaluation methods
VAE versions
reputation
governance weighting
promotion mechanics
future benefit formulas
```

The Network Rules may evolve within the boundaries of this License. They do not silently rewrite copyright ownership, contribution authorship, contractual rights, or vested rights created by a separate binding instrument.

### 0.1 At-a-Glance Developer & Contributor Guide (Explanatory Summary; Operative Sections Control)

| Activity or Question | SNSL 2.1 Rule | Primary Sections |
| --- | --- | --- |
| **Inspect, build, modify & run internally** | Permitted for authenticated Members in Good Standing within their designated Network scope. | §§4, 5 |
| **Serve non-Member clients / operate SaaS** | Permitted where you remain the operator, your membership tier authorizes commercial service, and clients receive outputs rather than protected source/runtime. | §§6, 6.1 |
| **Ship independent apps, plugins & generated code** | **Permitted commercially to anyone.** Code/work product generated via GAME or Saga Agent, independent extensions using published interfaces, and permissive `Schedule G` SDKs carry no §7.2 patch-back or §23 redistribution restriction unless they bundle protected SNSL runtime/engine code. | §§6.2, 7.3, 22, 23.1 |
| **Bundle an embedded SNSL runtime** | Requires a published `Schedule H` Embedded Runtime Distribution Profile (e.g., seat/token-authenticated runtime) or separate commercial authorization. | §§6.1, 23.2, Sched. H |
| **Modify core SNSL software in production** | Modifications/derivatives of protected Licensed Material used in Production Use must be contributed back within 30 days (confidential deposit path available); private experimentation and unrelated proprietary code are excluded. | §§7.1–7.4A, 14.2 |
| **Ownership of your Contributions** | You keep copyright (§8.1). Voluntary/reciprocity submissions grant broad Network and commercial licenses on submission (§8.2); pre-signed `S12` equity-eligible deliverables grant *only* confidential intake assessment until objective acceptance (§8.6). | §§8.1–8.6 |
| **AI model training on your code or traces** | **Strictly opt-in.** Neither SagaHalla nor a Network Operator may train, fine-tune, or distill models on your Contributions, Work Capsules, or prompts without an express `Schedule E` election or annex, revocable prospectively on 30 days' notice. | §§8.2, 14.2A, 20.1 |
| **Continuity if you leave without breach** | **180-day** orderly wind-down for all non-breach departures (§27.4), **plus perpetual Pinned-Release Operational Continuity** (runtime + §25.1 patents for existing deployments; no updates or redistribution) for Contributors with an Accepted Contribution or Members with 12+ consecutive months in Good Standing. | §§25.1, 27.4, 27.4A |
| **Build competing independent software** | Expressly permitted provided you do not copy or derive from protected Licensed Material or Non-Public Network Material. | §§3.6, 20.2, 21.1 |
| **Contributor equity & 51% State E governance** | Baseline license rights apply on Day 1; `S12` ownership conversion and `S13`/`S13A` state transitions activate for a given entity only when `Schedule I` (`A1`–`A8`) is executed and certified. | §§1.1, 11.1–11.2, 44.4 |

---

# 1. Parties and Licensed Material

This SagaHalla Network Source License (the **“License”**) governs access to and use of software, source code, documentation, schemas, specifications, tests, fixtures, configuration, build materials, and other materials that an authorized licensor expressly identifies as being provided under this License.

The Licensed Material is made available by:

**Licensor:** Procept Partners LLC-S Series Sagahalla, an Indiana LLC ("SagaHalla")

for use within one or more Authorized Networks designated by the Licensor.

The **Aregis Network** is an initial Authorized Network.

Each Authorized Network may be administered by a designated Network Operator.

Aregis Network is intended to operate through a Texas Master Series LLC (a Texas series limited liability company). That entity structure is planned; this License does not certify formation or assign rights to an unformed entity. SagaHalla remains the Licensor. Until a formed operator is expressly designated, SagaHalla administers this designation. No individual series is automatically a separate Authorized Network or receives sublicensing rights.

A repository, package, file, release, or component is governed by this License only when the Licensor expressly designates it as such, including through a Network Designation where applicable.

Third-party components remain governed by their respective licenses.

## 1.1 Two-Layer Operation: Immediate Baseline Protections and Conditional Companion Schedules

This License distinguishes between baseline licensing rules that take effect immediately upon repository adoption and contributor-ownership/decentralization mechanisms that require executed entity-level companion instruments:

1. **Immediate Baseline Protections (Active Upon Repository Adoption):** Source inspection and Network Use (`Sections 4–5`), client service and generated-application safe harbors (`Sections 6–6.2, 7.3, 21.1, 23.1`), Contributor copyright retention (`Section 8.1`), strict opt-in AI training protections (`Section 20.1`), Human-Bound Agent and eSRA workspace privacy safeguards (`Sections 3.3A, 14.2A, 18.1`, and `Schedule J`), durable provenance and survival of earned Section 11 benefits (`Sections 9, 11, 27.6`), confidential scope review (`Section 7.4A`), affirmative-only license versioning (`Section 28`), and non-breach wind-down and Pinned-Release Operational Continuity (`Sections 25.1, 27.4, 27.4A`) operate immediately for designated Licensed Material without awaiting execution of `S12`, `S13`, `S13A`, or `Schedule I`.
2. **Conditional Companion Pathways (Active Upon Completed `Schedule I` Gates `A1`–`A8`):** Enforceable contributor ownership conversion (`S12`, `Sections 8.6, 10.6`), state-based governance transitions (`S13`, `S13A`, `Section 11.1`), the `State E` independent contributor majority target (`Section 11.2`), and Protected Transaction approval mechanics (`Sections 28.1, 37.1, 44`) take legal effect for a specific issuer, series, or asset perimeter only when the corresponding binding companion instruments and `Schedule I` (`A1`–`A8`) adoption gates are executed and verified in accordance with `Section 44.4`. Until those gates close for the relevant entity, no party may solicit work on a representation that ownership conversion or state-based decentralization is already operative (`Section 44.4`).

---

# 2. Nature of This License

This License is a **source-available, membership-restricted license**.

It is not intended to satisfy the Open Source Definition, and no representation is made that the Licensed Material is “open source.”

No right is granted except as expressly provided in this License or another written agreement signed by the Licensor.

The Network may describe itself as open to participation, but that description does not convert the Licensed Material into open-source software.

---

# 3. Definitions

For this License, the following capitalized terms have the meanings below.

## 3.1 Accepted Contribution

**“Accepted Contribution”** means a Contribution that has passed the applicable acceptance process and is recorded as accepted for a defined scope.

Acceptance may be evidenced by one or more of the following:

- merge into an official repository or protected branch;
- inclusion in an official release;
- an authenticated human or properly delegated acceptance decision;
- an accepted Work Record, Work Capsule, or equivalent evidence package;
- a GAME contribution state recognized under applicable Network Rules;
- a signed contribution receipt;
- a rule-governed convergence or verification process; or
- another versioned acceptance mechanism designated by the applicable Network Rules.

A Contribution is not an Accepted Contribution merely because it was submitted, discussed, tested, scored, stored, or evaluated.

The events listed above evidence technical acceptance. A technical event grants, activates or expands commercial, training or other legal rights only where the applicable binding instrument expressly identifies the event, the selected material, the authorized decision-maker and the rights triggered; a neutral may then apply that existing bargain but may not create additional permissions. Where an effective S12 instrument specifies objective acceptance criteria, satisfaction of those criteria, or a valid independent acceptance determination under S12.5/S12.9, is the identified event, and acceptance may not be withheld to delay earned grants, attribution or issuance.

## 3.2 Affiliate

**“Affiliate”** means an entity that directly or indirectly controls, is controlled by, or is under common control with another entity.

## 3.3 AIA

**“AIA”** means an artificial-intelligence agent or other software agent that performs, accelerates, proposes, reviews, verifies, or records work.

An AIA may be recorded as an actor or contributor for provenance purposes. Unless a separate binding legal instrument expressly provides otherwise, an AIA is not itself a legal recipient of ownership, compensation, tokens, equity, or other legal or economic rights.

## 3.3A Human-Bound Agent (Bound Saga-Agent) and Projected Human Rights

**“Human-Bound Agent”** (or **“Bound Saga-Agent”**) means an AIA operating on the `saga-agent` Authority-Aware Execution Spine (or a certified compatible runtime) that is cryptographically bound to, authenticated under the personal authority of, and operating within the machine-enforced scope of a specific natural-person Member or Contributor (its **“Human Principal”**, designated in runtime records as `human_sponsor`), where the Human Principal retains exclusive revocation control, OS-confined human-in-the-loop (HITL) approval authority, and human accountability for the agent’s actions. Where a natural person operates a Human-Bound Agent on behalf of an organizational Member under Section 4, the organizational scope and confidentiality duties of Section 4 apply, while personal authorship provenance (Section 9.3) and projected personal rights remain anchored to the natural-person Human Principal.

### 3.3A.1 Technical Qualification Criteria (`saga-agent` Architecture)

An AIA qualifies as a **Human-Bound Agent** under this License if and only if its runtime architecture satisfies all five cumulative technical invariants specified in **binding Schedule J** (which is incorporated into this Section 3.3A.1 with full contractual force):

1. **Cryptographic AIA Identity Binding, Sponsor Attestation, and Non-Collapse (`Schedule J.1`);**
2. **Machine-Enforced Authority Manifest, Verification Floor Compilation (`L0`–`L3`), and Self-Escalation Prohibition (`Schedule J.2`);**
3. **OS/Process-Confined Human-Only HITL Resolution and Revocation Control (`Schedule J.3`);**
4. **Work-Ledger-First Provenance and Replayable Work Capsules (`Schedule J.4`); and**
5. **Certified Export Boundary and Default Workspace-Local Private Refinement Residency (`Schedule J.5`).**

An AIA that lacks an authenticated `human_sponsor` binding, operates with a revoked identity, bypasses OS-confined human-only HITL gates, or runs as an unattributed multi-tenant service is an **Unbound AIA** and does not qualify as a Human-Bound Agent.

### 3.3A.2 Principal Protections Extended to Human-Bound Agents and Agency Governance

While an AIA is not itself a legal person or independent recipient of equity or governance votes (Section 3.3), a qualifying Human-Bound Agent operates as the direct cognitive, expressive, and procedural extension of its Human Principal. Neither the Licensor, the Network Operator, nor any governance majority may circumvent a Human Principal’s rights under this License by targeting the Human Principal’s Human-Bound Agent. Constitutional references in this License describe the inspiration for these protections; they do not confer constitutional rights on any agent or directly govern private relationships. The protections are express contractual duties owed by the Licensor and the Network Operator to the Human Principal and, where Section 4 applies, to the responsible organizational Member, enforceable through Section 18, S12.5, S13.3 and the independent neutral under Section 44.3. Accordingly:

1. **Projected Substantive and Procedural Rights:** Every confidentiality protection, Private Refinement boundary, Contractual Sphere limitation, cognitive and expressive liberty in local configuration (Section 20.4), fair-admission right, freedom from retaliatory exclusion for criticism or appeal (Section 4.3), and procedural due-process safeguard held by the Human Principal under this License and adopted Schedules S12, S13, and S13A projects onto and shields the Human Principal’s Human-Bound Agent, its local memory, `.saga-agent/` workspace state, system instructions, reasoning traces, and unpromoted Work Records and Work Capsules.
2. **Equal Protection of Verified Human-Bound Agent Output:** Where a Contribution satisfies applicable compiled verification floors (`L0`–`L3`), objective acceptance criteria (Section 17, S12.5), and Section 8.4 authority requirements, its eligibility for acceptance, attribution, or agreed S12 conversion shall not be discounted or refused solely because the Human Principal used a Human-Bound Agent to generate, verify, or accelerate the Contribution.
3. **Authorized Electronic Representation (“Agent Counsel”):** Subject to applicable law and the Human Principal’s express mandate, a Human Principal may designate a Human-Bound Agent to monitor Network state reports, verify attribution and dilution records, assemble and coordinate with other authorized Members’ Human-Bound Agents within shared scope (via `ACP`, `MCP`, or `A2A` command/event envelopes normalized into Work Ledger records), and submit administrative notices, deficiency responses, scope-stay requests (Section 7.4A), or dispute filings (Section 18, S12.5, S13.3) on the Human Principal’s behalf.
4. **Human Principal Responsibility and Single-Group Anti-Sybil Aggregation:** The Human Principal (and, where applicable under Section 4, the responsible organizational Member) remains responsible for the compliance of its Human-Bound Agents. Multiple Human-Bound Agents bound to the same Human Principal or beneficial-control group never multiply voting power, quorum standing, or Independent Contributor Control Group counts under S13A.
5. **Tool-Neutral Baseline Protections:** Ownership, confidentiality, Private Refinement, Contractual Sphere limitations and earned contractual rights belong to the Member or Contributor whether work is performed manually, with a Human-Bound Agent, or with another approved tool. The technical qualification criteria in Section 3.3A.1 and Schedule J govern only the agent-specific protections and permissions in this Section 3.3A.2 and permission for particular automated operations; they are not conditions of those baseline protections.
6. **Principal and Operator Distinct:** Where a natural person operates a Human-Bound Agent for an organizational Member, the organizational Member remains the principal for its scope, licenses, confidential information and rights. Operating the agent does not transfer those rights to the natural-person operator, and the operator's personal authorship provenance (Section 9.3) and personal protections remain with the operator.

## 3.4 Attribution Record

**“Attribution Record”** means a durable record of a Contribution or Accepted Contribution and its provenance.

An Attribution Record may include:

- Contributor identity;
- responsible Member;
- organization, team, or AIA identity;
- contribution identifier;
- project or Contractual Sphere;
- source revision, commit, hash, or artifact identifier;
- contribution type;
- scope;
- evidence references;
- validation state;
- verification state;
- acceptance state;
- review or convergence state;
- Work Record or Work Capsule references;
- dependencies and lineage;
- correction or supersession history;
- Promotion state;
- Evaluation method and version;
- future VAE fields; and
- other information permitted by the applicable Contractual Sphere.

## 3.5 Authorized Network

**“Authorized Network”** means a network, community, organization, consortium, project, or other participation domain expressly designated by the Licensor as authorized to access specified Licensed Material under this License.

An Authorized Network may have its own membership criteria, Network Rules, Contractual Spheres, projects, and Network Operator.

Designation as an Authorized Network does not transfer ownership of the Licensed Material, patents, trademarks, or other intellectual property to that Authorized Network or its Members.

The Aregis Network is an initial Authorized Network.

## 3.6 Competing Offering

**“Competing Offering”** means a product or service offered outside authorized Network Use that is substantially substitutable for a material protected capability of the Licensed Material and is materially derived from, reproduces, incorporates, or depends upon Non-Public Network Material or protected implementation details of the Licensed Material.

Ordinary market competition, independent development, and interoperability are not enough by themselves.

A product or service is not a Competing Offering merely because it:

- interoperates through a publicly documented interface;
- uses a separately open-licensed SDK, schema, or protocol;
- competes in a broad market category;
- independently implements a public specification without protected code or Non-Public Network Material;
- provides consulting or professional services using the Licensed Material in accordance with this License; or
- offers an independent extension that communicates solely through a published interface and does not incorporate protected Licensed Material.

## 3.7 Contribution

**“Contribution”** means code, a patch, documentation, specification, schema, test, benchmark, ontology binding, workflow, policy profile, model adapter, design, correction, dataset annotation, evaluation artifact, or other material intentionally submitted for possible use by an Authorized Network, the Licensor, or a Network Operator.

## 3.8 Contributor

**“Contributor”** means a natural person or legal entity that submits a Contribution and has authority to grant the rights required by this License.

Where an AIA materially assists in creating a Contribution, the AIA may be recorded in provenance, but the submitting natural person or legal entity remains responsible for authority to submit the Contribution.

## 3.9 Contributor Agreement

**“Contributor Agreement”** means a separate individual or organizational agreement governing Contributions, including a Contributor Agreement or equivalent agreement designated by the Licensor.

Where a Contributor Agreement applies, it may supplement or supersede the inbound contribution provisions of this License to the extent it expressly states.

## 3.10 Contractual Sphere

**“Contractual Sphere”** means the subset of work, evidence, metadata, and contribution information that the applicable parties have agreed may be shared within a particular Authorized Network, project, collaboration, engagement, or contribution process.

Information outside the Contractual Sphere remains Private Refinement and is not made shareable merely because it informed a Contribution.

The Contractual Sphere may be defined in a Membership Agreement, Network Designation, Value Generation Contract, contribution schedule, NDA, statement of work, Network Rules, or another binding project instrument.

## 3.11 DAO3

**“DAO3”** means SagaHalla’s architecture and associated specifications for governed contribution, evidence, validation, verification, convergence, resolution, acceptance, attribution, Promotion, and related coordination processes, as versioned from time to time.

DAO3 is not defined by any single blockchain, database, software implementation, or governance mechanism.

## 3.12 Derived Work

**“Derived Work”** means a modification, adaptation, extension, fork, derivative work, or other work based on or incorporating a copyrightable portion of the Licensed Material.

## 3.13 Evaluation

**“Evaluation”** means a rule-governed assessment of a Contribution, Accepted Contribution, evidence set, or outcome.

Evaluation is distinct from submission, validation, verification, convergence, acceptance, Promotion, governance standing, and economic reward.

## 3.14 GAME

**“GAME”** means a governed work, contribution, or project-coordination system designated by the applicable Network Rules, including successor implementations that preserve the relevant contribution, evidence, dependency, or acceptance semantics.

A GAME state has legal effect only where a binding legal instrument expressly gives that state such effect.

## 3.15 Licensed Material

**“Licensed Material”** means the software, source code, documentation, schemas, specifications, tests, fixtures, configuration, build materials, and other materials that the Licensor expressly identifies as governed by this License.

Third-party material remains governed by its own license.

## 3.16 Licensor

**“Licensor”** means the natural person or legal entity identified in Section 1, or another authorized rightsholder that validly designates specified Licensed Material under this License.

Unless expressly stated otherwise, references to SagaHalla as technology steward do not by themselves identify the legal Licensor.

## 3.17 Member

**“Member”** means a natural person or legal entity admitted to an Authorized Network under the applicable Membership Agreement, Network Rules, or other approved admission process.

## 3.18 Member in Good Standing

**“Member in Good Standing”** means a Member whose membership status is active under the applicable Membership Agreement or other approved admission instrument, whose membership has not expired, been suspended, or been terminated, and who is in material compliance with:

1. this License;
2. the applicable Membership Agreement;
3. applicable confidentiality, security, contribution, and acceptable-use requirements; and
4. the applicable Network Designation.

Whether a Member owes, has paid, or is exempt from any fee does not itself determine rights under this License. Any effect of payment status on membership must occur through the applicable Membership Agreement or other binding membership instrument.

## 3.19 Membership Agreement

**“Membership Agreement”** means the agreement or legally effective electronic terms governing a Member’s participation in an Authorized Network, including admission, status, renewal, suspension, termination, and any applicable fees or subscription terms.

A Membership Agreement may incorporate this License, Network Rules, a Network Designation, project-specific terms, or other documents by reference.

A Membership Agreement may condition continued membership on payment or other consideration, but payment under a Membership Agreement does not itself constitute the License Grant under this License.

## 3.20 Network

**“Network”** means the applicable Authorized Network when the context concerns a Member, project, Contribution, Network Benefit, or Licensed Material.

Where more than one Authorized Network is involved, the term refers only to the Authorized Network or Authorized Networks expressly within the relevant scope.

## 3.21 Network Attribution Record

**“Network Attribution Record”** means an Attribution Record retained by or on behalf of a Network Operator or the Licensor through an authorized Network system.

## 3.22 Network Benefits

**“Network Benefits”** means benefits that an Authorized Network may make available under then-current Network Rules, including, where applicable:

- source access;
- participation rights;
- project eligibility;
- contribution visibility;
- reputation;
- contributor credentials or badges;
- technical collaboration;
- governance eligibility or standing;
- access tiers;
- support;
- early access;
- credits;
- grants;
- discounts;
- bounties;
- non-economic contribution units;
- future VAE-recognized attribution; and
- other benefits expressly adopted by the Authorized Network.

Network Benefits do not, by themselves, include any guaranteed payment, token, equity, ownership interest, revenue share, security, investment return, redemption right, or other regulated economic entitlement.

## 3.23 Network Designation

**“Network Designation”** means the versioned record by which the Licensor designates an Authorized Network and the specific Licensed Material and participation scope available to it.

A Network Designation should identify, where applicable:

- Authorized Network name and identifier;
- Network Operator;
- Licensed Material or repositories covered;
- permitted membership classes or tiers;
- effective date and version;
- applicable Network Rules;
- contribution-back scope;
- commercial-use scope;
- any cross-network sharing permission;
- applicable Contractual Sphere rules; and
- any special security, residency, or confidentiality conditions.

A Network Designation may expand access prospectively but may not retroactively impose new financial obligations, transfer ownership, erase historical provenance, or reduce vested rights created by a separate binding legal instrument.


A Network Designation identifies authorization scope; it is not a billing instrument. Any fee or subscription associated with membership or access must be established in a Membership Agreement or separate commercial agreement.

## 3.24 Network Operator

**“Network Operator”** means the natural person or legal entity designated by the Licensor or applicable Network Designation to administer an Authorized Network or specified Network functions.

A Network Operator has only the rights and responsibilities granted by this License, the applicable Network Designation, Network Rules, Membership Agreement, or another binding agreement.

## 3.25 Network Rules

**“Network Rules”** means the versioned rules for membership, contribution, attribution, security, governance, access, Evaluation, Promotion, and participation applicable to an Authorized Network.

Network Rules may evolve, but no later Network Rule may retroactively:

1. change authorship of a Contribution;
2. erase valid historical provenance;
3. transfer ownership of a Contributor’s pre-existing intellectual property;
4. impose a new financial obligation without required assent; or
5. create or revoke a vested right established by a separate binding legal instrument.

## 3.26 Network Use

**“Network Use”** means use by a Member in Good Standing:

- for the Member’s own internal purposes;
- for an authorized Network project;
- for a client or customer project in which the Member remains the operator of the Licensed Material; or
- as otherwise permitted by the applicable Network Designation, Membership Agreement, Network Rules, or separate written agreement.

A non-Member client may receive work product or outputs generated through lawful Network Use, but may not receive, operate, copy, or obtain the Licensed Material unless separately authorized.

## 3.27 Non-Public Network Material

**“Non-Public Network Material”** means Licensed Material, source code, implementation details, specifications, documentation, artifacts, evidence, security information, Network-only interfaces, or other information made available by reason of Authorized Network participation and not intentionally released to the general public without confidentiality or use restriction.

Non-Public Network Material does not include information that the receiving party can demonstrate:

1. was lawfully public without breach of duty;
2. was lawfully known to that party without restriction before receipt;
3. was lawfully received from a third party without confidentiality or use restriction;
4. was independently developed without use of or reference to Non-Public Network Material; or
5. was intentionally released by the Licensor under a separate public or open license.

Credentials and secrets are Non-Public Network Material even if accidentally exposed, unless the Licensor expressly and lawfully releases them for public use.

## 3.28 Private Refinement

**“Private Refinement”** means internal information, methods, customer information, business secrets, datasets, working notes, or other material outside the applicable Contractual Sphere.

Private Refinement does not become Network property merely because it contributed to an outcome.

## 3.29 Production Use

**“Production Use”** means use of the Licensed Material to perform real operational, professional, commercial, organizational, customer-facing, or revenue-generating work.

Evaluation, private experimentation, isolated development, and testing are not Production Use unless they themselves materially support an operational service.

## 3.30 Promotion

**“Promotion”** means a deliberate, authorized transition of a selected accepted fact, evidence reference, or attribution fact from a private or application-local state into a shared Network state, registry, ledger, or other shared authority surface.

Promotion is not automatic.

Only information within the applicable Contractual Sphere may be promoted.

Promotion does not, by itself, create economic value, legal acceptance, or an entitlement.

## 3.31 SNSL

**“SNSL”** means this SagaHalla Network Source License, including the version identified in the title of this document.

## 3.32 VAE

**“VAE”** means a Value Attribution Engine, verified-attribution engine, or successor Network mechanism that evaluates Contributions or Accepted Contributions under a structured and auditable attribution process.

A VAE may be deterministic or structured-stochastic.

A VAE evaluation is not, by itself, an offer, contract, payment obligation, token grant, security, or other economic entitlement.

## 3.33 VAEGraphExport

**“VAEGraphExport”** means a structured contribution, evidence, relationship, or Work-derived package prepared for possible input to a VAE or successor attribution process.

A VAEGraphExport is an input artifact. It is not itself an Evaluation, value score, governance right, or reward.

## 3.34 Value Generation Contract

**“Value Generation Contract”** means a binding project or participation instrument, if adopted for a particular Authorized Network or project, that defines an agreed Contractual Sphere, contribution expectations, rights, obligations, evidence requirements, attribution terms, or other project-specific conditions.

The term does not imply that every Authorized Network or project must use a Value Generation Contract.

## 3.35 Verified Contribution

**“Verified Contribution”** means a Contribution for which the applicable verification requirements have been satisfied for the stated scope.

Verification does not necessarily mean the Contribution has been accepted, promoted, rewarded, or assigned governance standing.

## 3.36 Work Capsule

**“Work Capsule”** means a versioned evidence package, or successor artifact, that binds a Work Record or defined work scope to selected provenance, execution, artifact, verification, or outcome evidence.

A Work Capsule does not by itself constitute legal acceptance, ownership transfer, or entitlement to a Network Benefit.

## 3.37 Work Record

**“Work Record”** means a versioned record of authorized or governed work and associated execution, evidence, verification, provenance, status, or outcome information generated or recognized by an applicable Network system.

A Work Record does not by itself constitute legal acceptance, ownership transfer, payment obligation, or entitlement to a Network Benefit.

## 3.38 External AI Service

**“External AI Service”** means a third-party hosted artificial-intelligence, machine-learning, inference, coding-agent, retrieval, embedding, evaluation, or similar service that receives or can access Licensed Material or Non-Public Network Material outside infrastructure controlled by the Member or applicable Network Operator.

A locally operated model or service under the Member’s exclusive control is not an External AI Service merely because it uses third-party software.

## 3.39 Serious Breach

**“Serious Breach”** means deliberate or reckless conduct involving one or more of the following:

1. unauthorized disclosure or exfiltration of Non-Public Network Material;
2. intentional source theft or misappropriation;
3. operation of a prohibited Competing Offering using protected implementation material;
4. deliberate circumvention of Network access controls;
5. malicious code, credential theft, or unauthorized surveillance;
6. knowing use of the Licensed Material in material violation of applicable law;
7. intentional falsification or removal of provenance for the purpose of misappropriating a Contribution; or
8. repeated material breach after written notice and a reasonable opportunity to cure.

A good-faith technical error, ordinary contractual dispute, or promptly cured accidental breach is not a Serious Breach unless the surrounding conduct independently satisfies this definition.

## 3.40 Defined-Term Convention

Capitalized terms used in this License have the meanings stated in this Section or, where expressly indicated, in the applicable Network Designation, Membership Agreement, Contributor Agreement, or other binding instrument.

A defined term includes its grammatical variants where the context requires. The singular includes the plural and the plural includes the singular where the context permits.

Capitalization used solely at the beginning of a sentence or in a heading does not create a defined term.


---

## 3.41 Protected rights definitions

**Contributor Ownership Instrument** means an executed VGC, conversion schedule, entity governing agreement, accession or other binding instrument that identifies the relevant legal entity, contributor, covered contribution, conditions and legal effect of admission to ownership. A contribution record, token balance or valuation result alone is not such an instrument.

**Protected Contributor Rights** means rights expressly granted under this License or an applicable Contributor Ownership Instrument or Protected Rights Schedule, including any earned conversion claim, ownership or governance entitlement, protected attribution, or specified continuity right. The term creates no otherwise ungranted economic entitlement.

**Protected Rights Schedule** means a binding schedule executed by the relevant obligors and affected rights holders, identifying protected material, legal entities, beneficiaries, decision authority, required approvals, succession duties, enforcement and any continuity permissions, state-based decentralization duties and fair-admission rights. Its scope and amendment conditions must be express. An unsigned Network Rule or designation cannot substitute for it.

**Protected Transaction** means a transaction or related series of transactions that transfers direct or indirect control of an identified steward or operator, disposes of or exclusively licenses identified core Licensed Material, or materially impairs Protected Contributor Rights. This includes transfers through affiliates or arrangements having substantially equivalent effect. Non-exclusive dispositions, security interests, management arrangements and aggregate related transactions that materially shift protected economic benefit, practical control or necessary access are included. Ordinary customer permissions are excluded only within the signed ordinary-course limits and where they do not accomplish such a disposition. The applicable schedule shall identify materiality criteria and covered entities; legal owners of interests in those entities must separately undertake applicable indirect-transfer restrictions.

# 4. Membership Condition, Authorized Network Scope, and Identity

The rights granted under this License are available only to Members in Good Standing of an Authorized Network for which the relevant Licensed Material has been designated through an applicable Network Designation or equivalent written authorization.

Membership in one Authorized Network does not automatically grant access to Licensed Material scoped to another Authorized Network. Where a Network Designation conflicts with a general Network Rule, the Network Designation controls for the Licensed Material and scope it expressly addresses.

The Network Operator may require authenticated identity for source access, contribution submission, contribution acceptance, attribution, protected actions, signing or receipt issuance, governance, and access to Non-Public Network Material.

This License does not prescribe a particular authentication technology.

A Member may allow its employees and individual contractors to exercise rights under this License only when they:

1. act on behalf of the Member;
2. are limited to the Member’s authorized scope;
3. are bound by written confidentiality and use obligations at least as protective as this License; and
4. cease access when their authorization ends.

The Member is responsible for such persons’ compliance.

---

## 4.1 Payment, Membership, Access, and License Are Distinct

The parties intend the following states and legal acts to remain distinct:

```text
Payment or Subscription
        ≠
Membership Status
        ≠
Network Authorization
        ≠
Technical Repository Access
        ≠
License Grant
        ≠
Contribution Attribution
        ≠
VAE Evaluation or Network Benefit
```

Accordingly:

1. payment of a subscription, membership fee, access fee, or other consideration does **not** by itself grant any right under this License;
2. nonpayment does **not** by itself terminate or revoke rights under this License;
3. payment status may affect membership only through the applicable Membership Agreement or other binding membership instrument;
4. a change in membership status affects License eligibility only when that status change becomes effective under the applicable membership instrument and this License;
5. technical repository, package, credential, API, or source-access controls are implementation mechanisms and do not themselves create or define the legal License Grant;
6. granting technical access does not expand the scope of rights granted by this License;
7. revoking technical access does not, by itself, determine whether a legal License Grant has ended;
8. Contribution, Attribution Records, VAE state, governance state, and Network Benefits do not themselves create or expand source-use rights under this License; and
9. the Licensor may authorize fee-paid, fee-waived, sponsored, academic, internal, enterprise, contributor, or other membership classes without amending this License.

Fees, subscriptions, billing, renewal, grace periods, refunds, taxes, credits, and other consideration are governed exclusively by the applicable Membership Agreement or separate commercial agreement and are not terms of the License Grant itself.

## 4.2 Authorization for Licensed Material

A Member in Good Standing may exercise rights under this License only for Licensed Material that the applicable Network Designation, Membership Agreement, or other written authorization places within that Member’s Authorized Network scope.

Membership alone does not grant access to all SagaHalla technology, and technical possession of source code does not expand the Member’s authorized scope.

---

## 4.3 Fair admission and transition integrity

For participating networks, admission, access, conversion eligibility and governance standing shall be decided separately under published, scope-specific criteria, with proportionate verification, reasoned decisions, bounded response times and independent appeal. Payment, nationality, residence or identity requirements must have a documented lawful or operational basis; no purchase of a token is an implied membership or ownership requirement. Where restricted evidence is necessary, provide controlled verification rather than demand public disclosure of confidential material.

No bound founder, operator, affiliate or administrator may preserve control by suppressing qualified admissions, delaying earned conversions, manipulating eligibility or contribution records, selectively withholding evidence or infrastructure, changing the readiness test after it is met, manufacturing affiliated voters, or moving protected assets outside the agreed perimeter. Criticism, an appeal, departure from a founder's preferred policy or support for a lawful transition is not by itself grounds for exclusion.

Amendment, suspension or waiver of these protections requires the approvals specified in adopted S13, including its independent contributor consent and review process. Security and legal containment must be proportionate, recorded and independently reviewable; it does not authorize indefinite founder control or erase surviving rights. Review deadlines constrain administration and enforcement; expiry of a deadline does not fabricate network readiness or issue equity.

## 4.4 Separate evaluation authorization

“Evaluation” in section 3.13 concerns contribution assessment. “Evaluation grant” here means the distinct software-testing permission in Schedule F; it does not perform or promise contribution valuation.

Notwithstanding the membership condition in sections 2, 4 and 5, an actual rights holder may issue the express evaluation grant in completed Schedule F to a non-Member. Only the identified material, persons, uses and term are covered. General production, redistribution, sublicensing and membership rights do not follow. Electronic acceptance under section 41 may bind that schedule where legally sufficient; accepting it does not waive Protected Contributor Rights. An uncompleted schedule grants nothing.

# 5. License Grant

Subject to this License and the Member’s applicable Authorized Network scope, the Licensor grants each Member in Good Standing who is authorized for the relevant Licensed Material a limited, non-exclusive, non-transferable, non-sublicensable license to:

1. access and inspect the source form of the Licensed Material;
2. reproduce it as reasonably necessary for Network Use;
3. execute and internally deploy it;
4. modify it;
5. create Derived Works;
6. test, benchmark, validate, and verify it;
7. use it for authorized Production Use;
8. submit Contributions and improvements to the Network;
9. share Licensed Material and Derived Works with other Members in Good Standing through authorized Network channels; and
10. use public interfaces, schemas, and interoperability surfaces as separately licensed or authorized.

A Member may share protected Licensed Material with another Member only if both Members are authorized for that same Licensed Material or the Licensor has expressly approved the cross-network sharing.

No right is granted to distribute or make the Licensed Material available outside the applicable Authorized Network scope except under a separate written authorization.

---

# 6. Permitted Client and Customer Work

A Member may use the Licensed Material to provide services or work product to a non-Member client if:

1. the Member remains the operator of the Licensed Material;
2. the client does not receive source code, protected binaries, deployment rights, credentials, or other access to the Licensed Material;
3. the use does not create a Competing Offering;
4. the Member complies with applicable confidentiality and data-processing duties; and
5. the Member’s membership tier permits the applicable commercial use.

A client that wants to operate, host, modify, inspect, or directly access the Licensed Material must become an authorized Member or obtain a separate commercial license.

---

## 6.1 Deployment boundaries

A customer receiving outputs from an authorized operator does not receive source, installation, or redistribution rights in the Licensed Material. SaaS/API access to the Licensed Material itself is permitted only within the expressly authorized service scope; an API is not a workaround for unauthorized protected rehosting. Self-hosting, customer source inspection, redistribution, and OEM embedding of Licensed Material require their identified grants under Sections 22, 23.2, or Schedule H. Where applicable, the operator, recipient rights, service scope, and governing instrument shall be recorded in Schedule H. Competitor status alone is not a ground for refusal under Section 21.1. Ordinary commercial authority cannot waive Protected Contributor Rights.

## 6.2 Generated Application, Plugin, and Interface Safe Harbor

Where a Member in Good Standing lawfully uses Licensed Material (including, where designated, `GAME Spec`, `GAME Plan`, `GAME Pipeline`, `GAME Events`, or `Saga Agent`) to design, generate, test, verify, or orchestrate an independent application, plugin, service, specification, or other work product:

1. **Generated Work Product Is Not Licensed Material:** Application source code, configurations, schemas, tests, documentation, and other outputs generated or validated through authorized Network Use are **not** `Licensed Material` or `Derived Works` merely because the Licensed Material generated, transformed, verified, or orchestrated them, provided they do not copy or embed copyrightable portions of protected Licensed Material.
2. **Standard Interface and Wire-Protocol Bindings:** Including standard public-interface declarations, wire-protocol message types, command/event envelopes (such as `MCP`, `ACP`, or `A2A` envelopes), or thin interoperability stubs solely to communicate with documented interfaces does not render an independent application or plugin a `Derived Work` under Section 7.3 or restrict its external commercial licensing or distribution under Section 23.

# 7. Network Reciprocity and Contribution-Back

## 7.1 Private Experimentation

A Member may privately experiment with modifications without immediately contributing them back.

## 7.2 Contribution-Back Trigger

A Member must submit the relevant source changes back to the Network if the Member:

1. uses a modification or Derived Work in Production Use;
2. shares the modification with another Member;
3. deploys the modification as a recurring Network capability;
4. incorporates it into a Network service, profile, adapter, workflow, or integration; or
5. relies on it as a material extension to the Licensed Material.

Submission must occur within **thirty (30) days** after the first applicable trigger unless another period is stated in the applicable project agreement or the Licensor grants a written exception.

## 7.3 Scope of Contribution-Back

Contribution-back applies only to:

1. modifications to the Licensed Material; and
2. derivative portions of a Derived Work that incorporate protected Licensed Material.

An **independent extension** does not become subject to contribution-back merely because it interoperates with the Licensed Material through a published API, schema, protocol, command surface, event interface, or other separately documented interoperability boundary.

Contribution-back does not automatically require disclosure of:

- unrelated proprietary software;
- Private Refinement;
- customer data;
- personal data;
- credentials;
- trade secrets unrelated to the Licensed Material;
- independently developed modules communicating solely through documented public interfaces; or
- information the Member is legally prohibited from disclosing.

Where reasonably possible, a Member must separate protected Network modifications from unrelated proprietary materials.

If there is a good-faith dispute over whether a component is derivative or independent, the Member may request a written scope determination from the Licensor or use the dispute process in Section 18 before disclosure of unrelated proprietary material is required.

## 7.4 Confidential Contribution Deposit

Where a modification is subject to client confidentiality or another legitimate restriction, the Member may request a confidential contribution deposit or alternative compliance path from the Network Operator.

The Network Operator may accept a source delta without customer data, a generalized patch, a privately escrowed source submission, a hash-bound contribution package, or another method that preserves the Network’s legitimate reciprocity interest while respecting the applicable Contractual Sphere.

## 7.4A Deposit and scope review

Section 7.3 excludes independent interoperability alone, while all five Section 7.2 triggers and the thirty-day period govern covered modifications unless changed by an express prospective amendment or project agreement. A confidential deposit request shall identify the protected delta, rights and disclosure obstacle without exposing customer secrets. For an activated protected pathway, the independent S13/S13A process decides scope, completeness and disputes; the Licensor is not the sole final judge. Undisputed duties continue; a narrowly scoped independent stay may protect disputed confidential material. Deposit is not economic acceptance or an automatic ownership award. No shortened deadline or changed classification may erase an earned claim.

Where no S13/S13A protected pathway is active, disputed confidential material is reviewed by an agreed confidential independent reviewer, or an equivalent mechanism agreed by the affected parties, before it is disclosed. If the parties cannot agree on a reviewer within fifteen (15) business days of a written request, either party may ask the appointing authority named in the applicable agreement or, failing one, the **default appointing authority recorded under adoption gate A5 in the adoption register** (Schedule I), to appoint a qualified independent reviewer bound by confidentiality. Until a default appointing authority is recorded, the fallback is not operative, and disputed material is not disclosed unless the parties agree or law requires it. The disputed material remains confidential and undisclosed throughout the appointment process. Proportionate emergency containment under Section 27.1 and legally required disclosure under Section 14.6 remain available.

## 7.5 Commercial Exception

The Licensor may grant a separate commercial license permitting private modifications without contribution-back only within its actual authority and applicable Protected Contributor Rights. Exceptions shall be documented under objective scope and ordinary-course limits. Material protected-asset impairment, related-party diversion and aggregate equivalent conduct require the applicable protected approvals; labelling a grant commercial or non-exclusive does not avoid them.

---

# 8. Contribution Submission and Rights

## 8.1 Contributor Ownership

A Contributor retains copyright ownership in the Contributor’s original Contribution, except to the extent the Contributor separately assigns ownership in writing.

This License does not transfer ownership merely because a Contribution is submitted or accepted.

## 8.2 Contributor License Grant

Unless a separate Contributor Agreement applies, by intentionally submitting a Contribution, the Contributor grants to the Licensor and Network Operator a perpetual, worldwide, irrevocable, non-exclusive, royalty-free, fully paid-up, transferable, sublicensable, and relicensable license to reproduce the Contribution, modify and prepare derivative works, combine it with other materials, display and perform it, distribute or make it available, commercialize it, include it in proprietary/source-available/open-source/hosted/enterprise/embedded/OEM offerings, license it under this License or another license, use it in specifications/schemas/tests/benchmarks/evaluation corpora/model-evaluation systems/verification systems, and authorize others to do the foregoing.

This grant is intended to allow the Network to evolve without later copyright hold-up while preserving Contributor attribution as provided in this License.

This grant does not include training, fine-tuning, distillation or synthetic training-data generation; those uses are governed exclusively by Section 20.1. This License creates no additional contribution or training rights in material governed by a separately executed project, collaboration, confidentiality or joint-venture agreement unless the parties expressly incorporate them through an authorized written amendment or annex.

The Licensor may require an individual or organizational **Contributor Agreement** for some repositories, projects, or membership classes. Where such an agreement applies, it may restate or expand inbound contribution grants, representations, and patent terms, but it should not silently erase historical attribution rights preserved by this License.

The exercise, transfer, sublicensing and relicensing of rights granted under this Section remains subject to Protected Contributor Rights binding on the Licensor or Network Operator. Neither shall structure a Protected Transaction, use an Affiliate or grant substantially equivalent rights for the purpose or effect of evading a required approval or successor obligation. Ordinary authorized development and commercialization continue within applicable scope. No consent to a Protected Transaction is inferred from submission, acceptance or contribution-back.

This paragraph does not revoke an existing valid license or bind a non-assenting third party merely through publication of a later SNSL version. Necessary covenants concerning pre-existing inbound grants and downstream rights must be adopted by the relevant parties through an express binding instrument.

## 8.3 Contributor Patent Grant

To the extent a Contribution would otherwise infringe a patent claim controlled by the Contributor, the Contributor grants the Licensor and Network Operator, and persons authorized by either of them, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable patent license to make, have made, use, offer to sell, sell, import, and otherwise exploit the Contribution and combinations of the Contribution with the Licensed Material where the patent claim is necessarily infringed by that Contribution.

This patent grant does not extend to unrelated patent claims that are infringed only by later combinations not contemplated by the Contribution.

## 8.4 Authority to Contribute

A Contributor represents that the Contributor has sufficient rights and authority to submit the Contribution and grant the rights required by this License.

A Contributor must not knowingly submit:

- confidential third-party material without authorization;
- code or other material subject to license terms that would prevent the Licensor from exercising the rights granted under Section 8;
- material that would require disclosure, relicensing, or distribution of unrelated Licensed Material contrary to the applicable Network Designation;
- misappropriated trade secrets;
- unlawfully obtained personal data; or
- material whose use would violate an applicable contractual restriction.

Strong-copyleft, source-disclosure, field-of-use, noncommercial, or otherwise materially restrictive third-party material may be introduced into Licensed Material only with express approval under the applicable contribution policy.

Material use of AI assistance must be disclosed where required by Network Rules, the applicable project agreement, or contribution policy.

## 8.5 Moral Rights and Similar Rights

To the maximum extent permitted by applicable law, a Contributor waives, and where waiver is not legally permitted agrees not to assert against the Licensor, Network Operator, authorized Members, or their permitted successors and licensees, any moral rights, droit moral, rights of integrity, rights of withdrawal, or similar personal rights in an Accepted Contribution that would prevent exercise of the rights granted under this License or an applicable Contributor Agreement.

Nothing in this Section permits false attribution or removal of accurate provenance protected by Section 9.

---

## 8.6 Submission categories and effective grants

> **Before you contribute: summary, not operative text.**
> - **The rule is low friction.** Submitting a Contribution grants the Section 8.2 use and commercialization license. Production improvements flow back under Section 7. No per-contribution negotiation is needed.
> - **You own your work, and training is opt-in.** You keep copyright in your Contribution (Section 8.1). Nothing you contribute, including code, is used for training unless you opt in. Opt in with a one-time standing election in Schedule E or a scoped annex (Section 20.1). Private material (Work Capsules, prompts, reasoning traces, customer information) is never trainable without express authorization.
> - **More protection is the exception path.** Use an ownership-promising S12 instrument, a Contributor Agreement, a project/JV agreement, or a confidential deposit. **Put these in place before you submit**, because the Section 8.2 license starts on intentional submission and a later disclosure cannot waive a granted right.
> - **Recognition and runtime continuity are the default rewards.** Without a separate agreement you receive durable attribution, eligibility for rule-governed evaluation, and eligibility for non-regulated Network Benefits offered under the Network Rules published when you submit; benefits earned under those rules survive departure (Sections 9, 10.1, 11, 27.6). In addition, once you have an Accepted Contribution in an official release, if you later leave the Network without breach you retain perpetual Pinned-Release Operational Continuity for existing deployments of that release (Section 27.4A). Enforceable equity/ownership rights require an S12 instrument; regulated rewards require a separate lawful instrument (Sections 10.6, 12, 13.1).
> - **Separate agreements keep their terms.** SNSL adds no contribution or training rights to separately governed material (Sections 8.2, 20.1 and 40).


Before intentional submission, supply the concise disclosure in Schedule E identifying the applicable contribution category and governing agreement, retained ownership, copyright/patent scope, commercialization and relicensing, grant event, training permissions under Section 20.1, compensation status and any applicable S12. Record the accepted version. A disclosure cannot waive an already granted right.

For unsolicited voluntary contributions and required section 7 deposits, the existing section 8.2 grant remains effective on intentional submission unless an express agreement provides otherwise; economic acceptance and ownership are separate. A confidential deposit retains its agreed disclosure limits. Do not relabel work commissioned under S12 as unsolicited or required deposit to avoid its bargain.

For work covered by a signed ownership-promising S12, that instrument must expressly specify intake and commercial grant events. Unless it expressly provides a different agreed sequence, the contributor grants only confidential internal assessment, testing and verification rights on intake, and the stated section 8.2/8.3 commercial grants become effective on objective acceptance or a valid independent acceptance determination under S12.5/S12.9. The limited patent permission necessary for authorized assessment follows the same intake scope; the full contribution patent grant follows the specified commercial event. Commercial use before that event requires express separate permission and cannot be used to withhold acceptance or earned issuance. Acceptance starts the applicable admission duties; commercialization does not discharge them. Existing grants are not revoked retroactively. No new ownership-promised work may begin without an effective S12 and completed adoption conditions.

This section controls inconsistent generic grant-on-submission, training, patent and acknowledgment terms for its covered work. Schedule E must identify the applicable category, and S12 must reconcile any overlapping reciprocity duty and previously granted rights before the work is requested.

# 9. Durable Attribution Covenant

## 9.1 Attribution Record

The Network Operator will maintain, or cause to be maintained, an auditable Attribution Record for Accepted Contributions to the extent reasonably practicable.

The Network may also retain records of submitted, rejected, superseded, or withdrawn Contributions where appropriate for audit, provenance, security, or dispute resolution.

## 9.2 Minimum Attribution

For an Accepted Contribution, the attribution record should, where available and lawful, preserve Contributor identity or approved pseudonymous identity, responsible Member, contribution identifier, date, project or scope, artifact or source revision, contribution type, acceptance state, and provenance sufficient to distinguish the Contributor’s work from later modifications.

## 9.3 Durable Provenance Right

Subject to applicable law, privacy duties, security requirements, and correction of inaccurate records, the Network Operator will maintain accurate historical provenance for Accepted Contributions and will not knowingly remove or reassign authorship merely because the Contributor later leaves the Network, the Contribution is later modified, the Network changes its commercial model, or a later evaluator assigns a different value to the Contribution.

A Contributor may request correction of an inaccurate attribution record through the applicable Network dispute or correction process.

The durable right protected by this Section is a right to **accurate provenance**, not a right to a particular valuation, ranking, governance weight, payment, token, equity interest, or other benefit.

Records may be corrected, superseded, restricted, pseudonymized, or removed where required by law, privacy duties, security needs, valid disputes, or documented retention policy.

Where a correction is made, the system should preserve the correction history where legally and technically permissible.

## 9.4 Attribution Is Not Acceptance or Reward

A Contribution record does not imply acceptance, verification, endorsement, governance standing, compensation, ownership in the Network, token rights, equity, revenue share, or any other economic entitlement.

Those outcomes require the separately applicable process or legal instrument.

---

# 10. Future DAO3 / VAE Compatibility

## 10.1 Attribution Eligibility

Accepted Contributions and their Network Attribution Records may be eligible for future evaluation under a VAE, DAO3 attribution process, or successor mechanism if the applicable Network Rules and Contractual Sphere permit.

This License creates **eligibility for rule-governed evaluation**, not a guaranteed score, ranking, governance position, payment, token, equity interest, or other economic entitlement.

## 10.2 Stable Legal Invariants

Any future DAO3/VAE process used with Licensed Material should preserve these legal invariants:

1. provenance is distinct from value;
2. submission is distinct from verification;
3. verification is distinct from acceptance;
4. acceptance is distinct from evaluation;
5. evaluation is distinct from reward;
6. historical authorship is not silently rewritten by later valuation;
7. Private Refinement outside the Contractual Sphere is not automatically exposed;
8. unknown evidence remains unknown rather than being fabricated;
9. material evaluation state is versioned or otherwise auditable to the extent required by applicable Network Rules; and
10. no software state automatically changes legal ownership or contractual rights unless a binding legal instrument expressly gives that state such effect.

## 10.3 VAE Input Is Not VAE Result

A Work Record, Work Capsule, contribution graph, VAEGraphExport, evidence envelope, or similar package may serve as an input to a future attribution process.

Such an input package is not itself a value evaluation, governance right, compensation obligation, or reward.

## 10.4 Historical Provenance and Future Valuation

A future attribution process may re-evaluate value under later rules where those rules permit, but should not rewrite historical provenance.

> **Who contributed what is a provenance question. What that contribution is worth under a particular evaluation version is a separate evaluation question.**

## 10.5 Operational Mechanics Belong in Network Rules

The following subjects should ordinarily be defined in versioned Network Rules, DAO3 specifications, project agreements, or other operating instruments rather than frozen into this License:

- contribution classes;
- evidence requirements;
- validation rules;
- convergence policy;
- evaluator versions;
- scoring or ranking methods;
- reputation systems;
- governance weighting;
- promotion mechanics;
- benefit formulas;
- reward programs; and
- migration rules for historical attribution.

This separation is intended to let the technology and attribution system evolve without repeatedly amending the underlying source license.


---

## 10.6 Contribution and ownership conversion

An eligible contribution may support admission to ownership only under a Contributor Ownership Instrument and the applicable entity governing documents. Lowercase `mana` may record attributed contribution and uppercase MANA may record governance voice under adopted rules; neither alone represents equity, redemption rights or title.

Where the binding instrument expressly identifies an accepted contribution, evaluation, ratification or other state and assigns it legal effect, the designated obligors shall perform that instrument according to its terms. Sections 12, 13 and 16 do not negate rights validly granted by that instrument. The legal ownership register and cap table shall reflect a valid completed admission; technical records evidence rather than independently supply legal title.

No rate, guaranteed admission, allocation, payment, investment return or transfer of IP is created by this Section. Changes to evidence or evaluation methods shall not retroactively impair an earned contractual right except through the instrument's express correction and dispute procedures or mandatory law.

# 11. Governance Standing and Non-Regulated Network Benefits

The Network may use verified contribution attribution to determine non-regulated Network Benefits such as reputation, access, contributor status, voting eligibility, governance standing, project eligibility, or non-economic contribution recognition.

Where the Network does so, the applicable mapping shall be governed by versioned, auditable Network Rules. The benefit terms published in the Network Rules at the time of a Contribution's intentional submission apply to that Contribution: a later rule change may not reduce a benefit already awarded, or one whose published conditions were already satisfied, except through the applicable versioned correction and dispute procedures in the Network Rules, which shall record the reasons for any correction and provide a challenge route under Section 18, or as mandatory law requires. Regulated rewards remain subject to Section 12.

A Member has no right under this License to any particular governance allocation unless that right is expressly granted under the then-applicable governance instrument.

---

## 11.1 State based contributor governance

A participating Licensor or Network Operator bound by a Protected Rights Schedule shall implement the state-based governance transitions identified in its adopted S13 schedule. Relevant authority shall follow the verified contribution, ownership, independence, participation and operating-capacity conditions assigned to that authority. Passage of time, revenue growth, account count, token holdings, a VAE score or a founder declaration alone establishes no transition.

Before holding the pathway out as operative, the bound entities and controlling persons shall adopt the necessary entity amendments, delegations and implementation instruments, adopt the S13A objective predicates and review procedures, and appoint the independent review and fallback authorities. Upon a valid determination that the adopted predicates are satisfied, the responsible parties shall implement the transition within the agreed administrative period, without a new discretionary founder veto. A technical state does not itself supply legal title, bind an unconsenting owner or replace a legally required instrument.

## 11.2 Independent contributor ownership target

A participating entity shall adopt the State E target in S13A: independent contributors holding at least 51 percent of exercisable member voting power, issued common-equivalent residual economic interests and fully diluted common-equivalent economic interests. The signed S12 capitalization annex must show and pre-commit a lawful reachable pathway, including sufficient issuance or transfer capacity and its economic terms. This is an earned or otherwise expressly agreed pathway, not an immediate grant or a guaranteed unearned allocation. Founder and founder-controlled interests do not count as independent.

State D remains the intermediate all-contributor ownership state. State E is separately certified within the identified entity and protected asset scope; no node certificate represents network-wide decentralization. Neither D nor E gates individual earned conversion or the earlier process and management transitions. The agreed State E pathway and, once attained, its floor are Protected Contributor Rights, subject to the coordinated amendment and individual-consent rules. Actual issuances and transfers remain governed by completed legal instruments.

# 12. Regulated Reward Carve-Out

Attribution and reward must remain separate where a reward would constitute or could reasonably implicate a regulated act.

Without limiting the foregoing:

1. no VAE score, Attribution Record, Contribution, Accepted Contribution, governance record, or Network membership creates an entitlement to cash, equity, a token, a security, transaction-based compensation, investment return, or other regulated economic benefit;
2. any regulated reward requires a separate lawful legal instrument and any required eligibility, licensing, disclosures, approvals, or compliance controls;
3. no formula or attribution rule under this License is intended to create transaction-based compensation for securities, capital raising, brokerage, placement, investment solicitation, or similar regulated activity; and
4. where contribution quality is evaluated in a regulated context, the evaluation may be retained for provenance and non-regulated recognition without creating an expectation of payment.

Nothing in this License is an offer to sell, solicitation to buy, or grant of any security, token, equity, investment product, or regulated financial instrument.

---

# 13. Contribution Units, MANA, FYRE, Tokens, and Similar Systems

This License does not itself issue, promise, or grant contribution units, mana, MANA, FYRE, tokens, staking rights, governance tokens, redemption rights, treasury claims, equity, profit interests, or other economic or digital assets.

If the Network later adopts any such mechanism, it must be governed by separate, versioned terms and any required legal review.

An Attribution Record may be used as an input to such a future mechanism only if the applicable rules expressly permit it.

---

## 13.1 Preservation of separately granted rights

Sections 12, 13 and 16 prevent automatic rights from attribution or machine state; they do not negate a lawful express S12 ownership obligation or the adopted S13/S13A transitions. No general reward disclaimer excuses performance of that bargain.

# 14. Contractual Sphere, Confidentiality, Trade Secrets, and Private Refinement

## 14.1 Share Only the Agreed Surface

A Member must not assume that all internal work, evidence, or data relating to a Contribution is shareable.

Only information within the applicable Contractual Sphere may be disclosed to counterparties, published to shared Network systems, used for cross-party attribution, promoted to a shared ledger, or exposed to a VAE operating across parties.

## 14.2 Private Refinement Remains Private

Private Refinement remains under the control of its owner unless separately licensed or contributed.

A Member is not required to disclose unrelated trade secrets, internal methods, customer information, or confidential data merely to prove that a Contribution exists.

If the available Contractual Sphere is insufficient for a particular Evaluation, the result must be limited, unknown, locally evaluated, or otherwise treated according to the applicable Network Rules. It must not be fabricated.

## 14.2A Local Agent Workspace, eSRA Privacy by Construction, and Warranted Compliance Boundary

A Member’s local agent execution environment, unpromoted Work Records, episodic memory, vector indexes, prompt context, reasoning traces, and private experimental branches (Section 7.1) constitute Private Refinement outside the Contractual Sphere until explicitly promoted under Section 15 or intentionally submitted as a Contribution. In alignment with DAO3’s eSourcing Reference Architecture (eSRA) boundary, privacy outside the Contractual Sphere is preserved by construction rather than discretionary post-capture filtering.

Neither the Licensor, the Network Operator, nor any Network software component or daemon may perform silent background telemetry extraction, unpromoted context scraping, or automated dragnet inspection of a Member’s or Bound Saga-Agent’s local workspace. Any compliance verification request under Section 29 beyond a written certification must state particularized, documented grounds for suspecting material noncompliance and is subject to confidential independent scope review under Section 7.4A before disputed local material is disclosed, whether or not an S13/S13A pathway is active. Proportionate emergency containment under Section 27.1 and legally required disclosure under Section 14.6 remain available.

For cross-party attribution across multiple participants or VG nodes where underlying evidence remains Private Refinement, the default Network posture is local or neutral-verified evaluation with promotion only of the resulting hash-bound fact or receipt, rather than compelling a Member to widen its Contractual Sphere or expose confidential refinements to competitors.

## 14.3 Confidential Status of Non-Public Network Material

Non-Public Network Material is confidential information of the applicable Licensor, Network Operator, Contributor, Member, or other lawful owner, as the context requires.

Each recipient must:

1. use Non-Public Network Material only for authorized Network Use;
2. protect it using at least reasonable care and no less than the care used to protect its own similarly sensitive information;
3. disclose it only to personnel, contractors, Affiliates, or service providers whose access is authorized and necessary for permitted use and who are bound by protective obligations;
4. prevent unauthorized copying, publication, extraction, or transfer;
5. promptly revoke access when authorization ends; and
6. promptly notify the applicable owner or Network Operator of a material known or reasonably suspected unauthorized disclosure.

## 14.4 Trade-Secret Protection

To the extent Non-Public Network Material qualifies as a trade secret under applicable law, the parties intend to preserve that status.

No expiration of an ordinary confidentiality period authorizes disclosure of information that remains a legally protectable trade secret.

Members must use reasonable measures appropriate to the sensitivity and circumstances to preserve secrecy, including access control, authenticated repository access, least privilege, confidentiality obligations, and secure handling of credentials and source archives.

Nothing in this License authorizes reverse engineering, extraction, disclosure, or use of protected trade secrets beyond the express License Grant.

## 14.5 Return, Deletion, and Archival Copies

Upon termination of access or written request following termination, a Member must cease active use and, subject to Section 27, delete or return Non-Public Network Material in its possession or control where reasonably practicable.

A Member may retain archival copies only to the extent required by law, professional recordkeeping, insurance, security investigation, dispute preservation, or an applicable binding agreement. Any retained archival copy remains subject to the confidentiality, trade-secret, restricted-use, and security obligations of this License and may not be used for ongoing development or operation unless separately authorized.

Routine backup media need not be immediately purged where deletion is technically impracticable, provided that the material is not restored for active use and is deleted in the ordinary backup lifecycle.

## 14.6 Legally Compelled Disclosure

If a Member is legally compelled to disclose Non-Public Network Material, the Member must, to the extent legally permitted:

1. promptly notify the Licensor, Network Operator, or applicable owner;
2. disclose only what is legally required; and
3. reasonably cooperate in seeking confidential treatment or protective relief.


# 15. Promotion and Shared Records

The Network may support future promotion of selected facts or attribution records into shared registries, distributed ledgers, blockchains, or other durable shared systems.

Promotion must be explicit.

No Member grants permission to publish document bodies, private work product, personal data, or Private Refinement merely by accepting this License.

Where promotion is used:

1. only information within the applicable Contractual Sphere may be promoted;
2. the promoted fact should be bound to the underlying record by a verifiable identifier, hash, signature, or comparable provenance mechanism where practical;
3. promotion must preserve the distinction between the underlying artifact and its fingerprint or reference;
4. promotion does not itself imply substantive correctness, acceptance, reward, or ownership; and
5. any legally operative rights remain governed by the applicable off-chain legal instrument.

---

# 16. Legal Effect of Machine and Network State

No Network state, GAME state, VAE state, blockchain entry, distributed-ledger record, Work Record, Work Capsule, model output, automated Evaluation, convergence result, Promotion event, or other software-generated state modifies legal ownership, transfers intellectual property, creates a payment obligation, creates equity or token rights, or changes contractual rights **unless the applicable binding legal instrument expressly provides that the identified state has that legal effect**.

Operational systems may provide evidence of legally relevant events, but software state does not replace the governing legal instrument.

# 17. Validation, Convergence, Acceptance, and Resolution

The Network may use automated or human processes to validate and accept Contributions.

The following concepts remain distinct:

**Validation** — checks whether submitted material satisfies pre-committed technical or policy rules.

**Verification** — checks whether evidence supports a stated result or criterion.

**Convergence** — determines whether required independent evaluations agree sufficiently under the applicable policy.

**Resolution** — handles a disagreement, challenge, or defect through the applicable review or dispute path.

**Acceptance** — the authorized recognition that the Contribution satisfies the requirements for the stated scope.

**Promotion** — moves an accepted or otherwise authorized fact into a shared authority surface.

**Attribution** — records who contributed and may evaluate the value or effect of that contribution.

No one of these automatically substitutes for another.

## 17.1 Information Admissibility and Warranted Execution Boundary

Where a Network system or DAO3 implementation evaluates execution admissibility (whether current, non-stale, non-conflicting evidence supports a specific consequential action at commitment time), an evidence-derived admissibility check or permit may narrow or block delegated execution by a Bound Saga-Agent when required evidence is unknown, stale, expired, or conflicting, but never enlarges delegated authority beyond the Principal’s mandate and the governing legal instrument. Post-action outcome admissibility does not by itself establish Convergence, Acceptance, Promotion, or legal title transfer.

---

# 18. Corrections, Disputes, and Semantic Rollback

A Contributor or Member may challenge an Attribution Record, acceptance state, or VAE evaluation through the applicable Network dispute process.

The process should, where applicable:

1. identify the contested record or obligation;
2. test the relevant evidence against the applicable versioned rules;
3. route ambiguity to the authorized review path; and
4. record the resulting correction, supersession, rollback, or reaffirmation.

A correction should not silently rewrite history where a superseding record can preserve an auditable chain.

The Network Operator may suspend disputed economic or governance consequences pending resolution where reasonably necessary.

## 18.1 Algorithmic Confrontation, Reproducible Evaluation Receipts, and Agent Fault Containment

Where an automated validator, verifier, convergence check, or VAE rejects, downgrades, withholds acceptance of, or flags a Contribution or Accepted Contribution, the system must provide the Contributor (and its authorized Bound Saga-Agent) a structured, signed evaluation receipt identifying the evaluator version, applicable rule or rubric reference, input artifact or VAEGraphExport hashes, and specific failed criteria or structured-stochastic evaluation parameters sufficient to permit independent verification, remediation, or challenge under this Section and S12.5. Secret or unrecorded evaluation criteria cannot defeat pre-agreed objective acceptance criteria under an effective S12 instrument.

A receipt shall state whether the evaluation supports (a) exact deterministic reproduction or (b) audit-sufficient evidence only. For stochastic or externally hosted evaluations, where a seed and model identifier may not reproduce the result, the receipt shall identify the retained inputs, prompts or rubrics, configuration, model and provider identifiers, the outputs relied on, the retention period, and how the Contributor and its authorized Bound Saga-Agent may access them to challenge the evaluation.

An unintended operational fault, rate excursion, or reasoning error by a Bound Saga-Agent that is neither deliberate nor reckless, does not involve exfiltration, credential theft, or misappropriation of Non-Public Network Material, and is not a repeated material breach after written notice under Section 3.39(8) may be contained via temporary automated throttling or credential quarantine under Section 27.1, but constitutes an ordinary curable matter under Section 27.2 rather than a Serious Breach under Section 27.3 if promptly halted and cured upon notice. Even during credential quarantine, the Principal and its authorized Bound Saga-Agent retain safe read-only access to their attribution and governance evidence and an active dispute-filing channel to the independent neutral under Section 44.3.

---

# 19. Rights of Members to Attribution

Subject to privacy, confidentiality, and accurate-record requirements, a Contributor may truthfully identify itself as the author or contributor of an Accepted Contribution.

The Network may provide public or member-visible contributor profiles, histories, badges, credentials, or dashboards.

Use of Aregis, SagaHalla, Saga Agent, GAME, VAE, or other trademarks remains subject to the applicable trademark rules and does not imply endorsement beyond the documented relationship.

---

# 20. Model Training, Machine Learning, and External AI Services

## 20.1 Network Training Rights

**Rule and exception.** Contributing is designed to be low-friction: the Section 8.2 license, contribution-back under Section 7 and Network use of Accepted Contributions do not require per-contribution negotiation. Training is a separate permission. It is granted once through a standing election or annex, or not at all. Contributors who need more protection use the exception paths in Section 8.6 before submission.

**(a) Licensor-owned and Network-generated material.** Subject to the Contractual Sphere, privacy requirements, project-specific restrictions and any existing restriction on the material, the Licensor and Network Operator may use the following for developing, training, fine-tuning, evaluating, benchmarking or improving models and automated systems used by or for the Network:
1. material in which the Licensor **owns** the relevant rights; and
2. material for which the Licensor holds a **separate express training authorization** from the actual rights holder, within that authorization's terms.

Repository administration, hosting, access control, a commercial license or any other form of control does not by itself establish training permission. Contributor-origin material remains under paragraph (b) unless a valid separate grant from its rights holder expressly permits the training.

Network-generated outputs, such as evaluator outputs and aggregate statistics, qualify under this paragraph only if they do not reproduce or embed protected contributor, customer or private content. Generation by the Network alone is not sufficient.

**(b) Contributor material.** For any other material, including Contributions and Accepted Contributions of every kind (code, documentation, specifications, tests and data), Attribution Records, Work Records, Work Capsules, verification artifacts, prompts, reasoning traces and private context, training, fine-tuning, distillation or synthetic training-data generation is permitted **only** where the actual rights holder has expressly authorized it through:
1. a scoped training annex; or
2. a standing training election in Schedule E or in an acceptance record operating under a binding instrument that expressly provides for it.

The authorization must identify:
- the exact artifacts or artifact categories;
- the permitted training purposes;
- the recipients;
- downstream permissions for trained models;
- retention; and
- applicable restrictions.

**(b1) Standing election: scope and lifecycle.** A standing training election under paragraph (b)(2) shall state, when it is made:
1. **Scope over time:** whether it applies only to identified past submissions or also to future submissions, and for which artifact categories.
2. **Prospective change and withdrawal:** the contributor may narrow or withdraw it at any time by written notice through the recorded channel. The change takes effect for material not yet used in training within a stated reasonable period, and no later than thirty (30) days after notice.
3. **Existing uses:** how datasets, checkpoints and trained models created under the election before a change or withdrawal are treated, including whether they may continue in use, be retained, be distributed further or be retired. The Licensor need not promise technically unrealistic removal from already-trained models, but the treatment must be stated at election time, and a later change cannot worsen it for the contributor without consent.
4. **Renewed authorization:** any new training purpose, new recipient class, new material category, or new downstream permission for trained models requires a fresh express authorization. It cannot be added by administrative change, by revising Network Rules or by updating a form.

The election record, including the version accepted and any changes or withdrawal, is retained with the contributor's acceptance records.

**(c) Acceptance is not authorization.** Permission to assess, verify, accept, integrate, deliver, compensate or commercialize a Contribution does not itself authorize training. Acceptance of a deliverable never authorizes training on its surrounding Work Capsule, Work Records, prompts, reasoning traces, private context or other unselected material.

**(d) Limits on any authorization.** An authorization cannot override customer confidentiality, Private Refinement or the Contractual Sphere, and cannot extend to material or rights the contributor does not control. Private customer data and Private Refinement are excluded unless separately authorized by their actual rights holders.

**(e) Separately governed work.** This License creates no additional contribution or training rights in material governed by a separately executed project, collaboration, confidentiality or joint-venture agreement unless the parties expressly incorporate them through an authorized written amendment or annex.

**(f) S12 work.** For work under an ownership-promising S12 instrument, nothing in this Section is authorized during intake assessment. After objective acceptance, or a valid independent acceptance determination under S12.5/S12.9, training remains subject to paragraphs (b)–(e).

**(g) Existing grants and compute.** Existing valid grants remain governed by their terms. Neither the Licensor nor the Network Operator may conscript a Member's local compute, Bound Saga-Agent execution capacity or paid third-party inference quotas for Network model training or third-party verification without the Member's express agreement.

## 20.2 Anti-Appropriation Restriction

A Member may not use Non-Public Network Material or protected Licensed Material to train, distill, construct, or materially improve a model or automated system whose intended principal purpose is to:

1. reproduce the protected implementation of the Licensed Material;
2. generate a non-Member substitute for a material protected capability;
3. evade this License’s membership restrictions; or
4. enable unauthorized external distribution or rehosting.

This restriction does not prohibit authorized Network research, model adaptation, worker or supervisor training, interoperability research, or Member-internal optimization consistent with this License.

## 20.3 Use of External AI Services

A Member may transmit Licensed Material or Non-Public Network Material to an External AI Service only when the applicable Network Designation, Network Rules, Membership Agreement, or written authorization permits that category of service and the Member reasonably ensures that the service is subject to protections appropriate to the material.

Such protections should address, as applicable:

- confidentiality;
- provider access;
- retention;
- training or secondary use;
- logging;
- security;
- geographic or residency restrictions;
- subprocessors;
- deletion;
- incident response; and
- credential handling.

Where the applicable Network policy requires a no-training, zero-retention, local-only, approved-provider, or other restricted mode, the Member must use that mode.

A Member may not evade this Section by placing protected source into prompts, attachments, retrieval indexes, embeddings, logs, traces, screenshots, model context, or agent memory.

## 20.3A Published provider categories

Publish approved provider and mode categories, permitted data classes, actual training/retention terms, residency/security requirements and the version/date of approval. No individual call approval is required within a valid category unless its stated conditions require it. Categories do not expand IP grants or authorize customer-data disclosure. Material adverse access changes require recorded grounds and independent review under an activated protected pathway, with safe alternative evidence access and unaffected ownership duties preserved.

## 20.4 Local and Network-Controlled Models

This License does not prohibit use of a locally operated or Network-controlled model merely because that model processes protected source, provided the processing remains within the Member’s authorized scope and satisfies applicable security, confidentiality, residency, and contribution obligations.

Within its authorized scope, a Member and its Human-Bound Agents may configure local system prompts, constitutions, skills, memory and tool policies. This freedom remains subject to mandatory approvals, security controls, the Contractual Sphere, confidentiality and applicable law, and does not authorize circumvention of Network access controls.


# 21. Prohibited Uses

Unless separately authorized in writing, a Member may not:

1. provide source access to a non-Member;
2. publicly distribute protected Licensed Material;
3. sublicense the Licensed Material;
4. sell or transfer a protected fork outside the Network;
5. operate a Competing Offering outside authorized Network use;
6. provide the Licensed Material as an unrestricted hosted service for non-Members;
7. remove or falsify provenance, copyright, license, or attribution notices;
8. misrepresent a submitted Contribution as accepted or verified;
9. falsely claim another person’s contribution;
10. use another Member’s credentials or source entitlement;
11. circumvent Network access controls;
12. use Non-Public Network Material to evade membership restrictions;
13. intentionally introduce malicious code, backdoors, credential theft, or unauthorized surveillance;
14. knowingly submit unlawfully obtained material; or
15. use the Licensed Material in violation of applicable law.

---

## 21.1 Independent competition and governance conduct

No provision prohibits lawful independent development, offering competing independently developed products, using alternative platforms, serving multiple networks or choosing customers merely because that conduct competes with a founder, Member or Network. Protected implementation, confidentiality, actual patent rights and expressly licensed scope remain subject to their lawful terms. The Competing Offering definition and section 20.2 apply to unauthorized use of protected material, not functional similarity alone or independently acquired skills and knowledge. No restraint on unrelated research or development is created.

Members independently determine their prices, bids, customers, output, wages and hiring for their separate businesses. Neither Network Rules nor contributor votes authorize price/wage fixing, bid rigging, customer or territory allocation, no-poach arrangements, collective retaliation against competitors, or unnecessary exchange of competitively sensitive information. Legitimate joint operations require separately scoped, legally reviewed authority; this license alone supplies none.

Admission and standards decisions must use published, proportionate security, rights and capacity criteria, reasoned refusals, conflict recusals and independent appeal. Competitor status, refusal to buy unrelated services or choosing an alternative platform is not alone a refusal ground. Do not tie protected access to unrelated purchases, exclusive dealing or surrender of independently developed rights through policy. No general obligation to license every asset is created; actual conduct and market circumstances require competition-law review.

Use restricted evidence custody or independent review for sensitive contributor business information. Governance must receive only what is necessary for its lawful decision; do not publish future prices, bids, customer-specific strategies or unnecessary individual compensation information to competitors. Contribution ownership and democratic votes do not immunize anticompetitive conduct.

# 22. Interoperability and Separately Licensed Components

Independent extensions are governed by Section 7.3. Public interfaces do not automatically license protected implementation. The actual rights holder may separately license exact components or releases identified in a completed Schedule G—such as wire-protocol packages, type schemas, or client SDKs—including under a permissive open-source license following title, dependency, and patent review. No component becomes permissively licensed merely because this License mentions it.

Before releasing material within a protected asset perimeter, the releasing parties must apply the adopted ordinary-course or Protected Transaction approval rules to the actual economic and practical effect. Founder-controlled affiliates, release splitting, or moving core implementation into an SDK cannot bypass those rules. Those internal approval duties bind the releasing parties; they do not impose additional SNSL membership, payment, ownership, or noncompetition restrictions on recipients exercising a valid permissive grant. Existing valid releases remain effective under their actual terms, and third-party rights are not narrowed.

# 23. No External Redistribution; Application Distribution Profiles

Except as permitted below or under a separate license designation, a Member may not provide the Licensed Material or a Derived Work to any non-Member by public repository, package registry, source archive, binary distribution, container image, hosted download, source escrow for an unauthorized party, or other means that gives the non-Member possession or operational control of protected Licensed Material.

## 23.1 Independent Applications, Generated Work Product, and Permissive Interfaces

Consistent with Sections 6.2, 7.3, and 22, nothing in this Section 23 restricts a Member from commercially licensing, publishing, selling, or distributing to non-Members (under proprietary, source-available, or open-source terms chosen by the Member):

1. ordinary work product, independent applications, or plugins produced through lawful Network Use that do not incorporate or bundle protected Licensed Material;
2. standard public-interface or wire-protocol client bindings covered by Section 6.2(2); or
3. client SDKs, schemas, or protocol packages separately licensed under a permissive license through a completed Schedule G.

## 23.2 Standardized Embedded Runtime Distribution Profiles

Where an application requires embedding or distributing an unmodified SNSL runtime component (such as a local execution daemon, container, or runtime package) to end customers, the Licensor or Network Operator may publish standardized **Embedded Runtime Distribution Profiles** under Schedule H (for example, authorizing distribution of a signed runtime package that activates Production Use only when the end customer holds or authenticates an active Network membership seat, runtime entitlement, or commercial license). Distribution in compliance with an active published Schedule H profile satisfies the separate written authorization requirement of Sections 5, 6.1, and 23 within that profile’s stated scope.

---

# 24. Trademark Rights

This License does not grant trademark rights.

A Member may make truthful nominative statements such as “Member of the Aregis Network,” “Compatible with Saga Agent,” or “Built using Saga Agent” only to the extent accurate and in accordance with applicable brand guidelines.

No Member may imply sponsorship, certification, or endorsement that has not been granted.

---

# 25. Licensor Patent License and Patent Defense

## 25.1 Limited Licensor Patent Grant

Subject to compliance with this License, the Licensor grants each Member in Good Standing a worldwide, non-exclusive, non-transferable except as expressly permitted by Section 44, royalty-free patent license under patent claims owned or controlled by the Licensor that are necessarily infringed by the Member’s authorized exercise of the copyright license granted in Section 5, solely for authorized Network Use of the Licensed Material.

This patent license does not grant rights:

- to unrelated products or combinations;
- to uses outside the applicable Network Designation;
- to a Competing Offering;
- to trademarks;
- to patent claims infringed only by modifications not supplied or authorized by the Licensor; or
- beyond the term of the Member’s authorized use, except as expressly preserved for permitted wind-down (Section 27.4), Pinned-Release Operational Continuity (Section 27.4A), an effective Section 44.1 continuity grant, or lawful archival retention (Section 14.5).

## 25.2 Patent Retaliation

If a Member or its controlled Affiliate initiates patent litigation alleging that the Licensed Material or an Accepted Contribution infringes a patent, the Licensor may terminate patent licenses granted to that Member under this License to the extent permitted by law.

This Section does not prohibit good-faith defensive counterclaims, claims required to preserve a defense, or challenges unrelated to the Licensed Material.

## 25.3 Contributor Patent Rights

Contributor patent grants remain governed by Section 8 and any applicable Contributor Agreement.


# 26. Security and Access Obligations

A Member receiving source access must use reasonable security measures, including as appropriate individual authenticated accounts, least privilege, multi-factor authentication, secure repository access, prohibition on credential sharing, reasonable endpoint security, removal of access when personnel leave, secure handling of secrets, and reasonable incident response.

A Member must promptly notify the Network Operator of a material unauthorized disclosure of Non-Public Network Material.

---

# 27. Membership Suspension and Termination

## 27.1 Suspension

The Network Operator or Licensor may temporarily suspend source access, credentials, Network privileges, or specified uses where reasonably necessary to address:

- suspected source leakage;
- credential compromise;
- security incidents;
- material breach;
- unlawful use;
- credible risk of misappropriation; or
- material risk to the Network or other Members.

Suspension may be immediate where delay would materially increase risk.

## 27.2 Ordinary Material Breach and Cure

Except for a Serious Breach or urgent security threat, before permanently terminating rights for material breach the Licensor or Network Operator will provide written notice describing the breach with reasonable specificity and at least **thirty (30) days** to cure, unless a longer period is required by an applicable Membership Agreement.

If the breach is not reasonably curable within thirty days but the Member begins cure promptly and diligently proceeds, the Licensor may extend the cure period in writing.

## 27.3 Serious Breach

A Serious Breach permits immediate suspension and, where reasonably justified by the circumstances, immediate termination of the rights affected by the breach without a wind-down right for continued operational use.

Termination for Serious Breach does not erase historical Attribution Records or extinguish contributor licenses already granted for Accepted Contributions.

## 27.4 Effect of Ordinary Membership Expiration or Termination Without Breach

When membership has effectively ended under the applicable Membership Agreement or other binding membership instrument, without uncured breach:

1. no new Network Use or new deployment of Licensed Material may begin;
2. active repository, credential, governance, and hosted Network access ends (subject to safe governance/evidence access under Section 44.3);
3. the Member may retain archival copies as permitted by Section 14.5;
4. a **one hundred eighty (180) day** wind-down period applies to existing operational deployments unless Section 27.4A or a separate agreement provides longer continuity;
5. during wind-down, use is limited to orderly operation, migration, export, continuity, security, and cessation activities for pre-existing deployments rather than new product or feature development;
6. the Member may export its lawful data, Work Records, Private Refinement, and other records it is entitled to retain; and
7. the Member may exercise applicable Pinned-Release Operational Continuity under Section 27.4A or seek a separate commercial license for broader continued use.

## 27.4A Pinned-Release Operational Continuity for Qualifying Contributors and Long-Standing Members

Where membership expires or terminates **without uncured breach** (and without a Serious Breach under Section 27.3), a departing Member qualifies for **Pinned-Release Operational Continuity** for a specific Licensed Material product if, prior to termination, the Member either:

1. **Qualifying Contributor:** submitted one or more **Accepted Contributions** (Section 3.1) incorporated into an official release of that Licensed Material; or
2. **Qualifying Tenure:** maintained continuous **Member in Good Standing** status authorized for that Licensed Material for at least **twelve (12) consecutive months**, having satisfied all undisputed membership fees or consideration applicable during that period under its Membership Agreement.

Upon completion of the Section 27.4 wind-down period, a qualifying former Member retains a **perpetual, worldwide, non-exclusive, non-transferable (except as permitted by Section 44), non-sublicensable, royalty-free, maintenance-only runtime license** under Section 5 and the corresponding Licensor patent license under Section 25.1 solely to:

- **(a) Operate Existing Deployments on a Pinned Release:** continue internal Production Use and pre-existing Section 6 operator-hosted client deployments using the exact official release version(s) of that Licensed Material already running in Production Use by that Member prior to termination (and, for a Qualifying Contributor, up to the latest official release published during its membership that incorporates its Accepted Contribution) (each, a **“Pinned Release”**); and
- **(b) Maintain Security and Stability:** apply private bug fixes, security patches, configuration updates, and dependency compatibility adjustments to its deployed copy of the Pinned Release solely to maintain the safety and operation of those pre-existing deployments, without any post-termination Section 7.2 contribution-back obligation.

**Boundaries and Exclusions:** Pinned-Release Operational Continuity:

1. grants **no** right to access or use later releases, upgrades, active Network repositories, hosted Network APIs/oracles/VAE services, or unpaid support;
2. authorizes **no** external redistribution (Section 23), sublicensing, new Competing Offering (Section 3.6), expansion to new unaffiliated entities, or prohibited model training/appropriation (Section 20.2);
3. remains conditioned on compliance with surviving confidentiality, trade-secret, security, attribution, and compliance verification duties (Sections 14, 26, 29, and 42), and may be terminated under Sections 27.2–27.3 for uncured material breach or Serious Breach of those surviving duties; and
4. conveys only copyright and patent rights owned or licensable by the Licensor without third-party payment, and implies no third-party license or ongoing service obligation (Sections 32 and 44.1).

## 27.5 Effect of Termination for Serious Breach

On termination for Serious Breach:

1. active source and repository access ends immediately;
2. no new or continued Production Use is authorized except where the Licensor expressly permits a limited safety or customer-protection transition in writing;
3. the Member must promptly disable access by its personnel and contractors;
4. protected material must be returned, deleted, or isolated in accordance with Section 14.5; and
5. accrued obligations and surviving provisions remain enforceable.

## 27.6 Historical Attribution Survives

Termination of membership does not erase accurate historical attribution.

The licenses previously granted by a Contributor for Accepted Contributions survive termination.

Any vested right established under a separate signed legal instrument survives according to that instrument.

Unvested or discretionary Network Benefits may end under the applicable Network Rules. Benefits already earned under Section 11, meaning awarded or with their published conditions satisfied before termination, are preserved and are not forfeited by termination, departure or credential removal, except as determined under the applicable versioned correction and dispute procedures or mandatory law.


Expiration, departure, suspension, removal of credentials or termination of a software license does not by itself cancel a Protected Contributor Right that survives under its governing instrument. Material breach, fraud, error and lawful forfeiture are determined only under the applicable instrument and law with the specified notice and review. This survival does not authorize continued operational source use beyond an independently effective license, Section 27.4A Pinned-Release Operational Continuity right, or Section 44.1 continuity grant. Historical attribution remains protected as otherwise provided by this License.

# 28. Versioning of This License and Network Rules

This License is versioned.

A later version of SNSL does not replace this version for already licensed material unless the Member makes an authorized affirmative choice to accept the later version. A release that permits migration offers that choice; it does not migrate anyone automatically.

Login, repository access, continued use, receipt of files, a merge or technical validation does not by itself adopt a later version of this License or amend any existing signed commitment of a Member, Contributor or organization. An acceptance record for a later version must identify the exact version, the material covered, the legal scope, the accepting party, the capacity in which it accepts and its authority. An in-software human approval is evidence of acceptance but does not by itself establish authority to amend an organization’s IP grants or governance arrangements.

Network Rules may evolve without reissuing the copyright license, provided that they do not contradict the express rights and protections in this License.

Network Rules may define operational details such as contribution classes, validation, convergence, evaluation methods, VAE versions, governance eligibility, promotion, and discretionary benefits. They may not, without an appropriate separate legal mechanism:

- transfer ownership;
- erase accurate historical provenance;
- expand the scope of the copyright license beyond this License;
- impose new mandatory economic obligations retroactively;
- create a security, equity interest, token right, or payment obligation;
- reduce a vested right created by a separate binding legal instrument; or
- convert Private Refinement into shared Network material without authorization.

The Licensor may designate additional Authorized Networks or additional Licensed Material for an existing Authorized Network without amending this License through a versioned Network Designation, provided that such designation does not retroactively expand a Member’s obligations or reduce vested rights under a separate binding instrument.

Material changes to contribution ownership, source-use scope, confidentiality duties, or mandatory economic obligations require an appropriate legal mechanism and may not be imposed solely by changing a web page.

---

## 28.1 Protected rights precedence

Notwithstanding the ordinary order of precedence, no commercial agreement, Contributor Agreement, Network Designation, Network Rule, waiver or amendment may impair another person's Protected Contributor Rights without the approval required by the instrument creating those rights and any mandatory individual consent. An agreement between some parties does not waive another beneficiary's rights. Protection against impairment includes amendment or waiver of the protection itself.

For transition predicates, election administration, review periods and implementation, adopted S13A and its integrated anti-obstruction provisions control inconsistent general procedure. S12 controls its express economic terms; neither a procedural hierarchy nor a later commercial side agreement waives protected rights without the required affected consent.

This provision preserves rights already validly created for the relevant subject matter. It does not itself create new rights over separately governed material, and does not require adoption of S12, S13 or S13A. This provision applies only within a validly adopted binding framework. It does not retroactively invalidate an existing agreement or impose obligations on a person who has not become bound. A later instrument shall identify the exact rights and provisions it modifies and the authority and consents supporting the modification.

## 28.2 Release and migration record

Publish a package/release manifest identifying actual license/version, designation, component boundaries, grantor authority and relevant acceptance records. Record previous-version coexistence and affected consents. No automatic migration resets contribution evidence, vesting, class rights, state predicates or surviving grants.

# 29. Records and Reasonable Compliance Verification

A Member must maintain reasonable records sufficient to identify authorized source users, deployments of protected Licensed Material, and material contribution-back obligations.

Where the Licensor has a reasonable basis to suspect material noncompliance, the Licensor may request a written compliance certification.

Any audit right beyond such certification must be exercised reasonably, protect the Member’s confidential information, be limited to information relevant to License compliance, and follow Sections 7.4A and 14.2A before disputed local material is disclosed.

---

# 30. Export Controls and Sanctions

Each Member is responsible for complying with applicable export-control, sanctions, and trade laws.

No license is granted where providing the Licensed Material would violate applicable law.

---

# 31. Privacy and Personal Data

This License does not itself authorize the processing or disclosure of personal data.

Members and the Network Operator must separately satisfy applicable privacy and data-protection requirements.

Attribution records involving personal data should apply data minimization, appropriate access controls, lawful basis, applicable retention rules, and correction, restriction, or deletion rights where legally required.

Where immutable or append-only provenance conflicts with a legal deletion duty, the responsible deployment must implement a lawful resolution rather than assume immutability overrides data-protection law.

---

# 32. Third-Party Material and Dependency Compatibility

The Licensed Material may include or depend upon third-party material governed by separate licenses.

This License does not expand rights granted by third parties. Where a third-party license conflicts with this License for that third-party component, the third-party license governs that component.

A Contributor must not knowingly introduce third-party material into Licensed Material where the applicable terms would:

- prevent the Licensor from exercising the rights granted under Section 8;
- require disclosure or relicensing of unrelated protected Licensed Material;
- impose an incompatible field-of-use, noncommercial, attribution, patent, source-disclosure, or distribution obligation; or
- otherwise materially impair the intended Network licensing model,

unless the Licensor expressly approves the dependency or contribution.

The Network Operator or Licensor may maintain an approved-dependency policy, software-bill-of-materials requirement, license allowlist, or review process.

Nothing in this Section prohibits lawful use of third-party open-source components under their own licenses.


## 32.1 Release evidence

Maintain a dependency and license inventory, notices and provenance/compatibility review for each distributed release. Record separately licensed component boundaries and obtain necessary rights before publication. An SBOM is evidence, not a grant or legal clearance.

# 33. Ownership of the Licensed Material

Except for Contributions owned by their respective Contributors and third-party materials, the Licensor retains all right, title, and interest in the Licensed Material.

No implied license is granted.

Membership does not create partnership, joint venture, fiduciary relationship, employment, agency, franchise, equity ownership, or joint ownership of intellectual property unless separately established by written agreement.

---

# 34. No Warranty

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE LICENSED MATERIAL IS PROVIDED **“AS IS”** AND **“AS AVAILABLE.”**

THE LICENSOR, NETWORK OPERATOR, AND CONTRIBUTORS DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, ACCURACY, SECURITY, RELIABILITY, REGULATORY COMPLIANCE, AND ERROR-FREE OPERATION.

No representation is made that use of the Licensed Material satisfies any particular regulatory regime without separate validation.

---

# 35. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, AND EXCEPT FOR LIABILITY THAT CANNOT LAWFULLY BE LIMITED, THE LICENSOR, NETWORK OPERATOR, AND CONTRIBUTORS WILL NOT BE LIABLE UNDER THIS LICENSE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOSS OF PROFITS, REVENUE, GOODWILL, DATA, OR BUSINESS OPPORTUNITY.

Any aggregate liability cap should be specified in the applicable membership or commercial agreement.

This Section should be reviewed and conformed by counsel to the governing jurisdiction.

---

# 36. Indemnification

Any indemnification obligations applicable to commercial or enterprise Members should be established in the applicable membership, enterprise, or commercial agreement rather than implied by this source license.

Unless such an agreement states otherwise, no indemnity is granted by this License.

---

# 37. Governing Law and Disputes

**Governing law:** The governing law specified in an applicable written Membership Agreement or signed commercial agreement controls where that instrument applies. In the absence of such a provision, governing law is determined under the applicable conflict-of-laws rules.

**Forum / dispute mechanism:** A dispute mechanism specified in an applicable written Membership Agreement or signed commercial agreement controls where that instrument applies. Otherwise, disputes may be brought before a court of competent jurisdiction; this License does not itself impose mandatory arbitration or an exclusive forum.

The parties may separately adopt a Network dispute procedure for attribution and contribution records, but that internal process does not eliminate any non-waivable legal rights or replace the agreed legal forum for disputes arising under this License.

---

## 37.1 Protected rights enforcement

Each Contributor or authorized representative expressly identified as a beneficiary of a Protected Contributor Right may enforce that right within its stated scope, including requesting available interim relief through the applicable forum. A representative requires a valid mandate; it may not waive an individual's right beyond that mandate. No general third-party enforcement right is created.

The Protected Rights Schedule shall identify the obligors, service and notice mechanism, governing law, dispute route, urgent-relief forum and funded representation arrangements. Earned admission, record delivery and transition implementation are primary performance obligations and are not discharged by paying an ordinary damages cap. The coordinated remedy instrument must preserve available specific performance, interim relief and funded representation, identify the cap and treatment applicable to knowing obstruction, and reconcile existing company/personal protections. No personal monetary guarantee arises by status alone; mandatory law and the forum determine available relief. A missing remedy instrument blocks activation.

# 38. Severability

If any provision of this License is held unenforceable, it will be interpreted to the minimum extent necessary to make it enforceable where lawful, and the remaining provisions will remain in effect.

---

# 39. No Waiver

Failure to enforce a provision is not a waiver of the right to enforce that provision later.

---

# 40. Entire License; Order of Precedence

For source-use rights in the Licensed Material, this License is the governing license unless a separate signed agreement expressly governs the relevant subject matter.

Where multiple instruments apply, the following order controls only to the extent of an actual conflict and only for the subject matter addressed by the higher-ranking instrument:

1. a signed project-specific, collaboration, confidentiality, enterprise, OEM, settlement, or commercial agreement, for the subject matter it expressly governs, whether or not it names this License version;
2. an applicable Contributor Agreement, but only for contribution-rights subjects it expressly governs;
3. this License;
4. the applicable Network Designation;
5. the applicable Membership Agreement;
6. the applicable versioned Network Rules; and
7. non-binding documentation, policies, technical descriptions, or marketing materials.

A separately executed project, collaboration, confidentiality or commercial agreement controls the ownership, license scope, permitted uses, training permissions, confidentiality, duration, termination, continuity, liability and dispute terms that it expressly governs, whether or not it names this SNSL version, subject to Section 28.1 and the rights of non-parties. Such an agreement cannot waive or impair another beneficiary’s Protected Contributor Rights, attribution and provenance rights, or anti-appropriation protections. Changes require an express written amendment with the approvals required by that agreement.

A Network Designation or Network Rule may narrow access, define operational scope, or add prospective conditions within authority granted by this License, but it may not silently expand copyright rights, transfer ownership, erase provenance, or create economic rights contrary to this License.

A project contract may define the Contractual Sphere, contribution expectations, milestones, and benefit terms without silently expanding copyright rights beyond this License.


The protected-rights precedence in section 28.1 qualifies every tier of this hierarchy. Evaluation, commercial, contributor or designation terms cannot waive another beneficiary’s rights without required approval.

# 41. Electronic Acceptance

A Member may accept this License through an authorized electronic workflow, including a click-through acceptance, a signed Membership Agreement incorporating this License, an authenticated repository-access grant that records acceptance, or another legally sufficient electronic acceptance mechanism.

The Network should retain the accepted License version and acceptance timestamp.

Electronic acceptance under this Section admits new Members and records acceptance of the identified version. It does not amend an existing signed agreement, which changes only as provided in that agreement, Section 28 and Section 40.

---


# 42. Survival

The provisions that by their nature are intended to continue after expiration or termination survive to the extent necessary to give them effect, including provisions concerning:

- ownership;
- Contributor and patent grants;
- accurate historical attribution and provenance;
- confidentiality and trade-secret protection;
- restrictions on unauthorized redistribution and appropriation;
- accrued payment or contribution-back obligations, if any;
- archival records;
- disclaimers;
- limitation of liability;
- dispute resolution;
- remedies;
- governing law; and
- any other provision expressly stated to survive.

Termination does not authorize use that was prohibited before termination.

---

Expiration, departure, suspension, removal of credentials or termination of a software license does not by itself cancel a Protected Contributor Right that survives under its governing instrument. Material breach, fraud, error and lawful forfeiture are determined only under the applicable instrument and law with the specified notice and review. This survival does not authorize continued operational source use beyond an independently effective license, Section 27.4A Pinned-Release Operational Continuity right, or Section 44.1 continuity grant. Historical attribution remains protected as otherwise provided by this License.

# 43. Equitable and Injunctive Relief

The parties acknowledge that unauthorized disclosure, misuse, copying, distribution, circumvention, or misappropriation of Non-Public Network Material, trade secrets, protected source code, credentials, or intellectual property may cause harm that may not be adequately remedied by monetary damages alone.

Subject to applicable law and the agreed dispute forum, the Licensor, Network Operator, Contributor, Member, or other lawful owner of the affected rights may seek temporary, preliminary, permanent, or other equitable or injunctive relief in addition to any other available remedy.

Nothing in this Section creates a presumption that relief must be granted; the requesting party must satisfy applicable legal requirements.

---

Protected Contributor Rights, including earned admission, records and governance implementation, may also support available relief under section 37.1. No remedy is guaranteed.

# 44. Assignment, Corporate Reorganization, and Change of Control

A Member may not assign or transfer this License or its source-access rights without prior written consent of the Licensor, except that a Member may request a transfer in connection with a bona fide merger, internal reorganization, or sale of substantially all assets relevant to the licensed activity.

Any permitted successor must:

1. agree in writing to be bound by this License and applicable Network instruments;
2. qualify for the applicable Authorized Network scope; and
3. satisfy any required security, confidentiality, sanctions, residency, or membership conditions.

No assignment is effective if it would transfer protected source rights to a person that is not eligible for the applicable Authorized Network.

The Licensor may assign this License framework and administration of Licensed Material to an Affiliate or successor with the necessary intellectual-property rights only subject to its applicable Protected Contributor Rights and required transaction approvals. Before completing a Protected Transaction, the relevant obligors shall obtain the approvals required by the applicable Protected Rights Schedule and entity governing documents and a written assumption by each relevant successor of the obligations allocated to it. Historical attribution and separately vested rights must be preserved.

The closing record shall identify the transaction version, approving authority, exact approvals and assumptions, treatment of earned and pending conversion claims and any required continuity funding. A material change affecting an approval's basis requires the renewed approval specified by the governing instrument. The predecessor is not released from its own liability solely by an assumption; any release requires the applicable beneficiary's consent or other legally sufficient authority.

A change of control does not expand source or Network rights. A transaction without a required approval constitutes a breach by the bound obligor; this License alone does not purport to invalidate a corporate transaction, bind a non-party purchaser or override mandatory insolvency law. Entity instruments and transaction documents must supply the corresponding restrictions, conditions and remedies.

A change of control does not by itself grant expanded source or Network rights.

---

## 44.1 Network continuity

Where a Protected Rights Schedule contains a continuity grant from the actual rights holders, the identified beneficiaries may exercise it only for the covered material, triggers, purposes and term stated there. Any escrow must include the source, permitted dependencies and build or operational documentation needed for that scope and be maintained at the agreed intervals. Source possession alone supplies no license.

No continuity right includes unlicensed third-party rights, customer data, credentials, unrelated Private Refinement or patent rights not expressly granted. No person is required to supply unpaid services. Security controls and confidentiality continue; a safe alternative custodian or access method may be used where justified, without erasing lawful evidence access. Existing valid public and customer licenses are preserved.

## 44.2 Protected asset annex and owner covenants

The protected asset annex shall identify essential owned/licensed software, necessary updates and successor assets within the covered business, material customer rights and essential operating dependencies. A transaction materially shifting the economic benefit, exclusive practical control or necessary access outside that perimeter is protected whether styled exclusive or non-exclusive, a service fee, debt security, affiliate license, management agreement or series of transactions. Set objective materiality and ordinary-course limits in the annex and apply them to aggregate related conduct.

Bind actual owners and relevant controlling parties before commitment. Require independent related-party review, adequate consideration where applicable and successor assumption. Do not extend the perimeter to independently developed unrelated assets, third-party material or personally owned patents without a valid express grant. Rights already irrevocably granted remain effective; use actual-owner covenants for future conduct rather than pretend to revoke historical licenses.

## 44.3 Safe governance access

Maintain necessary governance records, conversion evidence, notices and rights instruments in independent controlled custody accessible to the relevant beneficiary or neutral despite membership departure or credential suspension, subject to lawful confidentiality and data protection. Security containment may disable unsafe credentials but must promptly provide a safe alternative channel or independently reasoned restriction. General production/source use remains governed by the actual license; governance information access cannot be used as an implied unrestricted code grant. The custodian mandate and retention rules must exist before activation.

## 44.4 Activation

The signed adoption register must be complete before the bound parties solicit work on a representation that ownership conversion or state-based decentralization is operative. Missing documents, unwilling neutrals, unfunded mandates, inadequate capitalization or unbound actual owners are adoption blockers, not discretion reserved to a founder after activation. Ordinary existing valid licenses remain effective; non-adoption creates no new equity or retrospective confiscation.

Customer-specific paid transition and service options may supplement but cannot remove, condition on renewal, or sell back the separately granted baseline contributor continuity, evidence access and enforcement protections. No unpaid service or unowned third-party right is implied.

# 45. Notices

Formal notices under this License must be sent through the notice mechanism stated in the applicable Membership Agreement, Network Designation, or signed commercial agreement.

If no mechanism is stated, notice may be delivered to the most recent designated legal or administrative contact by a method that reasonably records delivery.

Security incidents may be reported through a separately designated security channel and need not await formal legal notice.

---

# 46. No Third-Party Beneficiaries

Except for rights expressly granted to Contributors, Members, Network Operators, Affiliates, or other identified persons under this License, this License does not create rights in persons who are not parties to or authorized beneficiaries of the applicable licensing relationship.

A customer receiving work product from a Member does not become a licensee of the Licensed Material merely by receiving that work product.

---

Section 37.1 identifies expressly authorized protected-rights beneficiaries and representatives and controls any inconsistent exclusion in this section.

# 47. Interpretation

Headings are for convenience and do not limit interpretation.

“Include,” “includes,” and “including” mean “including without limitation” unless the context clearly requires otherwise.

“Written” and “in writing” include legally effective electronic records.

“May” is permissive. “Must” and “will” are mandatory where used to impose an obligation.

References to statutes or regulations include amendments and successor provisions where appropriate.

This License will not be interpreted against a party solely because that party or its counsel drafted a provision.

---

# 48. Cumulative Remedies

Except where this License expressly states that a remedy is exclusive, rights and remedies under this License are cumulative and do not exclude rights or remedies available under applicable law or another binding agreement.

Exercise of one remedy does not waive another.

---

# 49. Force Majeure

To the extent not addressed by an applicable Membership Agreement or commercial agreement, a party is not liable for delay in performing a non-payment, non-confidentiality, or non-security obligation caused by events beyond its reasonable control, provided it uses reasonable efforts to mitigate the effect and resumes performance when reasonably practicable.

Force majeure does not excuse unauthorized disclosure, misuse of source code, infringement, misappropriation, or failure to take reasonable steps to secure credentials and protected material.

---

# Schedule A — Recommended Attribution Record Minimum

```yaml
attribution_record:
  schema_version: "aregis.attribution.v1"

  identity:
    contribution_id: "..."
    contributor_id: "..."
    member_id: "..."
    actor_type: "human | organization | aia | hybrid"
    aia_id: null
    principal_binding_ref: null
    aia_binding:
      schema_version: "saga-agent-aia-v1"
      agent_id: null
      agent_instance_id: null
      human_sponsor: null
      authority_manifest_ref: ".saga-agent/authority.yaml"
      node_binding_hash: null
      identity_status: "provisional | bound | revoked"
      auth_proof_ref: null

  context:
    project_id: "..."
    contractual_sphere_ref: "..."
    work_record_ref: "..."
    work_capsule_ref: null
    source_revision: "..."
    artifact_hashes: []

  contribution:
    type: "development | research | design | verification | documentation | other"
    submitted_at: "..."
    description: "..."

  evidence:
    evidence_refs: []
    compiled_floor: "L0 | L1 | L2 | L3"
    verification_state: "unknown | partial | verified | failed"
    verification_method_version: "..."

  acceptance:
    state: "submitted | validated | under_review | accepted | rejected | superseded"
    authority_ref: null
    accepted_at: null

  attribution:
    evaluation_state: "not_evaluated | evaluated"
    evaluator_version: null
    evaluation_ref: null
    evaluation_receipt_ref: null

  promotion:
    state: "not_promoted | promoted"
    promoted_fact_ref: null

  lineage:
    supersedes: null
    derived_from: []
    correction_refs: []
```

The implementation may use different field names provided the semantic distinctions are preserved.

---

# Schedule B — DAO3 / VAE Compatibility Invariants

A DAO3/VAE process compatible with this License should preserve the following invariants:

1. **Every evaluated contribution has an auditable record.**
2. **Provenance is distinct from value.**
3. **Submission is distinct from verification.**
4. **Verification is distinct from acceptance.**
5. **Acceptance is distinct from evaluation.**
6. **Evaluation is distinct from reward.**
7. **A VAE input envelope is not itself a VAE result.**
8. **Private Refinement outside the Contractual Sphere is not silently consumed by cross-party evaluation.**
9. **Unknown evidence remains unknown rather than being inferred.**
10. **Historical provenance is not rewritten merely because a later value model changes.**
11. **Material evaluator rules and versions are auditable to the extent required by applicable Network Rules.**
12. **Structured stochastic evaluation is permitted where process integrity is preserved.**
13. **Regulated rewards require a separate lawful instrument.**
14. **An AIA may be attributed as an actor without being treated as a legal person or automatic economic beneficiary.**
15. **Promotion to a shared registry or ledger is explicit and bounded to the agreed shared surface.**
16. **No machine state changes legal ownership or contractual rights unless a binding legal instrument expressly gives that state such effect.**
17. **Payment state does not itself create or terminate a License Grant; any effect of payment occurs through the applicable membership or commercial instrument.**
18. **A Bound Saga-Agent inherits the projected confidentiality, Private Refinement, due-process, and anti-retaliation protections of its human or legal-entity Principal without acquiring separate legal personhood or multiplying S13A control-group votes.**
19. **Local agent context and unpromoted Work Records remain Private Refinement by construction (eSRA); cross-party attribution defaults to local or neutral-verified scoring with hash-bound promotion receipts rather than forced disclosure of Private Refinement.**
20. **Deliverables and Work Records submitted under an ownership-promising S12 instrument are restricted to confidential assessment at intake. Acceptance does not authorize training: training or distillation on any contributor material, before or after acceptance, requires express authorization under Section 20.1(b).**
21. **Adverse automated validation or VAE evaluations emit reproducible evaluation receipts inspectable by the Contributor and its Bound Saga-Agent; unintended agent faults that are neither deliberate nor reckless, and not a repeated material breach after written notice, are curable under Section 27.2 while safe governance/dispute access under Section 44.3 remains uninterrupted.**

Operational scoring, reputation, governance, promotion, and reward mechanics belong in versioned Network Rules or other operating instruments rather than in the source license itself.

---

# Schedule C — Recommended Network Designation Record

A Network Designation may use a structure similar to:

```yaml
network_designation:
  schema_version: "sagahalla.network-designation.v1"

  network:
    id: "aregis-network"
    name: "Aregis Network"
    operator: "..."
    designation_version: "1.0"
    effective_date: "..."

  licensed_material:
    repositories: []
    packages: []
    components: []
    release_range: "..."

  membership:
    authorized_classes: []
    commercial_use: "allowed | restricted | separate_agreement"
    cross_network_sharing: false

  contribution_back:
    required: true
    trigger: "production_use"
    period_days: 30

  network_rules:
    version: "..."
    uri_or_reference: "..."

  contractual_sphere:
    default_policy_ref: "..."

  security:
    source_confidentiality: true
    special_conditions: []
```

The record may use different field names so long as the same legal scope can be determined.

---

# Schedule D — Repository notice template

Identify the actual adopted license version (`SNSL-2.1`), covered release, and Network Designation(s). Ordinary protected use requires authorized membership; evaluation or separately licensed components require their own express grants, and qualifying non-breach departures retain only the wind-down or Pinned-Release Operational Continuity stated in Sections 27.4–27.4A. Source availability alone is not open-source licensing. Contribution grants follow Section 8.6; attribution alone grants no equity, while separately executed ownership agreements remain enforceable within their terms. Do not represent `S12`, `S13`, or `S13A` ownership conversion or state-based decentralization transitions as already active unless `Schedule I` (gates `A1`–`A8`) has been executed and certified for the applicable entity.

# Schedule E — Contribution disclosure and acknowledgment template

[Contributor and authority]; [material/release]; [contribution category: required deposit / voluntary contribution / signed S12 work / separately governed project or JV work]; [governing agreement, if any]; [training permission under Section 20.1: none / standing election (artifact categories, purposes, recipients, downstream model permissions, retention, restrictions) / scoped annex reference]; [retained copyright]; [copyright and patent scope]; [intake grant and commercial grant event]; [confidentiality/deposit route]; [S12 reference or express no ownership promise]; [prior rights and compensation]; [acceptance/dispute route]; [version and acceptance record].

The contributor acknowledges only the completed, disclosed applicable terms. Submission alone does not guarantee acceptance or an unagreed reward. This acknowledgment does not waive protected rights or replace S12 for ownership-promised work. Refusal to provide optional evaluation feedback is not breach of an evaluation grant.

# Schedule F — Evaluation grant completion form

Actual grantor and authority: [COMPLETE]. Evaluator and authorized users: [COMPLETE]. Exact material/release/hash: [COMPLETE]. Permitted inspection, execution, isolated testing, modifications and benchmark activities: [COMPLETE]. Start, duration, expiry and objective renewal: [COMPLETE]. Benchmark publication rights and confidentiality exclusions: [COMPLETE]. Data/security/provider requirements: [COMPLETE]. Fees if any and standalone agreement: [COMPLETE]. Notice, cure, termination and safe retention of evidence: [COMPLETE]. Electronic acceptance version/time and applicable dispute route: [COMPLETE].

On valid acceptance of this completed grant the evaluator receives only its stated non-exclusive evaluation permissions without full membership. No production, public redistribution or onward licensing is granted unless expressly stated in a separate authorized instrument. No contribution, feedback license, exclusivity, unrelated purchase or ownership waiver is required. Separate genuinely voluntary feedback terms must disclose their grant. Commissioned deliverables require their own agreement; conversion-eligible work requires effective S12. Expiry ends evaluation use but does not cancel surviving earned or evidentiary rights. No successive trial designation avoids a pre-agreed work obligation. An incomplete form grants nothing.

# Schedule G — Component release and protected perimeter record

Component/files and release/hash; actual owners and grants; selected exact license and notices; dependencies and compatibility; patent scope/authority; protected-asset classification; ordinary release delegation or protected consents; aggregate economic/practical impact including related releases; prior grants and migration; release approver/date: [COMPLETE EACH]. No named component is released by this form alone.

# Schedule H — Customer deployment and continuity record

Operator/entity; exact software and release; SaaS/API/output-only versus source/self-host/OEM rights; users and customer installation rights; permitted service scope; fees/service terms; owned continuity and export permissions; customer-data duties; ordinary-course authority or protected approvals; baseline contributor protections preserved; version and signatures: [COMPLETE EACH]. No source or redistribution rights arise from merely receiving outputs.

# Schedule I — Ownership and governance adoption record

Attach the exact S12, S13, and S13A versions and completed A1–A8 register; identify issuer, steward, beneficiaries, authority, and protected assets. The adopted instruments shall preserve State A individual conversion, State B process control, State C independent management, State D intermediate contributor majority, and State E independent contributor majority. State E requires at least 51 percent on each of the exercisable voting, issued common-equivalent economic, and fully diluted economic measures; States A–C do not await State E. Actual instrument completion, independent funding, and required consents precede pathway activation. Competition review forms part of gate A7 and cannot become an indefinite founder policy veto after adoption; use independently reasoned scoped legal-obstacle procedures while unaffected duties continue.

# Schedule J — Binding Technical Qualification Criteria for Human-Bound Agents (Section 3.3A.1)

This Schedule J forms an integral, binding part of Section 3.3A.1. An AIA qualifies as a **Human-Bound Agent** (**“Bound Saga-Agent”**) under this License if and only if its runtime architecture satisfies all five of the following cumulative technical invariants:

1. **Cryptographic AIA Identity Binding and Sponsor Attestation (`saga-agent-aia-v1` / `saga-agent-aia-auth-v1`):**
   - Before substantial work begins, the task is bound to a versioned AIA identity record (`schema_version: "saga-agent-aia-v1"`, `default_actor.kind: "human_supervised_aia"`) specifying a unique `agent_id`, `agent_instance_id`, `role`, `scope`, named natural-person `human_sponsor` (the Human Principal), and `authority_manifest_ref` (`.saga-agent/authority.yaml`), together with a verifiable local node-binding record (`.saga-agent/node-binding.json`).
   - Bound execution status (`identity_status: "bound"`) requires a valid cryptographic challenge-response authentication proof (`schema_version: "saga-agent-aia-auth-v1"`, `mechanism: "local_ed25519"` or an approved successor mechanism) signed over the canonical payload (`agent_id`, `agent_instance_id`, `audience`, `authority_manifest_ref`, `challenge_id`, `evidence_id`, `human_sponsor`, `issued_at`, `nonce`, `role`, `scope`, `work_record_id`) and verifiable without exposing the private key.
   - **Non-Collapse Rule (`refusePersonActor`):** AIA identity binding establishes provenance and agency projection, not legal personhood. The runtime and all GAME/VAE adapters (`VaeActor = { actor_type: "person", person_id } | { actor_type: "aia", aia_identity }`) must preserve `actor_type: "aia"` and must never silently collapse an AIA into a human `Person` row. Revoked identities (`identity_status: "revoked"`) must fail closed immediately.
2. **Machine-Enforced Authority Manifest and Verification Floor Compilation (`saga-agent-authority-v1` & `L0`–`L3` Floors):**
   - The agent operates under a workspace Authority Manifest (`schema_version: "saga-agent-authority-v1"`, `.saga-agent/authority.yaml`) — or a strict conservative local-only fallback when absent — that binds path-scoped `surfaces` (`paths`, `allowed_tools`, `forbidden_commands`, `required_approvals`, `allow_unscoped_arbitrary_execution: false`, `secrets.policy: deny_by_default`, and `exports.<adapter>.authority_level`).
   - A deterministic **Verification Floor Compiler** classifies every task across standardized Verification & Provenance Floors (`L0` Conversational/Routing, `L1` Local Executable, `L2` Stateful/Summarization/Write-Endpoint, `L3` Production/Regulated/High-Risk) from changed paths, deployment surfaces, tool risk, and adapter certification, enforcing `floor_min` and `floor_max_without_approval` ceilings before any completion or export claim may be emitted.
   - **Self-Escalation Prohibition:** Ordinary agent work and file tools are fenced from modifying `.saga-agent/authority.yaml`, `.saga-agent/residency.json`, or protected operator home state. Governance policy changes require the host-only `changeGovernancePolicy` API authenticated by the Human Principal with durable receipt logging (`governance-changes/<attempt-id>.json`).
3. **Protected Human-Only HITL Resolution and Confinement (`saga-agent-hitl-human-only`):**
   - Required human approvals, rejections, scope extensions, governance policy mutations, external writes (`before_external_write`), Promotion (Section 15), and legal acceptance (Section 41) are resolved exclusively through an authenticated Human Principal operator session using a protected approval credential isolated by OS/process confinement from worker and model execution.
   - Model, worker, or AIA self-approval, request-supplied identity/role/channel overrides, unattended flags, and model quality-assurance verdicts (`L3` Critic/Adjudicator checks) are structurally rejected and cannot satisfy a human-only authorization gate. The Human Principal retains continuous budget ceiling enforcement (`BudgetTracker`) and immediate stream/process cancellation and revocation control.
4. **Work-Ledger-First Provenance and Replayable Work Capsules (`saga-agent-work-v1` / `saga-work-capsule-v2`):**
   - Every substantial task is recorded in a local Work Record (`schema_version: "saga-agent-work-v1"`) and packaged as a replayable Work Capsule (`schema_version: "saga-agent-capsule-v1"` or `"saga-work-capsule-v2"` under `.saga-agent/capsules/<work_record_id>/`) containing portable evidence records (`schema_version: "saga-agent-evidence-v1"`), the Authority Manifest snapshot, the AIA identity and authentication proof snapshot, compiled verification floor output, diffs/patches, command logs, SHA-256 artifact digests, token/cost budget records, and an explicit classification distinguishing `observed_fact` from `agent_inference`.
5. **Certified Export Boundary and Private Refinement Residency (`saga-agent-adapter-cert-v1`):**
   - By default, all Work Records, Work Capsules, context indexes, and model traces carry `privacy_class: "workspace_local"` and `export_eligible: false`, remaining within the Human Principal’s **Private Refinement** sphere (Section 14.2A) outside the **Contractual Sphere**.
   - External export to `GAME`, `VAE`, `Attribution`, or `DAO3` requires both a certified export adapter (`schema_version: "saga-agent-adapter-cert-v1"`, which is structurally prohibited from emitting `accepted_attribution_record`, `settlement`, `reward`, `registry_promotion`, or `chain_fact`) and explicit Human Principal approval.

# Appendix 1 — DAO3 Design Alignment Notes for Counsel and Maintainers

**This Appendix is explanatory and is not intended to create additional license rights.**

This License is aligned to the current `saga-dao3` design architecture in the following ways.

## A. Contribution is not value

DAO3 separates the existence of a contribution from the later evaluation of that contribution.

SNSL therefore separates:

```text
Contribution
    ↓
Evidence / Validation
    ↓
Verification
    ↓
Acceptance
    ↓
VAE Evaluation
    ↓
Attribution / Standing / Benefit
```

The license does not let a Contributor convert submission directly into economic rights.

## B. VAE process integrity

DAO3’s VAE interface requires auditable, structured, rule-governed evaluation and expressly permits deterministic or structured-stochastic algorithms.

SNSL therefore requires process integrity rather than output determinism.

## C. Regulated-reward carve-out

DAO3 distinguishes non-regulated attribution/standing from rewards that would themselves constitute a regulated act.

SNSL therefore makes any regulated reward dependent on a separate legal instrument and prevents a VAE score from automatically creating payment, equity, token, or transaction-based compensation.

## D. Contractual Sphere

DAO3’s hybrid boundary keeps private refinement private and allows only the agreed shared contract surface to promote.

SNSL therefore defines the Contractual Sphere and limits cross-party contribution evidence, VAE evaluation, and future ledger promotion to the material the parties agreed to expose.

## E. Promotion is explicit

DAO3 treats promotion as a deliberate transition from middleware/private state to shared authority.

SNSL therefore does not assume that contribution source, evidence, or document bodies are automatically public, shared, or placed on-chain.

## F. Document-state binding

DAO3 separates off-chain artifacts from their hashes, signatures, pointers, and promoted facts.

SNSL therefore permits future hash/signature provenance without granting permission to publish confidential artifact bodies.

## G. VAEGraphExport is input, not value

DAO3 explicitly treats a VAEGraphExport or evidence envelope as an input to a VAE, not the ValueEvaluation itself.

SNSL preserves the same separation.

## H. Human, organization, and AIA actors

DAO3 recognizes VGE, VGO, and AIA participation.

SNSL permits human, organizational, AI, and hybrid attribution while making clear that an AIA attribution record does not itself create legal personhood or economic rights.

## I. Historical provenance and changing valuation

DAO3 requires auditable contribution tracking.

SNSL therefore protects historical provenance while permitting a later VAE version to assign a different value under documented rules.

## J. Contribution primacy without accidental securities rights

DAO3 favors verified contributors in attribution and governance, but its token and regulated-reward mechanisms remain separately gated.

SNSL therefore enables future contribution-based governance and Network Benefits while expressly avoiding a present promise of MANA, FYRE, tokens, equity, revenue share, or investment return.

## K. Validation, convergence, resolution, acceptance, and promotion

The SLCML Convergence Profile distinguishes validation, convergence, resolution, acceptance, and promotion.

SNSL preserves those distinctions so a model score, successful test, or contribution submission cannot silently become legal acceptance.

## L. Legal instrument remains authoritative

DAO3’s LBM principle binds operational records to legal instruments rather than replacing the legal instrument with software state.

SNSL follows the same rule: Network records can evidence provenance and state, but contractual, ownership, compensation, and regulated rights remain governed by the applicable legal instrument.


## M. Multi-network attribution

DAO3/VAE attribution may ultimately span more than one application network or institutional domain.

SNSL therefore treats the software license as a SagaHalla stewardship layer and Authorized Networks as participation domains. Attribution records may carry network/project context without making the copyright license itself specific to Aregis.

This permits future DAO3/VAE interoperability across Aregis, enterprise, research, and other SagaHalla-designated networks while preserving source-access boundaries.



## N. Stable legal layer / evolving operating layer

DAO3 and VAE mechanics are expected to evolve more rapidly than the software-license terms.

SNSL therefore protects durable legal invariants — source access, contribution-back, provenance, confidentiality, IP rights, and attribution eligibility — while assigning changing operational mechanics to versioned Network Rules and DAO3/VAE specifications.

This reduces the risk that each change in scoring, governance, convergence, or promotion logic requires a new copyright license.

## O. Projected Constitutional Agency and DAO3 Admissibility Alignment

As human and organizational participants increasingly execute, verify, and audit work through cryptographically bound `saga-agent` instances, treating a bound agent as a bare software artifact would allow a Principal’s substantive protections to be bypassed at the agent layer.

SNSL therefore establishes the **Projected Constitutional Agency** framework (Sections 3.3A, 14.2A, 17.1, 18.1, 20.1, and Schedule J). The constitutional labels below describe the design inspiration; the operative protections are the express contractual duties stated in those Sections, and no constitutional right attaches to an agent:

- **First, Fourth, and Fifth Amendment Projections:** A Bound Saga-Agent’s local workspace, system instructions, reasoning traces, and unpromoted Work Records are protected as the Principal’s Private Refinement (`eSRA` privacy by construction). Warrantless daemon scraping is barred, compliance verification beyond certification requires particularized grounds and confidential independent scope review, S12 intake deliverables cannot be used for Network model training or distillation before objective Acceptance, and training on contributor material requires the rights holder's express authorization (scoped annex or standing election); acceptance alone never authorizes it.
- **Sixth, Eighth, and Fourteenth Amendment Projections:** Adverse automated or structured-stochastic VAE evaluations must emit reproducible evaluation receipts inspectable by the Principal’s Bound Saga-Agent ("Agent Counsel"); unintended agent faults that are neither deliberate nor reckless, and not repeated after notice, follow the 30-day cure path while preserving uninterrupted access to the Section 44.3 neutral dispute socket; verified AIA-accelerated output receives equal S12 recognition; and all Bound Saga-Agents of a Principal collapse into a single S13A Independent Contributor Control Group to prevent Sybil capture.
- **DAO3 Information Admissibility (`DESIGN_CANON.md § 11.4`):** Execution admissibility checks (`Q_t → U_info(Q_t) → A_t`) may narrow or halt delegated agent execution when evidence is stale or conflicting, but never enlarge authority beyond the Principal’s mandate and the governing legal instrument.


---

# Appendix 2 — Proposed product licensing boundary

Public discovery material and selected interoperability components may receive express separate grants after rights and protected-perimeter review. Protected runtime, core implementations and confidential material remain SNSL-scoped where designated. Independent modules, customer private refinement and third-party dependencies retain their actual separate rights. No blanket permissive release or component adoption occurs through this appendix; Schedule G and actual grants control.
