# SagaHalla Network Source License (SNSL) v1.0 **Effective date:** 6 October 2026 **Status:** Final version 1.0 — adopted for designated Saga GAME material; payment-neutral membership/license architecture **Intended model:** SagaHalla-stewarded, member-restricted source access across designated Authorized Networks, with reciprocal contribution-back, durable provenance, and future DAO3/VAE-compatible attribution governed by separate versioned Network Rules **License character:** Source-available / network-restricted; **not** an OSI-approved open-source license **Defined-term status:** Operative capitalized terms are normalized in Section 3; project-specific instruments may add scoped definitions only where expressly permitted. **Version identifier:** `SNSL-1.0` > **Licensor:** Procept Partners LLC-S Series Sagahalla, an Indiana LLC ("SagaHalla"). **Initial designated network:** Aregis Network. The applicable Network Designation determines covered material and participation scope. Separate legal review notes are maintained outside this License. --- ## 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 five principles: 1. **Inspectable source within a governed network.** 2. **Use rights follow authenticated Network membership.** 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.** 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. --- # 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. --- # 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. ## 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.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 an 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. --- # 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. --- # 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. --- # 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.5 Commercial Exception The Licensor may grant a separate commercial license permitting private modifications without contribution-back. --- # 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/training data/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. 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. ## 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. --- # 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. --- # 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 should be governed by versioned, auditable Network Rules. 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. --- # 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. --- # 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.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. --- # 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. --- # 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 Subject to the Contractual Sphere, privacy requirements, and any project-specific restrictions, the Licensor and Network Operator may use Licensed Material, Accepted Contributions, permitted Attribution Records, non-confidential verification artifacts, and authorized Work Records to develop, train, fine-tune, evaluate, benchmark, or improve models and automated systems used by or for the Network. Private customer data and Private Refinement are not included unless separately authorized. ## 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.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. # 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. --- # 22. Interoperability and Public Interfaces Saga-owned SDKs, client libraries, protocol schemas, interface definitions, conformance fixtures, interoperability specifications and selected components are governed by this License when designated. No Apache-2.0 or other open-license exception is granted for Saga-owned material by this License. Third-party material remains under its own terms. Third-party material under a separate license remains governed by that license. No separate open-license grant for Saga-owned interfaces is made by this License. The publication of an interface does not expand the authorized use or redistribution scope of either the interface or its protected implementation. > **Support interoperability within authorized scope; preserve the same licensing boundaries for Saga-owned interfaces and implementations.** --- # 23. No External Redistribution Except for material separately designated under another license, 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. Ordinary work product produced through Network Use is not treated as Licensed Material solely because the Licensed Material helped create it. --- # 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 required for permitted archival or wind-down activity. ## 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 may begin; 2. repository, source, credential, and active Network access ends; 3. the Member may retain archival copies only as permitted by Section 14.5; 4. a **sixty (60) day** wind-down period applies to existing operational deployments unless a separate agreement provides otherwise; 5. during wind-down, use is limited to orderly migration, export, continuity, security, and cessation activities rather than new feature development; 6. the Member may export its lawful data, Work Records, and other records it is entitled to retain; and 7. the Member may seek a separate commercial license for continued use. ## 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. # 28. Versioning of This License and Network Rules This License is versioned. A later version of SNSL does not automatically replace this version for already licensed material unless the applicable release expressly permits migration to a later version or the Member affirmatively accepts the later version. 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. --- # 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, and be limited to information relevant to License compliance. --- # 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. # 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. --- # 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 modifies it. 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, enterprise, OEM, settlement, or commercial agreement that expressly states it modifies this License; 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 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. # 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. --- # 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. --- # 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. --- # 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 the administration of Licensed Material to an Affiliate or successor that acquires or succeeds to the relevant intellectual-property rights, provided the assignment does not erase historical Contributor attribution or vested rights created by a separate binding instrument. A change of control does not by itself grant expanded source or Network rights. --- # 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. --- # 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 context: project_id: "..." contractual_sphere_ref: "..." work_record_ref: "..." source_revision: "..." artifact_hashes: [] contribution: type: "development | research | design | verification | documentation | other" submitted_at: "..." description: "..." evidence: evidence_refs: [] 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 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.** 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 > **SagaHalla Network Source License (SNSL)** > Source access and use are limited to authorized members of a SagaHalla-designated Authorized Network under an applicable Network Designation. > The Aregis Network is an initial Authorized Network. Members may inspect, use, modify, and contribute to designated software subject to SNSL, their Authorized Network scope, and applicable Network Rules. Production modifications are subject to contribution-back. Accepted contributions retain durable provenance and may be eligible for future DAO3/VAE attribution. Attribution does not itself create a token, equity, payment, governance entitlement, or other economic right. > This software is source-available and is **not open-source software**. > Access to Non-Public Network Material should be provided only through authenticated, scope-controlled channels that retain the applicable License and Network Designation acceptance record. --- # Schedule E — Contributor Acknowledgment > I have authority to submit this Contribution. I agree that my original authorship may be preserved in the Network Attribution Record. I grant the Contributor licenses stated in SNSL. I understand that submission does not guarantee acceptance, value attribution, governance standing, payment, token allocation, equity, or other reward. If the Contribution is accepted, the Network may use it in accordance with SNSL, including future rule-governed evaluation and VAE-compatible attribution. --- # 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. --- # Appendix 2 — Recommended Product Licensing Boundary | Layer | Recommended treatment | | --- | --- | | Saga-owned architecture and educational material | SNSL; public access only when expressly designated | | Saga-owned interoperability schemas and SDKs | SNSL; no Apache-2.0 exception | | SagaHalla / Saga Agent protected runtime | SNSL | | Network-only profiles, adapters, and governance integration | SNSL | | Saga-owned VAE portable interface / contract | SNSL; no Apache-2.0 exception | | Saga-owned VAE scoring/reference engine | SNSL | | Customer-private data and Private Refinement | Not licensed to Network absent express agreement | | Regulated reward or token rights | Separate legal instrument only | --- For Saga Agent, the selected direction is SNSL across all Saga-owned workspace packages, including the daemon, GUI, shared protocol and SDK/interface material. Third-party materials retain their own licenses. The accompanying Saga Agent Network Designation defines the covered repository and package scope.