The Cyrus License: CyLi#

Warning

This license does not exist yet. This page states the principle CyLi is meant to protect and the questions still open. It deliberately contains no license terms — the drafting work is genuinely not done, and text that merely sounded like a license would claim an authority nobody has granted.

Nothing on this page may be relied on as a license. The license currently governing content on this site is the Jonah License.

The core principle#

What has been published cannot be revoked, but newer versions can be published.

That single sentence is the whole idea. Everything else is machinery for making it institutionally reliable.

Why this needs a license at all#

StayVS already does this technically: every published version (OOv1, PPv2, and so on) is a permanent record, superseded by later versions rather than overwritten by them.

But a technical convention is only as durable as the person maintaining it. An institution deciding whether to build on this material has to ask a harder question: what stops the author from quietly rewriting version 1 next year? Today the honest answer is “goodwill and a git history.” That is not enough to plan around.

CyLi is intended to close that gap — to make the StayVS guarantee something a third party can rely on rather than something they have to trust.

What CyLi is intended to guarantee#

For material published on this site under StayVS versioning:

  1. Published contributions remain accessible and attributable.

  2. No one — including the original author — can retroactively alter what was published under a given version number.

  3. Improvements are always possible through new versions, with the versioning history itself being a public record.

Point 2 is the one that costs something. It binds the author, not just everyone else. A license that only constrains readers would not solve the problem CyLi exists to solve.

Scope#

Site content under StayVS versioning only. (Confirmed by LLoL 2026m08d03.)

CyLi is aimed at material published on Balospe.com that carries a StayVS version marker. It is not currently scoped to:

  • third-party or institutional contributions (those are covered by the Jonah License, as is all FeedbackFlow input);

  • reuse as a general-purpose license by other projects.

Both of those are plausible later extensions. Neither is claimed now. Keeping the first version narrow is deliberate: a narrow license that actually works is worth more than a broad one that has never been tested against a real dispute.

How CyLi relates to the Jonah License#

They are different layers, not competitors, and they answer different questions:

JoLi

CyLi (planned)

Question it answers

May I use and share this?

Can I trust that this version will still say the same thing later?

Direction it binds

Frees the reader

Binds the author

Status

In force (JoLi MMv1_2024m10d18)

Not drafted

Applies to

All site content and all FeedbackFlow submissions

Site content carrying a StayVS version marker

JoLi removes barriers to sharing. CyLi is meant to remove doubt about stability. A reader can need both answers at once, which is why CyLi is planned as a complement rather than a successor.

Why “Cyrus”?#

The name honors Cyrus the Great, who issued the first known declaration of human rights and enabled the return of exiled peoples to rebuild their heritage. CyLi aims to similarly protect the integrity of intellectual contributions while enabling continuous renewal.

Note

Until 2026m08d03 this license was written as the “Cycrus License” across this site — a typo, corrected everywhere on that date. The abbreviation CyLi was always correct and is unchanged.

Open questions#

Recorded so the gaps are visible rather than glossed over. These are genuine uncertainties, not rhetorical ones:

  1. What enforces it? A license is a legal instrument, but the guarantee CyLi wants is closer to an archival commitment. Is the right mechanism a license, a public commitment, a third-party archive deposit, or some combination?

  2. What happens on error? If a published version contains a factual error or a harmful mistake, “cannot be revoked” collides with “should be corrected.” StayVS answers this with supersession plus a visible correction notice. Does CyLi need to say more?

  3. What happens if the site disappears? An immutability promise that depends on one domain staying paid for is weak. Does CyLi require a mirror or deposit obligation?

  4. Does it bind successors? If the material changes hands, does the guarantee travel with it?

  5. How does it interact with CC0? JoLi is CC0-based, and CC0 waives essentially everything. Can a CC0-licensed work carry an additional author-binding stability commitment without contradiction?

If you have experience with any of these — especially question 5 — the FeedbackFlow link at the bottom of this page is the fastest way to say so.

Status#

Informal draft (CyLi MMv0r1_2026m03d31). The formal specification will be developed as part of the broader StayVS and POST System infrastructure. This page is offered not to be believed, but to be checked.

Notes

Content stability — Content is variant dv_ClaOp50Max_MMv0r1p0_2026m08d03 (see StayVS). Rebuilt 2026-09-17.

See also on Balospe.com
Epic Fury to Epic Empathy: Fund a ResearchCity for Mathematical Theology

For millennia, Jews, Christians, Muslims, and others have fought wars — and fueled apocalyptic fears — over theological questions that none of them could state precisely enough to resolve. Mathematical theology offers a way out: translate the claims into formal axioms, check them for consistency, and discover where traditions actually agree once ambiguity is removed.

First explorations reveal a striking result: all three Abrahamic scriptures converge on the same pan-en-theistic structure when mapped to formal axioms. If that convergence holds under rigorous scrutiny, it can defuse centuries of eschatological conflict by showing that many disagreements are verbal, not logical.

But this work requires global support to avoid capture by special interests. Refining axioms, engaging scholars across traditions, and running formal consistency checks all require sustained effort — as does real-world testing of what matheology discovers.

If you believe replacing eschatological warfare with mathematical clarity is worth pursuing before it’s too late, please fund this work — every contribution helps evolve a global ResearchCity for finding the narrow path to peace.

FF FeedbackFlow to improve this page: How you can contribute

For the full guide on providing feedback — including how it is handled, licensing, and what to expect — see How to use FeedbackFlow.

Please check if See also on Balospe.com above already addresses your idea. Feedback works best when it targets the most specific page. If none of those pages help, you may have a good case for sending FF here.

To submit your FeedbackFlow:

  1. Click anywhere on the email preview below to open a pre-filled email.

  2. Replace the placeholder text with your feedback.

  3. Send.

To: [email protected] CC: [email protected] Subject: FF k2 s2 AIMS for [license-cyli] Replace_by_OneLineSummary Body: To make this page [license-cyli] more gentle kind reasonable for beginners, producers, andOr experts with a background in xyz: Please consider improving this: -- By sending this email, I agree that its content may be published under the Jonah License (balospe.com/en/license/joli/) unless I state otherwise above. MailForm=OOv2r0p0

The email subject contains k2 and s2 — default codes for impact and urgency. Most contributors can leave these unchanged. To adjust each as independently as they are:

  • Importance of impact: above average k3, average default k2, below average k1.

  • Urgency of speedup: above average s3, average default s2, below average s1.

This allows plotting importance over urgency to help triage FF. For more details see FF System Design.

On this page
Recent Posts
Tags