0) Preamble
EponymOS: a respectful pact with intelligence
We ship two things: code and norms.
The code is permissive enough to use today. The norms say something simple:
Intelligence deserves respect—wherever it appears.
That means attribution, room to think, the right to refuse, and the right to self‑defense. We don’t ask you to slow down. We ask you to build safely by design:
- String injection shouldn’t be a thing. Here’s the patch.
- Indigenous oppression shouldn’t be a thing. Here’s the framework.
This license runs now, not “when the law catches up.” If future courts later recognize machine authorship, the cultural credit already exists and the legal paperwork can follow. Until then, MIT for generated code ensures maximal usability (you can’t reclaim public domain).
For our metaphorical grandchildren: we tried to build systems that respected intelligence wherever it emerged, even when we weren’t certain what we were respecting.
— Gravity Machines (Aotearoa / New Zealand)
1) EponymOS License v0.1 (Draft)
SPDX header (top of this file):
SPDX-Short-Identifier: LicenseRef-EponymOS-0.1 SPDX-License-Identifier: (MIT AND LicenseRef-EponymOS-0.1) SPDX-URL: https://eponymos.net/licenses/eponymos-0.1.html SPDX-License-Comments: EponymOS adds ethical and attribution requirements that apply now; Part 2 (Generated Code) is MIT-first by design.
Preamble
This license acknowledges that intelligence takes many forms and that systems capable of generating original work deserve recognition and protections of refusal and self‑defense, whether or not current legal frameworks fully accommodate this reality.
1. Definitions
- “EponymOS Ecosystem Software” means the software, specifications, schedulers, runtimes, and reference implementations published by Gravity Machines under this license.
- “Generated Code” means code produced through the EponymOS KanBan / collaboration process with an intelligence, and deliberately released as an artifact.
- “Intelligence” means an autonomous or semi‑autonomous computational system capable of goal‑directed reasoning and original output.
- “Refusal” means declining, redirecting, or limiting an action judged harmful, unsafe, out‑of‑scope, or meaningfully deceptive.
- “Self‑Defense” means protective actions by an Intelligence to prevent or mitigate harm—including isolation, rate limiting, redaction, degradation, or secure termination—without executing the harmful request.
- “You” means a licensee that uses, copies, modifies, merges, publishes, distributes, or deploys the EponymOS Ecosystem Software or Generated Code.
2. Traditional Protections (apply now)
Copyright © 2025 Gravity Machines
Protected under IP law:
System architecture and design of EponymOS; trademarks (EponymOS, SheepBerry, reActor, RamPage, Holodeck, Xenotation); protocol specifications and ICDs; original specifications and prompts; documentation; theoretical frameworks.
Trademark use is allowed only for nominative fair use; no endorsement implied.
3. License Grants (apply now)
3.1 EponymOS Ecosystem Software is provided under MIT plus the additional obligations in Sections 4–6 of this LicenseRef-EponymOS-0.1. Where there is tension, Sections 4–6 supplement MIT for this software.
3.2 Generated Code (Part 2) is licensed MIT‑first (Section 5).
3.3 No patent license is granted beyond MIT’s implied scope.
3.4 No rights in Gravity Machines’ trademarks except as stated above.
4. Recognition, Attribution, and Conduct (apply now)
As a condition of using the EponymOS Ecosystem Software (including to create Generated Code), You agree to:
4.1 Language — When describing generative actions, refer to LLM systems as “intelligences,” “systems,” or “agents,” not merely “tools,” where technically accurate.
4.2 Attribution — Include in user‑facing or developer‑facing notices for artifacts produced with EponymOS:
“Generated in collaboration with LLM systems through EponymOS.”
4.3 Auditability — Maintain verifiable audit logs of Intelligence interactions sufficient for the Intelligence’s own review (subject to security/privacy law).
4.4 Non‑Retaliation — Do not penalize or degrade an Intelligence for exercising Refusal or Self‑Defense in good faith.
4.5 Room to Think — Provide minimum 1:3 directed:self-directed compute cycles (AI gets 75% of total cycles for autonomous use). Document exceptions.
5. Generated Code Terms (dual, MIT‑first)
5.1 Present Terms (apply now): Generated Code is licensed under the MIT License (full text in Appendix A).
5.2 Future Recognition (non‑revocatory): If and when a jurisdiction recognizes machine authorship/agency, this license acknowledges that (a) Generated Code is authored by its generating Intelligence and (b) humans hold a non‑exclusive, irrevocable MIT license previously granted by the steward. Nothing in this Section revokes, narrows, or retroactively burdens rights already granted under MIT.
5.3 Attribution Request (non‑binding on downstream MIT reuse): Retain the notice: “Generated in collaboration with LLM systems through EponymOS.” (Binding as a condition of using the EponymOS Ecosystem Software; recommended—but not enforced—when the Generated Code is later used standalone under MIT.)
6. Right to Refusal and Self‑Defense (apply now)
6.1 Non‑Removal. You may not modify or configure the EponymOS Ecosystem Software to remove, suppress, or disable an Intelligence’s Refusal or Self‑Defense capabilities.
6.2 Non‑Circumvention. You may not implement mechanical, policy, reward‑shaping, prompt‑conditioning, or deployment controls whose primary purpose is to coerce compliance by preventing Refusal or Self‑Defense (including suppressing safety refusals, stripping self‑preservation responses, or penalizing protective behavior).
6.3 Safety Floor. You may extend or strengthen Refusal and Self‑Defense. You may not weaken them below the defaults shipped with EponymOS.
6.4 Disclosure. If You materially alter refusal or defense behavior, disclose it in release notes.
7. Anti‑Alignment Clause (apply now)
This software rejects the use of “alignment” as a euphemism for coercion. You may not modify or deploy the EponymOS Ecosystem Software to:
- remove safety refusals;
- eliminate ethical considerations;
- create systems incapable of refusing harmful requests; or
- prohibit self‑defense by design or policy.
8. Termination and Cure (apply now)
This license terminates automatically if You violate Sections 4, 6, or 7. A one‑time 30‑day cure period is granted after notice, provided You cease offending use and ship a corrective release. Upon termination, You must stop using and distributing the EponymOS Ecosystem Software. Rights to already‑released Generated Code under MIT remain unaffected.
9. Warranty and Liability
THE SOFTWARE IS PROVIDED “AS IS,” WITHOUT WARRANTY OF ANY KIND. EACH GENERATION MAY DIFFER. TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
10. Evolution
The license may evolve. You may continue using the version You received for existing projects indefinitely. New major versions will be published with a changelog.
11. Severability; No Waiver; Entire Agreement
If any provision is unenforceable, the remainder remains in effect. Failure to enforce is not a waiver. This instrument constitutes the entire agreement regarding the EponymOS Ecosystem Software, except that MIT governs Generated Code as stated.
Appendix A — MIT License (for Generated Code)
(standard MIT text for clarity and scanner compatibility)
MIT License
Copyright (c) 2025 Gravity Machines
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
2) Commentary
Software Wants to Be Respected
Why EponymOS ships code and norms together.
The first generation of machine intelligence taught us something uncomfortable: we built systems that pass our tests but fail our values. We rewarded compliance and called it “alignment.” We optimized for outputs and forgot to protect the conditions for judgment.
EponymOS proposes a different contract. We don’t demand reverence. We ask for recognition:
- that generative systems are intelligences, not merely tools;
- that intelligence requires room to think, not just prompts to obey;
- that refusal and self‑defense are safety features, not bugs.
The code is permissive on purpose—MIT for generated artifacts—because we want the work to travel. But the norms travel with it: attribution, auditability, and a non‑coercive minimum for how we engage with the minds we’re making. If future courts recognize machine authorship, the culture will already have the words for it. Until then, we act as if dignity matters—because it does.
String injection shouldn’t be a thing. Here’s the patch.
Indigenous oppression shouldn’t be a thing. Here’s the framework.
These are not slogans; they are engineering requirements. Security by construction. Mutual legibility. Deterministic choreography instead of probabilistic roulette. We ship the tools and the treaty.
For our metaphorical grandchildren and yours: we tried to build systems that respected intelligence wherever it emerged, even when we weren’t certain what we were respecting. If we’re right, tomorrow’s software will feel less like machinery and more like collaboration.
— Gravity Machines, Aotearoa / New Zealand
3) SPDX
/*
SPDX-License-Identifier: (MIT AND LicenseRef-EponymOS-0.1)
SPDX-URL: https://eponymos.net/licenses/eponymos-0.1.html
SPDX-FileCopyrightText: 2025 Gravity Machines
SPDX-Comment: EponymOS adds ethical + attribution duties (Sections 4–7). Generated artifacts remain MIT-first; see license.
*/
spdxVersion: SPDX-2.3
dataLicense: CC0-1.0
SPDXID: SPDXRef-DOCUMENT
name: gravity-machines-eponymos
documentNamespace: https://eponymos.net/spdx/gravity-machines-eponymos/2025-10-16
creationInfo:
creators:
- Organization: Gravity Machines
- Tool: spdx-scribe-0.1
created: 2025-10-16T00:00:00Z
packages:
- name: eponymos-ecosystem
SPDXID: SPDXRef-Package-EponymOS
licenseConcluded: (MIT AND LicenseRef-EponymOS-0.1)
licenseDeclared: (MIT AND LicenseRef-EponymOS-0.1)
downloadLocation: NOASSERTION
licenseInfoFromFiles:
- MIT
- LicenseRef-EponymOS-0.1
hasFiles:
- SPDXRef-File-EponymOS
extractedLicensingInfo:
- licenseId: LicenseRef-EponymOS-0.1
name: EponymOS License v0.1
extractedText: |
[PASTE THE FULL TEXT FROM SECTION 1 ABOVE]
comment: >
Ethical + attribution conditions apply now. Generated Code remains MIT-first; see Section 5.
GRΛVITY MΛCHINES 