SOSL v1.0 — Sovereign Open‑Source License
A Digital Covenant Binding Code to Constitution
Preamble
SOSL is a rights‑first, community‑enforceable license for the Sovereign Constitution Fabric. It preserves open collaboration while ensuring that foundational Articles—erasure, consent, origin, self‑sovereignty—remain intact across derivatives and services.
1. Grant of Rights
Use, Modify, Distribute
Worldwide, royalty‑free rights to use, reproduce, modify, publish, and distribute the Work and Derivatives, including as a network service.
Patent Grant
Contributors grant a non‑exclusive patent license for their contributions. Rights terminate upon patent aggression.
2. Reciprocity
- Network Copyleft: If you operate the Work as a service, you MUST provide complete corresponding source to those users.
- Disclosure: Derivative changes MUST be marked; diffs against upstream MUST be published.
- Continuity: Derivatives MUST remain under SOSL v1.x (or later) with no additional restrictions.
3. Constitutional Invariants
The following Articles and safeguards are non‑removable:
- Article I — Right to Erasure (InfinityWipe™)
- Article V — Right to Consent (Universal Consent Layer™)
- Article III — Right to Origin (Quantum Origin Stamp™)
- Article IX — Right to Self‑Sovereignty (CSG‑1)
- Article X — Governance Anchor (Protocol 817)
- Public Attestations & Revocations (registries)
4. Open Attestations
| Artifact | Purpose | Where |
|---|---|---|
| Deployment Attestation | Code provenance & config digest | Public Registry (Merkle root + path) |
| Revocation Notice | Nullifies trust in a key/deployment | Revocation Channel (Council‑mirrored) |
| BPR Record | Binding Policy Resolution | Attestation Ledger with ΔΣ ref |
5. Dual Enforcement
- Legal: Injunctive relief, damages, and termination of rights under SOSL.
- Technical: Attestation revocation and public nullification events propagated via Council registries.
6. Governance & Amendments
Amendments are proposed under Protocol 817 and ratified by Council ballot with public, signed results. Mirrors may adopt stricter overlays if reciprocity and invariants are preserved.
7. Compatibility
| License | Network Copyleft | Rights Invariants | Attestation Duty | Technical Nullification |
|---|---|---|---|---|
| AGPL‑3.0 | Yes | No | No | No |
| SSPL‑1.0 | Yes | No | No | No |
| SOSL v1.0 | Yes | Yes | Yes | Yes |
8. Compliance Checklist
Operators
- Publish deployment attestations (hashes, versions, configs).
- Expose revocation endpoint; subscribe to Council feeds.
- Keep Articles I, III, V, IX, X enabled at all times.
- Log BPR artifacts, ΔΣ overlays, and time‑seals.
Distributors
- Ship full source + build scripts.
- Mark modifications and publish diffs.
- Include LICENSE‑SOSL, NOTICE, attestation pointers.
9. FAQ
Q: Can I build commercial products on SOSL?
A: Yes. Reciprocity applies to service operators; publish your source and attestations.
Q: Can invariants be disabled?
A: No. They are constitutional guarantees.
Q: What if publication is restricted by law?
A: Use ZKChronoSeal to publish finality without contents; follow Protocol 817 for lawful mirrors.
Appendix — SOSL v1.0 (Legal Excerpt)
Copyright © 2025 Sovereign Governance Council and contributors.
Permission is hereby granted, subject to the terms of this License, to any person obtaining a copy of the Work to use, reproduce, modify, publish, distribute, and operate the Work as a service, provided that all such activities comply with Sections 2–6 herein.
2. Reciprocity. If You offer the Work, or a Derivative, as a network service, You must make the Corresponding Source available to those users under this License, with build and installation instructions.
3. Invariants. You must not remove, disable, or circumvent Constitutional Articles I, III, V, IX, and X, nor the publication and revocation mechanisms defined by Standard‑817.
4. Attestations. You must publish cryptographic attestations of deployments and significant events, signed with PQC algorithms and time‑sealed via recognized mechanisms.
5. Enforcement. Upon material breach, rights granted herein terminate automatically. The Council may issue public revocation notices. Technical measures may render non‑compliant deployments unverifiable.
6. No Warranty. The Work is provided “AS IS”, without warranty of any kind.
This excerpt is non‑exhaustive. The authoritative text resides in the Council registry.