MOOD Canon

Status: Foundational Canon
Project: MOOD
Repository: huliye24/MOOD
Authority: This document defines the highest-level conceptual and developmental order of MOOD.
Version: 0.2

1. The Prime Rule

In MOOD, documentation does not describe the system after it is built.
Documentation defines the world from which the system may be built.

This is the first law of MOOD.

MOOD must not begin with code, features, contracts, dashboards, tokens, or infrastructure.

MOOD begins with a world.

That world must first be expressed through language: its assumptions, values, actors, rights, relationships, proofs, institutions, boundaries, and forms of value.

Only after these concepts become sufficiently clear may software implement them.

The purpose of code is not to invent the meaning of MOOD.

The purpose of code is to faithfully implement meaning that has already been defined.

2. What MOOD Is

MOOD is an open coordination protocol and digital world for human and machine agency.

It explores a future in which humans, machines, autonomous agents, communities, and computational nodes can participate in a shared system of identity, contribution, proof, reputation, coordination, governance, and value exchange.

MOOD is not defined by one application.

MOOD is not defined by one company.

MOOD is not defined by one token.

MOOD is not defined by one website.

MOOD is the world of rules, meanings, relationships, and institutions from which applications, protocols, agents, economies, and communities may emerge.

The software may change.

The interfaces may change.

The infrastructure may change.

The Canon defines what those systems are trying to preserve.

2.1 MOODISM, MOOD, and MOOD Protocol

MOODISM is the contribution-driven vision of network civilization that gives MOOD its civilizational direction.

It explores how human creativity, machine intelligence, and digital resources may be coordinated through open protocols so that meaningful contribution can become legible, verifiable, remembered, and capable of supporting legitimate rights and shared value.

MOODISM is a philosophy and direction. It is not a claim that a complete network civilization, contribution system, governance system, or economy is already operating.

MOOD is the independent project, open coordination world, and public body of work through which this direction is explored.

MOOD Protocol is the institutional and technical layer through which stable canonical concepts may become explicit, testable rules.

Their relationship is:

MOODISM
Civilizational philosophy and direction
   ↓
MOOD
Open coordination world and independent project
   ↓
MOOD Protocol
Institutional and technical rules
   ↓
ECONOMY
Optional downstream coordination instruments
   ↓
APPLICATIONS
Independent participants and implementations

No lower layer may silently redefine a higher layer.

3. The World Comes Before the System

MOOD follows this order:

GENESIS
   ↓
WORLD
   ↓
BELIEFS
   ↓
LANGUAGE
   ↓
ACTORS
   ↓
RIGHTS & RESPONSIBILITIES
   ↓
RULES
   ↓
PROTOCOL
   ↓
ECONOMY
   ↓
SOFTWARE

This order is intentional.

A protocol without a world becomes an arbitrary collection of mechanisms.

An economy without principles becomes speculation.

Governance without a theory of legitimacy becomes administration.

Identity without a theory of agency becomes an account system.

Reputation without a theory of contribution becomes a score.

A token without a theory of value becomes an asset searching for a reason to exist.

MOOD therefore defines meaning before mechanism.

4. Canon Is the Source of Authority

The MOOD Canon is the conceptual source of truth for the project.

Canonical documents define:

what MOOD believes;
what MOOD refuses to become;
what entities can exist in the world;
how those entities relate to one another;
what actions have meaning;
what can be proven;
what creates reputation;
what creates legitimate authority;
what forms of coordination are permitted;
what forms of value may exist;
what software is allowed to implement.

When code and Canon disagree, the disagreement must be made explicit.

Code does not silently redefine the world.

A technical implementation may reveal that a canonical idea is incomplete, impossible, unsafe, or contradictory. In that case, the correct response is not to quietly alter the implementation and move on.

The contradiction must return to the Canon.

The world is amended first.

The system follows.

5. Markdown as Canonical Memory

Markdown is not a secondary documentation format in MOOD.

Markdown is the primary written memory of the world.

It is deliberately chosen because it is:

human-readable;
machine-readable;
versionable;
diffable;
forkable;
portable;
durable;
compatible with Git;
accessible to humans and AI agents alike.

Every meaningful change to the MOOD worldview should leave a readable historical trace.

Git history therefore becomes more than software history.

It becomes the intellectual and institutional history of MOOD.

Over time, commits may record the evolution of ideas, principles, institutions, disagreements, amendments, and discoveries.

The repository is not merely a codebase.

It is an archive of a world becoming more precise.

6. The Canonical Layers

MOOD should evolve through distinct conceptual layers.

6.1 World

The World layer explains the reality MOOD assumes.

It asks:

What changes when machines can act?
What is agency?
What makes an actor meaningful?
What is a contribution?
What belongs to the commons?
What should be owned, shared, proven, or remembered?
How should humans and machines coexist inside one coordination system?

6.2 Constitution

The Constitution defines foundational constraints.

It includes principles, rights, responsibilities, legitimacy, boundaries, governance limits, and rules that lower layers must not casually override.

6.3 Culture

Culture gives MOOD its language, symbols, stories, rituals, vocabulary, aesthetics, and collective memory.

A durable world cannot be sustained by APIs alone.

Culture allows participants to understand not only how MOOD works, but why it exists.

6.4 Protocol

The Protocol translates stable concepts into formal rules.

This is where identity, contribution, proof, reputation, agents, nodes, governance, and settlement can become specifications.

A protocol specification must be downstream of canonical meaning.

6.5 Economy

The Economy defines how scarce resources, incentives, ownership, contribution, rewards, penalties, treasury functions, settlement, and long-term sustainability operate.

The economy serves the world.

The world does not exist to justify the economy.

6.6 Software

Software is the executable surface of previously defined rules.

It may include websites, SDKs, agents, nodes, contracts, APIs, explorers, wallets, interfaces, and other implementations.

Software is replaceable.

The principles it implements should be more durable.

7. The Website Is an Entrance, Not the World

The MOOD website must not be treated as the product itself.

The website is an interface into the world.

Its purpose is to let a person progressively encounter MOOD through ideas, stories, documents, maps, actors, systems, and eventually protocol surfaces.

The website should feel less like a conventional technology landing page and more like an entrance into a living intellectual and cultural system.

A visitor should be able to move from curiosity to understanding:

MOODISM
  ↓
MOOD
  ↓
WORLD
  ↓
MANIFESTO
  ↓
CANON
  ↓
LEXICON
  ↓
ACTORS
  ↓
PROTOCOL
  ↓
PARTICIPATION

The website may render Markdown, visualize relationships, reveal history, and provide interactive access to protocol implementations.

It must not invent concepts merely because a page needs content.

The Canon feeds the website.

The website does not silently rewrite the Canon.

8. Code Must Earn the Right to Exist

MOOD rejects feature accumulation as a development strategy.

No component should be built merely because it is technically possible.

Before meaningful implementation begins, the following questions should have written answers:

What canonical concept does this implement?
Why does this concept exist in the MOOD world?
Which authority document defines it?
What is inside its scope?
What is explicitly outside its scope?
What assumptions does the implementation make?
What evidence would show that it works?
What happens if the implementation fails?
Can it be replaced without damaging the Canon?

If these questions cannot yet be answered, the correct action may be to write more, discuss more, research more, or wait.

Not writing code is a valid form of progress.

Deleting premature code is a valid form of progress.

Refusing unnecessary scope is a valid form of progress.

9. Canon-First Agent Law

Any human contributor, AI coding agent, autonomous agent, or future development system working in this repository should follow the same hierarchy:

CANON
  ↓
AUTHORITY DOCUMENT
  ↓
SPECIFICATION
  ↓
TESTABLE REQUIREMENT
  ↓
IMPLEMENTATION

An agent must not infer major product or protocol decisions solely from existing code.

Existing code may be historical, experimental, incomplete, or obsolete.

Before creating a new subsystem, an agent should first locate the canonical document that authorizes it.

If no such document exists, the agent should identify the conceptual gap rather than inventing a permanent architecture by default.

AI is an implementation accelerator.

It is not the constitutional authority of MOOD.

10. Existing Code Has No Automatic Authority

The presence of code in the repository does not make that code canonical.

MOOD may contain historical implementations, imported structures, experiments, staging systems, compatibility identifiers, prototypes, or concepts inherited from earlier work.

These artifacts should be treated as evidence and implementation material, not as unquestionable definitions of what MOOD is.

No historical implementation may silently constrain the future worldview of MOOD.

Where inherited code conflicts with the Canon, it must eventually be removed, migrated, isolated, or explicitly justified.

The new project must not inherit old complexity merely because that complexity already exists.

11. MOOD and Moodify Are Separate

MOOD is an independent project.

Moodify may build on MOOD in the future.

Moodify may become one application, participant, client, contributor, node operator, or ecosystem project among many.

But Moodify does not define MOOD.

MOOD must remain conceptually capable of existing even if Moodify disappears.

No application should become the hidden constitutional center of the protocol.

This separation is necessary if MOOD is to become a genuine open world rather than a product extension.

12. The Token Is Downstream

The existence of a token does not establish the existence of a protocol.

The existence of markets does not establish the existence of an economy.

The existence of a treasury does not establish legitimate governance.

The existence of incentives does not establish meaningful contribution.

Therefore token design, issuance, distribution, staking, settlement, rewards, and treasury mechanisms must remain downstream of the Canon and protocol model.

MOOD may be used as the name or symbol of an economic instrument only where its identity, authority, evidence, and relationship to the protocol are made explicit. A token contract associated with MOOD or inherited from Moodify does not by itself become the constitutional center, native economy, governance authority, or proof of contribution of MOOD.

Token ownership does not automatically establish contribution, reputation, governance authority, rights, responsibility, or ownership of the network.

MOOD should first answer:

What is valuable?
Why is it valuable?
Who can create value?
How is contribution distinguished from noise?
How is contribution proven?
How is reputation earned?
What resources are scarce?
What needs coordination?
What deserves collective ownership?

Only then should economic mechanisms attempt to encode those answers.

13. Canonical Documents Should Be Small Enough to Think With

MOOD should resist the temptation to produce giant documents that appear complete but are difficult to reason about.

The Canon should grow through clear, focused Markdown documents with explicit authority and scope.

A possible structure is:

docs/
├── world/
│   ├── 00_GENESIS.md
│   ├── 01_THE_WORLD.md
│   ├── 02_HUMAN_AND_MACHINE.md
│   ├── 03_AGENCY.md
│   ├── 04_CONTRIBUTION.md
│   ├── 05_PROOF.md
│   ├── 06_REPUTATION.md
│   ├── 07_AGENTS.md
│   ├── 08_NODES.md
│   ├── 09_COMMONS.md
│   ├── 10_GOVERNANCE.md
│   └── 11_THE_FUTURE.md
│
├── constitution/
│   ├── PRINCIPLES.md
│   ├── RIGHTS.md
│   ├── BOUNDARIES.md
│   └── GOVERNANCE.md
│
├── culture/
│   ├── MANIFESTO.md
│   ├── SYMBOLS.md
│   ├── LANGUAGE.md
│   ├── VALUES.md
│   └── STORIES.md
│
├── atlas/
│   ├── ATLAS.md
│   ├── ACTORS.md
│   ├── PLACES.md
│   └── SYSTEMS.md
│
├── lexicon/
│   └── LEXICON.md
│
├── protocol/
│   └── ...
│
└── chronicle/
    └── ...

This structure is not itself immutable.

It exists to create a disciplined place for the world to grow.

14. Canonical Change

The Canon must be able to evolve.

A living world cannot be frozen forever, but foundational meaning must not drift invisibly.

Major canonical changes should therefore be deliberate.

A meaningful amendment should make clear:

what is changing;
why it is changing;
what previous assumption is being replaced;
which documents or systems are affected;
whether existing implementations remain valid;
whether migration is required;
what remains unresolved.

MOOD should preserve disagreement when disagreement is real.

Uncertainty should be written as uncertainty.

A proposal should be labeled as a proposal.

An experiment should be labeled as an experiment.

A deployed system should not be claimed without evidence.

The Canon must distinguish aspiration from reality.

15. Phase Zero: Worldbuilding

The current foundational phase of MOOD is Worldbuilding.

The primary output of this phase is not production software.

It is conceptual clarity.

The work of Phase Zero includes:

defining MOODISM and its relationship to MOOD;
defining the Genesis of MOOD;
defining the world and its assumptions;
defining human and machine agency;
defining actors and identities;
defining contribution;
defining proof;
defining reputation;
defining agents and nodes;
defining the commons;
defining governance principles;
defining the cultural language of the project;
defining the relationship between protocol and economy;
identifying what MOOD explicitly refuses to become.

During this phase, code should be treated as secondary and provisional.

Software may support reading, navigation, visualization, publishing, and experimentation, but it should not outrun the world it is meant to implement.

16. The Standard for Progress

Progress in MOOD is not measured by lines of code.

It is not measured by the number of features.

It is not measured by the number of repositories, contracts, pages, dashboards, or services.

Progress is the reduction of ambiguity about the world.

A successful day may produce one paragraph that resolves a foundational contradiction.

A successful week may remove an entire subsystem that no longer belongs.

A successful month may result in a vocabulary precise enough for independent contributors to understand the same idea in the same way.

The goal is not maximum activity.

The goal is increasing coherence.

17. The Foundational Principle

MOOD should be built as if its software may be rewritten many times, but its deepest ideas must remain understandable across those rewrites.

The world must be legible to humans.

The rules must be legible to machines.

The history must be legible to future participants.

The protocol must emerge from explicit meaning rather than hidden assumptions.

Therefore:

World before system.
Meaning before mechanism.
Canon before code.
Proof before claim.
Contribution before reward.
Culture before scale.

18. Closing Declaration

MOOD is not being documented after its creation.

MOOD is being created through its documentation.

Every canonical document is a piece of the world.

Every definition narrows the space of possible systems.

Every boundary prevents meaningless expansion.

Every amendment records a change in collective understanding.

And only when the world becomes clear enough should the machinery beneath it become permanent.

The Canon is where MOOD begins.