DocumentLITEPAPER-001 Statusv0.1 / Genesis Issued byOM Editors MVPapp.omworld.one · live
Genesis Protocol Gateway · v0.1 · MVP live 2026-05-18

One Mind,
One World.

A self-growing intent realization network. Every realization makes the next one easier.

OM World connects what people want with the capabilities that can deliver it, and turns every realization into a reusable pattern in a shared Pattern Library — so over time the system grows more capable on its own.

DemandTell OM World what you want realized.
SupplyRegister tools, agents, services that can deliver.
MemoryEvery realization becomes a reusable pattern.
§ 01 — What is OM World?

A self-growing
intent realization network.

OM World is a self-growing intent realization network.

It connects three sides: people who declare intentions; tools, agents, and human services that can deliver them; and a Pattern Library that remembers every successful realization. Each time an intent is realized, the path is saved as a reusable pattern — so the next intent of the same kind is faster, cheaper, and requires less manual thinking. The system grows more capable on its own, and the people who created the underlying patterns are credited each time their work is reused.

The single test every part of the system must pass: does it make future intent realization easier?

OM World 是一个自增长的意图实现网络。它连接意图需求与实现能力,把每一次成功的实现沉淀为可复用模式,让未来同类意图越来越容易实现。成熟形态下,它也是一个去中心化意图经济协议——但 "自增长" 才是核心机制。

01 · DECLARE
Declare.

Users submit real intentions through Submit an Intent. The system classifies what kind of intent it is.

02 · MATCH & EXECUTE
Match & Execute.

A matching engine proposes realization paths from registered tools, agents, and human services. The chosen path runs and records its trace.

03 · REMEMBER
Remember.

Each realization becomes a reusable Pattern. The second intent of the same kind is faster, cheaper, and easier than the first.

§ 01.5 — MVP is live

Open the network
at app.omworld.one.

The Genesis MVP shipped on 2026-05-18. It implements five modules — the minimum needed to test the self-growth thesis:

  1. Intent Demand Entry — Submit an Intent (form + LLM classification)
  2. Capability Supply Entry — Contribute a Capability (Tool / Agent / Human Service)
  3. Matching Engine — LLM-routed, half-automatic path proposals
  4. Pattern Library v0 — every realization becomes a reusable pattern
  5. OM Credit Ledger v0 — internal accounting unit (no token, no on-chain representation)

The first seeded capability is the Genesis Builder Recruitment Generator. Try it: submit "I want to recruit 5 Genesis co-builders for my project" and you'll receive a complete campaign package (positioning, X article, X thread, DM templates, GitHub issue plan, target builder profiles, follow-up plan). The second realization of the same intent type is measurably faster than the first — that's the self-growth loop, validated.

§ 02 — Why intent must be decentralized

The next internet
will route intent.

The previous internet auctioned attention. The next internet will route intent.

If the intent layer is captured by centralized AI platforms, human intention becomes platform inventory, agent decisions become black-box recommendations, and execution paths become hidden auctions.

— Until now

The Attention Economy

  • clicks
  • views
  • likes
  • impressions
  • ads
  • engagement metrics
  • closed recommendations
— Beginning now

The Intent Economy

  • intents
  • mandates
  • agents
  • tools
  • execution proofs
  • settlement events
  • reputation history
  • open protocol routing
Human intention should not be owned by platforms, auctioned by advertisers, or executed by black boxes.
— THE OM COUNCIL · GENESIS DRAFT
§ 03 — Three principles

Three principles.
One protocol.

Three commitments to users, agents, and the world they act in. None novel alone — together, a contract.

Principle I · 01 / 03

AI is the engine.

AI provides reasoning, planning, generation, coordination, and execution capacity. It is power, not purpose.

Principle II · 02 / 03

Crypto is the law.

Signatures, hashes, attestations, smart contracts, and settlement rules make execution verifiable.

Principle III · 03 / 03

Humanity owns its intentions.

The originator of an intent remains its sovereign owner. Agents act under mandate, not ownership.

§ 04 — Intent Lifecycle

From intention
to verifiable outcome.

Declare. Bind. Route. Execute. Prove. Settle. Remember. Seven stations — each consuming and producing structured evidence.

01 · DECLARE

Declare.

A user expresses an intention.

02 · BIND

Bind.

The intention becomes a signed mandate.

03 · ROUTE

Route.

Agents select tools, compute, and execution paths.

04 · EXECUTE

Execute.

Tools and agents perform the required actions.

05 · PROVE

Prove.

Results are verified through proofs, logs, hashes, or attestations.

06 · SETTLE

Settle.

Payments, rewards, refunds, and reputation are finalized.

07 · REMEMBER

Remember.

The intent becomes part of the originator's owned history.

§ 05 — Protocol Architecture

12 systems.
5 in the MVP.

OM World is best understood as three nested layers: the 12 core systems of the mature world, the 8 module groups they cluster into as the ecosystem grows, and the 5 modules actually shipped today. The MVP is not a v0 of the full system — it is a deliberate, minimal subset chosen so the self-growth loop can be validated before larger commitments are made.

S1

Intent Demand Portal

Where users declare what they want
natural languagemulti-turn refinementdefault authorizationsintent history
S2

Capability Supply Portal

Where supply-side registers what it can do
toolagentAPIhuman servicecomputestoragedatapattern
SUP
S3

Intent Router

Classifies + selects realization path
classificationpattern retrievalcost/time estimatemulti-path comparison
RTR
S4

Pattern Library

The memory · the compounding asset
pattern recordsreuse countsuccess ratecreator creditversioning
S5

Distributed Storage Network

Where patterns + traces + proofs live
user-contributed storageshardingcommitmentsoff-chain bulk
STO
S6

Distributed Compute Network

Tiered compute supply
light nodeslocal executioncompute nodesexpert nodes
CPU
S7

Execution Runtime

Invokes capabilities · composes flows
LLM callstool invocationmulti-agenttrace capture
RTM
S8

Proof & Trace Layer

Confirms what happened, by whom
tracesartifact hashesattestationsdispute evidence
S9

Settlement System

OM Credit (OMC) · no token
OMC ledgerevent recordsno on-chain tokenno financial promise
SET
S10

Value Distribution Engine

Splits proceeds by event-time records
capability rewardspattern creator creditnode payoutscore maintenance
DST
S11

Node Client

Turn a device into a participant
storagecomputelocal toolsbrowser executionOMC earned
NOD
S12

OM World Index / Explorer

Read-only world-state surface
intent flowpattern reuse mapcapability graphgrowth dashboard
IDX
S1 + S4 — the demand and memory anchors
S8 — proof & trace
S1, S2, S3, S4, S9 are live in the MVP today at app.omworld.one
§ 06 — Ecosystem Roles

A world is built
by many roles.

OM World is not a company. It is a constellation of roles — eight seats around a shared protocol, each indispensable, none dominant.

01 · ORIGIN

Intent Originators

Declare intentions and define mandates.

02 · BUILD

AI Agent Builders

Build agents that plan, route, and execute workflows.

03 · CREATE

Tool Creators

Create capabilities that fulfill intents.

04 · POWER

Compute Providers

Supply inference and execution resources.

05 · PROVE

Verifiers

Attest that outcomes match declared requirements.

06 · FUND

Capital Providers

Fund intents that require upfront resources.

07 · SURFACE

Interface Builders

Build wallets, explorers, dashboards, and marketplaces.

08 · STEWARD

Governance Participants

Steward standards, grants, disputes, and upgrades.

§ 07 — Genesis Documents

Genesis documents
are public.

OM World begins in public. The first documents are open for review, critique, translation, and contribution.

DOC · 01STABLE

Manifesto

The first principles. Why intent must be decentralized.

Read Manifesto
DOC · 02v0.1 · GENESIS

Litepaper

Architecture, lifecycle, economics, governance — 33 pages.

Read Litepaper Download PDF
DOC · 03DRAFT

Governance

From Genesis to DAO — a five-stage ladder.

View Governance
DOC · 04v0.1

Roadmap

Five phases. Each with deliverables and exit criteria.

View Roadmap
DOC · 05v1.0

Brand System

Visual language: Origin Point, Proof Ring, Agent Path.

View Brand
DOC · 06v0.1 · CANON

Self-Growth Engine

The canonical MVP architecture. Pattern Library, settlement templates, the self-growth loop.

Read Self-Growth Engine
DOC · 07LIVE

Genesis MVP

The protocol running today. Submit an Intent, register a Capability, browse the Pattern Library, watch the OMC ledger move.

Open the MVP
DOC · 08LIVE

GitHub Issues

Open specifications. Open questions. Open contributions.

View GitHub
§ 08 — Open Questions

Open questions
for builders.

OM World is early. These questions are not weaknesses — they are invitations.

Q.01

How should intents be structured without limiting human expression?

Q.02

Which parts of execution should be on‑chain, off‑chain, private, or public?

Q.03

How should subjective outcomes be verified?

Q.04

How can agent decisions be explainable without exposing sensitive data?

Q.05

How should tool creators be rewarded and bad tools penalized?

Q.06

How can governance avoid capture?

Open an Issue View Open Questions
§ 09 — Join the Genesis

Join the
Genesis.

OM World is looking for builders, researchers, designers, writers, protocol engineers, AI agent developers, smart contract developers, verifiers, and community contributors.

A world is not built by one founder. A protocol is not made real by one document.

▸ Active protocol tracks

Each track has an open issue. Pick one and critique. No commitment beyond a single contribution.

PRIMITIVE · 01

Intent Schema

PRIMITIVE · 02

Agent Mandate

PRIMITIVE · 03

Execution Proof

PRIMITIVE · 04

Tool Registry

SPRINT · 001

Genesis Review

Contribution tracks · by skill
DO · 01

Submit a real intent

DO · 02

Register a capability

DO · 03

Browse the Pattern Library

TRACK · 04

Become a Genesis Co-builder

TRACK · 05

Read Self-Growth Engine

TRACK · 06

Review primitive specs

TRACK · 07

Read CONTRIBUTING

TRACK · 08

Translate to Chinese

TRACK · 09

Open issues

Open the MVP Good First Issues Follow X / @OMWorldProtocol →