Mova0.5 pre-release⌕
☰
home / docs / licence / Not a Big Brother

Not a Big Brother

Appendix to the Elamur Cosmic License and the Elamur API Terms
Working policy text — English draft
Version: 2026-10-15 (re-scoped from Mova Extended, which is postponed)

Purpose

The Elamur API is not intended to become a toolkit for population control.

Scope (2026-10-15). The code is open, but not for Big Brother. Free Elamur repositories (mova-free and others) move to the Elamur Cosmic License (ELAMUR-COSMIC-LICENSE.md): the most open license we can write — anything, for anyone, no attribution, no fees — with only the restrictions of this appendix built in and passed on to every copy. The hosted API and tokens carry the same restrictions in Elamur API and Token Terms — working draft. Mova Extended is postponed; Elamur sells nothing but API access and tokens.

This appendix explains the policy logic behind restrictions on certain government, security, intelligence, and state-controlled uses of the Elamur API.

It is explanatory policy text. The operative legal terms should remain in the license and its formal annexes.

The core principle is simple:

Powerful language, search, analytical, and automation systems should not be used to turn entire populations into targets of political control.

What this appendix is not

This document is not:

The concern is institutional conduct and prohibited use, not citizenship.

A student, researcher, journalist, dissident, developer, civil-society organization, or ordinary user should not be prohibited merely because they live in or come from a restricted jurisdiction.

The distinction between capability and abuse

Many states possess powerful surveillance capabilities.

That fact alone is not enough to place a country in the restricted-jurisdiction annex.

The relevant questions are:

The difference is therefore not simply technical capacity.

It is the relationship between surveillance power, political coercion, accountability, and human rights.

Repressive Big Brother

The working highest-risk classification is:

These jurisdictions are treated as especially sensitive because the working policy analysis identifies a combination of:

Vietnam is currently treated as a closely related but separate category:

This classification may change as the evidence base is reviewed.

High-capacity surveillance states

Some democratic states also possess exceptionally powerful intelligence and surveillance systems.

The United States and United Kingdom are examples of:

They are not placed in Annex A merely because they possess strong surveillance capabilities.

Their inclusion in this separate category serves an important purpose: the project should not pretend that surveillance power exists only in authoritarian systems.

The policy distinction is based on factors such as:

These safeguards are not perfect, and their existence does not make all surveillance legitimate.

They do, however, materially distinguish surveillance capacity from a system designed primarily for political repression or population control.

Restricted jurisdictions

The current working restricted-jurisdiction list is maintained separately in:

The evidence supporting each designation should be maintained separately in:

The restricted list is intentionally narrower than generic lists of authoritarian or "Not Free" states.

A jurisdiction should normally enter Annex A only where there is a serious combination of factors such as:

Prohibited institutional users

The final license should distinguish between nationality and institutional role.

Restricted categories should focus on actors such as:

Prohibited uses

The final legal language should define prohibited conduct as precisely as possible.

Working concepts include:

These labels are placeholders for formal legal drafting.

They should not remain vague moral slogans if they can be converted into concrete definitions.

Allowed users from restricted jurisdictions

Restrictions must not become collective punishment.

Examples of users who should remain eligible, subject to the normal license terms:

Examples:

By contrast:

Evidence and review

Restrictions should be evidence-based and versioned.

No jurisdiction should be treated as permanently restricted merely because it once qualified.

A country may be removed if conditions materially improve.

Relevant changes can include:

Likewise, a jurisdiction outside Annex A may be added if conditions deteriorate.

Every evidence entry should eventually include:

Current policy files

Recommended structure:

Review notes currently recorded

The current working policy includes these review decisions:

Uzbekistan and Bahrain remain in Annex A but should be reviewed annually.

Enforcement

The project does not plan to rely on litigation. A party that violates these restrictions loses its API keys and is added to an internal blacklist: no new keys, tokens, contracts, services, data access or custom work. No court finding or formal proof is required for the project to decline to do business with someone.

The cultural framing of this policy ("the family settles its own affairs, as in old Chicago") lives in Mythology and is satirical, never operative.

Final principle

The purpose of these restrictions is not to decide which countries are morally pure.

The purpose is to draw a practical boundary around dangerous uses of powerful software.

The Elamur API should not help a state:

The project should remain open to people.

It should not become infrastructure for a Big Brother.

This page in Markdown → https://md.mova.elamur.ai/free/en/docs/licence/Not-a-Big-Brother/